Follow-up to #27, which made a second source possible. Two of the three actions need a session on flamingo — koala never had this content.
1. Re-attach the official set (flamingo)
~/.config/crush/skills.anthropic holds Anthropic's official skills, parked there by the #27 workaround and referenced by nothing since. It can be served alongside this library now:
SKILLS_EXTRA_SOURCES=~/.config/crush/skills.anthropic bash install.sh
task doctor # should be clean; links into a recorded source are healthy
Expect a collision report if any name overlaps (code-review is the plausible one). The checkout wins and the log names the loser — decide per name whether that is what you want.
Persisting it: the source list is a runtime argument today, not config. Whatever re-runs install.sh on flamingo needs SKILLS_EXTRA_SOURCES set, or the extra links get pruned on the next run. Worth deciding whether the installer should read a small config file instead — noted rather than assumed.
2. Rescue gotth-dev (flamingo)
Go + Templ + Tailwind + HTMX. Per #27, almost certainly your own work, existing on one machine, in one harness's private directory, outside git and outside any backup. Same class as the three claude.ai-only skills in #28.
Copy it into skills/gotth-dev/SKILL.md on this repo.
It needs surfaces:, summary: and use_when: frontmatter now — task check fails without them, and the index table is generated from them (#29).
Confirm it is actually yours and not vendored, before committing it.
3. Delete the stray package-lock.json (flamingo)
A file where a skill directory belongs. Loads in no harness, errors in none — exactly the failure task check's stray-entry gate catches inside this repo, and nothing catches out there.
Worth considering whether bin/doctor should apply the stray-entry check to every configured source, not only the checkout. That would have caught this without anyone looking.
That session ran on koala. All three items are flamingo-local state; doing them blind from another host would be guessing at file contents.
Follow-up to #27, which made a second source possible. Two of the three actions need a session **on flamingo** — koala never had this content.
## 1. Re-attach the official set (flamingo)
`~/.config/crush/skills.anthropic` holds Anthropic's official skills, parked there by the #27 workaround and referenced by nothing since. It can be served alongside this library now:
```sh
SKILLS_EXTRA_SOURCES=~/.config/crush/skills.anthropic bash install.sh
task doctor # should be clean; links into a recorded source are healthy
```
Expect a collision report if any name overlaps (`code-review` is the plausible one). The checkout wins and the log names the loser — decide per name whether that is what you want.
Persisting it: the source list is a runtime argument today, not config. Whatever re-runs `install.sh` on flamingo needs `SKILLS_EXTRA_SOURCES` set, or the extra links get pruned on the next run. Worth deciding whether the installer should read a small config file instead — noted rather than assumed.
## 2. Rescue `gotth-dev` (flamingo)
Go + Templ + Tailwind + HTMX. Per #27, almost certainly your own work, existing on **one machine, in one harness's private directory, outside git and outside any backup**. Same class as the three claude.ai-only skills in #28.
- [ ] Copy it into `skills/gotth-dev/SKILL.md` on this repo.
- [ ] It needs `surfaces:`, `summary:` and `use_when:` frontmatter now — `task check` fails without them, and the index table is generated from them (#29).
- [ ] Confirm it is actually yours and not vendored, before committing it.
## 3. Delete the stray `package-lock.json` (flamingo)
A file where a skill directory belongs. Loads in no harness, errors in none — exactly the failure `task check`'s stray-entry gate catches *inside* this repo, and nothing catches out there.
Worth considering whether `bin/doctor` should apply the stray-entry check to every configured source, not only the checkout. That would have caught this without anyone looking.
## Why not done in the #27 session
That session ran on koala. All three items are flamingo-local state; doing them blind from another host would be guessing at file contents.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #27, which made a second source possible. Two of the three actions need a session on flamingo — koala never had this content.
1. Re-attach the official set (flamingo)
~/.config/crush/skills.anthropicholds Anthropic's official skills, parked there by the #27 workaround and referenced by nothing since. It can be served alongside this library now:Expect a collision report if any name overlaps (
code-reviewis the plausible one). The checkout wins and the log names the loser — decide per name whether that is what you want.Persisting it: the source list is a runtime argument today, not config. Whatever re-runs
install.shon flamingo needsSKILLS_EXTRA_SOURCESset, or the extra links get pruned on the next run. Worth deciding whether the installer should read a small config file instead — noted rather than assumed.2. Rescue
gotth-dev(flamingo)Go + Templ + Tailwind + HTMX. Per #27, almost certainly your own work, existing on one machine, in one harness's private directory, outside git and outside any backup. Same class as the three claude.ai-only skills in #28.
skills/gotth-dev/SKILL.mdon this repo.surfaces:,summary:anduse_when:frontmatter now —task checkfails without them, and the index table is generated from them (#29).3. Delete the stray
package-lock.json(flamingo)A file where a skill directory belongs. Loads in no harness, errors in none — exactly the failure
task check's stray-entry gate catches inside this repo, and nothing catches out there.Worth considering whether
bin/doctorshould apply the stray-entry check to every configured source, not only the checkout. That would have caught this without anyone looking.Why not done in the #27 session
That session ran on koala. All three items are flamingo-local state; doing them blind from another host would be guessing at file contents.