meta-prompting
Meta-Prompting
Take the user's raw prompt — usually quickly typed, possibly rambling, missing structure — and rewrite it as a polished prompt that can be pasted into a fresh AI agent session. Deliver the rewritten prompt on the system clipboard via the bundled script.
When to use
Only when the user has explicitly asked to meta-prompt a draft or invoked this skill by name. Do not run it on your own initiative — a pasted-in draft, a rambling message, or a "before I start a new chat…" aside is not a trigger. Wait for the intent to be stated.
When it does run, the output is going to a new AI session with zero context. Whatever the user assumed in their head must end up explicitly written in the refined prompt, or the new session will flounder.
Principles
- Self-contained — the new session has no memory of this conversation. Every fact, file path, constraint, or goal needs to be in the rewritten prompt.
- Faithful — do not invent requirements, technologies, or assumptions the user didn't state. If something important is missing, name it as an open question rather than guessing.
- Structured — group information by purpose (context, goal, constraints, deliverables) instead of preserving the order it was typed in.
- Specific — replace vague gestures ("the thing", "that issue") with concrete names. If the draft is too vague to specify without inventing, ask before rewriting.
- Actionable — the new session should know what to do next without re-asking the user.
- Tone-neutral — drop filler ("please could you maybe…"), keep substance.
More from jei-skappa/skills
consult-the-expert
Drafts a casual, context-rich message to consult a more experienced developer about a technical problem, decision, or blocker. Use when the user wants help framing a question for a senior teammate, mentor, or domain expert who has zero context on the project being worked on.
9report-to-the-owner
Drafts a casual, context-rich message to a code owner about something in their code that's blocking the user — a bug, missing capability, or design that doesn't extend to a new use case — along with a proposed change. Use when the user has hit a blocker in code owned by another developer or team and explicitly wants to hand off the work, not ask for advice.
7brief-the-implementer
Drafts a self-contained outcome briefing — the verdict, why, caveats, and pointers — that someone who wasn't part of the discussion can pick up and act on. Use when the user wants the conclusion of the current discussion packaged as a paste-ready handoff for a separate context — a fresh AI session, a follow-up task, or a teammate catching up.
6afk-exploration
Start AFK exploration on a topic. Use only when the user explicitly asks to start an AFK research or exploration on a topic.
3