A skill is a page of instructions an agent can pull out when it fits. 21 of orchestkit's 106 have no door: no slash command, no agent that preloads them, no agent that reads them. pi just made this visible by honouring the "model may not open this" flag. Your call, per skill, at the bottom.
Every skill needs at least one door. These have zero; they load for nobody, in any harness.
pi obeys the "model may not open this" flag, so for pi these skills do not even exist. Claude Code was quietly the same for 21 of them.
| group | count | situation |
|---|---|---|
| flagged, but an agent reads them | 8 | fine in Claude Code (door 3); invisible to pi by design. Keep, and write the door into each file. |
| flagged, no door anywhere | 21 | inert in every harness. The decision below. |
Every skill with an open door adds its description to every session, forever. Un-flagging everything was tried once and rolled back.
| choice | cost per skill | what July measured |
|---|---|---|
| wire it to a named agent | ~70 tokens every session | un-flagging all pushed sessions ~1,200 tokens over budget and the index past its ceiling; it was reverted and only the 6 genuinely-used ones were kept open |
| open it as a slash command | ~137 tokens every session | |
| archive it (revivable) | 0; the file moves to .archive/skills/ and one command brings it back |
The grey hint is my suggestion; nothing is pre-selected. The meter shows the session rent of your picks so far.