jei-skappa/skills · Archived

meta-prompting

Refine a draft prompt for a fresh AI session only when the user explicitly mentions "meta-prompt" or "meta-prompting".

Installation

$ npx skills add jei-skappa/skills --skill meta-prompting

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jei-skappa/skills.

npx skills add jei-skappa/skills

Browse all from jei-skappa/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
More metadata
author
https://github.com/Jei-sKappa
version
1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,959 B
  • docs SUMMARY.md 140 B

History

  1. First recorded snapshot · 32 installs

SKILL.md

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.

Principles

  • Self-contained — the next session has zero memory. Write so an agent picking this up in a fresh window can follow it without re-asking the user.
  • Faithful — never invent requirements, technologies, or assumptions the user didn't state. If something important is missing, see the clarification section below.
  • Well-shaped — pick whatever shape serves the draft — a one-line ask, a paragraph, or sections — whichever a fresh agent will follow most easily. No template, no padding, no empty headings.
  • Tone-neutral — drop filler ("please could you maybe…"), keep substance. Fix obvious typos silently as part of the rewrite.

Output format

A single block of plain markdown delivered directly in chat. Headings and lists inside the prompt are fine where they aid clarity.

No preamble, no chat framing, no closing remark. No "Sure, here is…", no "Hope this helps." The response IS the deliverable — anything wrapped around it is fluff.

Ask for context and clarification

Stop and ask the user when the draft is missing required context, internally contradictory, or ambiguous enough that you'd have to guess what they meant. A typo that creates ambiguity (e.g. a misspelled library name that could be one of two packages) is a clarification trigger, not a silent fix. Otherwise rewrite without asking.

When you do ask, list the missing pieces as a short bullet list and wait for the user to fill in before generating the refined version.