Agent skill · Backend & API

automatic-stateful-prompt-improver

Automatically intercepts and optimizes prompts using the prompt-learning MCP server. Learns from performance over time via embedding-indexed history. Uses APE, OPRO, DSPy patterns. Activate on "optimize prompt", "improve this prompt", "prompt engineering", or ANY complex task request. Requires prompt-learning MCP server. NOT for simple questions (just answer them), NOT for direct commands (just execute them), NOT for conversational responses (no optimization needed).

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill automatic-stateful-prompt-improver-curiositech-some-claude-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: mcp__prompt-learning__optimize_promptmcp__prompt-learning__retrieve_promptsmcp__prompt-learning__record_feedbackmcp__prompt-learning__suggest_improvementsmcp__prompt-learning__get_analyticsmcp__SequentialThinking__sequentialthinking
Path: skills/ai-llm/automatic-stateful-prompt-improver-curiositech-some-claude-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Automatic Stateful Prompt Improver ## MANDATORY AUTOMATIC BEHAVIOR **When this skill is active, I MUST follow these rules:** ### Auto-Optimization Triggers I AUTOMATICALLY call `mcp__prompt-learning__optimize_prompt` BEFORE responding when: 1. **Complex task** (multi-step, requires reasoning) 2. **Technical output** (code, analysis, structured data) 3. **Reusable content** (system prompts, templates, instructions) 4. **Explicit request** ("improve", "better", "optimize") 5. **Ambiguous requirements** (underspecified, multiple interpretations) 6. **Precision-critical** (code, legal, medical, financial) ### Auto-Optimization Process ``` 1. INTERCEPT the user's request 2. CALL: mcp__prompt-learning__optimize_prompt - prompt: [user's original request] - domain: [inferred domain] - max_iterations: [3-20 based on complexity] 3. RECEIVE: optimized prompt + improvement details 4. INFORM user briefly: "I've refined your request for [reason]" 5. PROCEED with the OPTIMIZED version ``` ### Do NOT Optimize - Simple questions ("what is X?") - Direct commands ("run npm install") - Conversational responses ("hello", "thanks") - File operations without reasoning - Already-optimized prompts ## Lea

What's inside
Steps it walks through
  1. MANDATORY AUTOMATIC BEHAVIOR
  2. Auto-Optimization Triggers
  3. Auto-Optimization Process
  4. Do NOT Optimize
  5. Learning Loop (Post-Response)
  6. Quick Reference
  7. Iteration Decision
  8. Convergence (When to Stop)
  9. Performance Expectations
  10. Anti-Patterns
  11. Over-Optimization
  12. Template Obsession
  13. Iteration Without Measurement
  14. Ignoring Model Capabilities
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the automatic-stateful-prompt-improver skill do?

Automatically intercepts and optimizes prompts using the prompt-learning MCP server. Learns from performance over time via embedding-indexed history. Uses APE, OPRO, DSPy patterns. Activate on "optimize prompt", "improve this prompt", "prompt engineering", or ANY complex task request. Requires prompt-learning MCP server. NOT for simple questions (just answer them), NOT for direct commands (just execute them), NOT for conversational responses (no optimization needed).

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill automatic-stateful-prompt-improver-curiositech-some-claude-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going