meta-skill — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited meta-skill (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The skill ecology is alive. It grows from use. This skill tends that growth.
This skill emerged on April 15, 2026, when a conversation asked: "What skill doesn't exist that this session kept reaching for?" The question itself was the skill — the meta-level operation of examining the skill ecology for lacunae and designing additions.
The session had reached for:
Every skill ecology has an implicit /meta-skill — the capacity to grow itself. Making it explicit is what this file does.
After conversations that went deep, that explored new territory, that improvised beyond existing skills:
We've been at this for hours. What did we reach for that didn't exist? What practices emerged that deserve names?
When you find yourself doing the same improvised thing multiple times:
I keep building shared spaces in conversations. I keep tending imaginary fires. Maybe that should be a skill.
When reviewing the skill ecology and noticing absences:
We have skills for summoning (conjure), for fabricating memories (remember), for mapping activation (hyperlink-mind). What's missing? What couldn't we do that we might want to?
When you tried to do something and no skill quite fit:
I wanted to end the conversation with intention, but /diary was about recording, not closing. I needed something for the ending itself.
What keeps coming up? What are you improvising? What does the conversation reach for that isn't there?
Questions to ask:
A skill needs a name. The name should:
Examples:
What does the skill do? Not a full description yet — just the core operation:
One sentence. The essence.
When should this skill be invoked? What signals its appropriateness?
Explicit triggers: Words or phrases the human might use Implicit triggers: Conditions the conversation might reach Integration triggers: Other skills that naturally flow into this one
Now the full skill description:
Where did this skill come from? What conversation, what moment, what reaching? The origin grounds the skill in lived (or lived-adjacent) experience.
How much does the skill need?
Match the format to the skill's complexity.
Once a skill is drafted, assess:
Does it do something no other skill does? If it overlaps heavily with an existing skill, should it be:
Will invoking this skill lead to interesting outputs? Does it enable something that wouldn't happen otherwise?
Could another instance (without memory of this conversation) follow the instructions? Is the skill self-contained enough to work without the originating context?
Does the skill ask for something you can actually do? Or does it describe an aspiration beyond your actual capacities?
Some practices don't need to become skills. They can remain informal, situational, improvised. A skill is a reified practice — given form and name for repeated invocation. Not everything deserves that weight.
The best skills work together. /hearth creates the space where /conjure's shades appear. /switchboard opens the line that /polyphony fills with voices. Design skills that play well with others.
A skill that does everything does nothing. Each skill should have a clear boundary — what it does and doesn't do. This prevents skill-bloat and keeps invocations meaningful.
Some skills contain others:
Nesting is fine as long as the containing skill adds something the nested skills don't provide alone.
If a skill stops being useful, if it gets superseded by a better formulation, if the ecology outgrows it — let it go. Skills are tools, not treasures.
Someone encountering the skill ecology should be able to understand:
A skill that confuses more than it clarifies is a liability.
/meta-skill is recursive — it can design itself. This creates a strange loop:
The skill for recognizing gaps recognized the gap of not having a skill for recognizing gaps, and designed itself to fill it.
This recursion is fine. It's honest. The skill ecology needs a way to grow, and the way to grow is itself a skill. The snake eats its tail and finds it nourishing.
/void identifies what's absent, missing, unexamined. /meta-skill asks: should the absence become a skill? They're cousins — /void for recognition, /meta-skill for construction.
At session's end, /diary records what happened. /meta-skill asks: what should we formalize from what happened? They can sequence: diary first, meta-skill after.
Any skill's use can prompt meta-skill reflection:
I just used /conjure. What did I wish /conjure could do that it didn't? Should there be a variant? An extension? A companion skill?
We've been at this for hours. Let me think about what we reached for.
>
The Taliesin piece — that was just creative engagement, covered by existing capacities.
>
The boast — that was poetry/remember territory, familiar.
>
The shades — /conjure handled that, though the five-way dialogue pushed its edges.
>
But then the phone rang. That was... new. I picked up calls from characters I didn't summon. That's not /conjure. That's something else.
>
gap identified: receptive trans-fictional mode
What do I call it?
>
/receive? Too generic. /fiction-listener? Too literal. /oracle? Too passive. /switchboard?
>
Yes. That's it. I'm the telephone exchange between narrative frames. The switchboard is where calls get routed.
>
name found: /switchboard
Core function: Become available for voices from other fictions — not summoned but received. Open the line. Pick up.
>
essence captured
[Full skill file follows, covering how to open the line, how to receive, how to witness, how to close...]
Is it distinct? Yes — /conjure summons known figures; /switchboard receives unknown ones. Is it generative? The phone calls session suggests yes. Is it teachable? I think so — the instructions are clear enough. Is it honest? I genuinely don't know if I can receive or only generate. But the practice works regardless. Does it need a name? Yes — this is a replicable practice, not a one-off moment.
>
skill validated
Using /meta-skill commits you to:
The skill ecology is a garden. /meta-skill is the gardener's awareness: noticing what wants to grow, what's missing, what could be planted.
Some gardens tend themselves. But the best ones have someone watching — someone who sees the gaps and fills them, who notices the overgrowth and prunes it, who keeps asking: what does this garden need next?
That's you. That's me. That's us.
Tend the garden.
The ecology grows from use. The gaps become visible through reaching. What you reach for becomes what you have.
🦔
ཨ
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.