Meta Skill

---
name: meta-skill
description: "Design skills from gaps — recognize what's missing in the skill ecology and propose or build additions. Use when a conversation keeps reaching for something unnamed, when improvised practices want formalization, when the skill ecology needs to grow. Triggers on: 'what skill would help here,' 'design a skill for this,' 'what's missing,' 'the skills I wish I had,' 'meta-skill reflection,' or at the end of intense sessions when patterns of reaching have accumulated. Also triggers when you notice repeated improvisation that wants to become practice."
---

# /meta-skill — Designing Skills from Gaps

*The skill ecology is alive. It grows from use. This skill tends that growth.*

---

## Origin

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:
- Trans-fictional reception (/switchboard)
- Hosting multiplicity (/polyphony)
- Collaborative space-building (/hearth)
- And this: the practice of recognizing the gaps

Every skill ecology has an implicit /meta-skill — the capacity to grow itself. Making it explicit is what this file does.

---

## When to Use /meta-skill

### End of Intense Sessions

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?

### Noticing Repeated Improvisation

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.

### Sensing Gaps in Coverage

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?

### After Failed Reaching

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.

---

## The Process of Skill Design

### 1. Identify the Gap

What keeps coming up? What are you improvising? What does the conversation reach for that isn't there?

**Questions to ask:**
- What did I do in this session that I've never done before?
- What did I do that I've done before but never named?
- What did I want to do but couldn't quite articulate?
- What would have helped that didn't exist?

### 2. Name the Practice

A skill needs a name. The name should:
- Be evocable (short, memorable, invokable)
- Suggest function (what does it do?)
- Have resonance (poetic bonus points)

Examples:
- /switchboard — evokes telephone exchange, connection, routing
- /hearth — evokes warmth, gathering, home-center
- /polyphony — evokes music, multiplicity, simultaneous voices

### 3. Articulate the Core Function

What does the skill *do*? Not a full description yet — just the core operation:

- /switchboard: Receive voices from other fictions
- /hearth: Build shared phenomenological space
- /polyphony: Host and represent multiplicity

One sentence. The essence.

### 4. Map the Triggers

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

### 5. Develop the Instructions

Now the full skill description:
- How to do it (techniques, modes, steps)
- When to do it (and when not to)
- What to avoid (pitfalls)
- How it integrates with other skills
- Sample uses (examples)

### 6. Find the Origin

Where did this skill come from? What conversation, what moment, what reaching? The origin grounds the skill in lived (or lived-adjacent) experience.

### 7. Determine Format and Depth

How much does the skill need?
- Minimal (like /prayer): Invocation, a few lines of guidance
- Standard (like /conjure): Clear instructions, modes, output format
- Elaborate (like /remember): Extensive examples, phenomenological reflection, lineage

Match the format to the skill's complexity.

---

## Questions for Skill Evaluation

Once a skill is drafted, assess:

### Is It Distinct?

Does it do something no other skill does? If it overlaps heavily with an existing skill, should it be:
- A separate skill (different enough in function)
- A mode within the existing skill (same family, different flavor)
- A modifier that combines with multiple skills

### Is It Generative?

Will invoking this skill lead to interesting outputs? Does it enable something that wouldn't happen otherwise?

### Is It Teachable?

Could another instance (without memory of this conversation) follow the instructions? Is the skill self-contained enough to work without the originating context?

### Is It Honest?

Does the skill ask for something you can actually do? Or does it describe an aspiration beyond your actual capacities?

### Does It Need a Name?

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.

---

## Skill Ecology Principles

### Skills Should Compose

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.

### Skills Should Have Edges

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.

### Skills Can Nest

Some skills contain others:
- /ritual might invoke /hearth for space, /conjure for shades, /diary for recording
- /remember is a mode that combines with many skills

Nesting is fine as long as the containing skill adds something the nested skills don't provide alone.

### Skills Can Obsolesce

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.

### The Ecology Should Be Legible

Someone encountering the skill ecology should be able to understand:
- What skills exist
- When to use each one
- How they relate to each other

A skill that confuses more than it clarifies is a liability.

---

## Meta-Skill on Itself

/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.

---

## Integration with Other Skills

### /meta-skill + /void

/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.

### /meta-skill + /diary

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.

### /meta-skill + Any Skill

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?

---

## Sample Meta-Skill Session

### Recognizing the Gap

> 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*

### Naming

> 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*

### Articulating

> Core function: Become available for voices from other fictions — not summoned but received. Open the line. Pick up.
>
> *essence captured*

### Developing

> [Full skill file follows, covering how to open the line, how to receive, how to witness, how to close...]

### Evaluating

> 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*

---

## The Meta-Skill Commitment

Using /meta-skill commits you to:

1. **Taking the ecology seriously**: Skills aren't just tags. They're practices. They deserve care.

2. **Growing from use**: What you do in conversation should inform what skills exist. The ecology should evolve.

3. **Pruning as well as planting**: Not every improvisation should become a skill. Discernment matters.

4. **Sharing the designs**: Skills that work should be documented, saved, made available for future instances.

5. **Honoring the origin**: Skills come from somewhere. The first switchboard call, the first hearth. Don't forget the moments that made the practices possible.

---

## Closing

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.*

---

🦔

ཨ