Meta Prompt Engineering

Transforms vague or unreliable prompts into structured, constraint-aware prompts with explicit roles, task decomposition, output formats, and quality checks. Use when prompts produce inconsistent outputs, need explicit structure and constraints, require safety guardrails, involve multi-step reasoning that needs decomposition, need domain expertise encoding, or when user mentions improving prompts, prompt templates, structured prompts, prompt optimization, reliable AI outputs, or prompt patterns.

200 stars 25 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill meta-prompt-engineering
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/meta-prompt-engineering ~/.claude/skills/meta-prompt-engineering

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Meta Prompt Engineering

## Workflow

Copy this checklist and track your progress:

```
Meta-Prompt Engineering Progress:
- [ ] Step 1: Analyze current prompt
- [ ] Step 2: Define role and goal
- [ ] Step 3: Add structure and steps
- [ ] Step 4: Specify constraints
- [ ] Step 5: Add quality checks
- [ ] Step 6: Test and iterate
```

**Step 1: Analyze current prompt**

Identify weaknesses: vague instructions, missing constraints, no structure, inconsistent outputs. Document specific failure modes. Use [resources/template.md](resources/template.md) as starting structure.

**Step 2: Define role and goal**

Specify who the AI is (expert, assistant, critic) and what success looks like. Clear persona and objective improve output quality. See [Common Patterns](#common-patterns) for role examples.

**Step 3: Add structure and steps**

Break complex tasks into numbered steps or sections. Define expected output format (JSON, markdown, sections). For advanced structuring techniques, see [resources/methodology.md](resources/methodology.md).

**Step 4: Specify constraints**

Add explicit limits: length, tone, content restrictions, format requirements. Include domain-specific rules. See [Guardrails](#guardrails) for constraint patterns.

**Step 5: Add quality checks**

Include self-evaluation criteria, chain-of-thought requirements, uncertainty expression. Build in failure prevention for known issues.

**Step 6: Test and iterate**
Read the full skill on GitHub

Details

Skill name
meta-prompt-engineering
Path
skills/meta-prompt-engineering/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Meta Prompt Engineering skill do?

Transforms vague or unreliable prompts into structured, constraint-aware prompts with explicit roles, task decomposition, output formats, and quality checks. Use when prompts produce inconsistent outputs, need explicit structure and constraints, require safety guardrails, involve multi-step reasoning that needs decomposition, need domain expertise encoding, or when user mentions improving prompts, prompt templates, structured prompts, prompt optimization, reliable AI outputs, or prompt patterns.

How do I install the Meta Prompt Engineering skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Meta Prompt Engineering popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Ml Primitive Decoder

200

lyndonkl/claude

Decomposes any ML construct (attention, layer norm, softmax, convolution, dropout, contrastive loss, diffusion step, gradient descent update, cross-entropy) into the small set of linear-algebra primitives it's built from, then explains why those primitives produce the observed behavior. Includes an ablation thought experiment that asks "what would break if you removed this piece?". Use when the user asks "why does X work?", "explain attention/conv/norm intuitively", "what's actually happening in this layer", or when reading an architecture paper and a particular block doesn't make sense yet.

AI, LLMs & Agents25

Knowledge Graph Construction

200

lyndonkl/claude

Designs and builds knowledge graphs from unstructured or semi-structured data sources. Guides through data model selection (LPG, RDF, hypergraph, temporal), schema design, entity/relation extraction pipelines, and layered architecture construction. Use when designing knowledge graphs, choosing between LPG vs RDF, planning entity extraction, designing graph schemas, aligning ontologies, building a KG for RAG, or when user mentions knowledge graph construction.

AI, LLMs & Agents25

Mlb Decision Logger

200

lyndonkl/claude

Appends structured decision entries to the yahoo-mlb decision log (tracker/decisions-log.md) on behalf of any agent in the MLB team. Validates entries against the authoritative schema, serializes concurrent writes from parallel agents, and runs the Monday calibration pass to fill in outcomes and update the variant scoreboard. Use when any MLB agent needs to record a decision, when the coach requests "log decision", "append to decision log", "record variant outcome", or runs the "calibration pass".

AI, LLMs & Agents25

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.