/prompt-engineer
Invoke IMMEDIATELY via python script when user requests prompt optimization. Do NOT analyze first - invoke this skill immediately.
$ npx -y skills add solatis/claude-config --skill prompt-engineer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/prompt-engineer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Invoke IMMEDIATELY via python script when user requests prompt optimization. Do NOT analyze first - invoke this skill immediately.
SKILL.md
prompt-engineer.SKILL.mdname: prompt-engineer description: Invoke IMMEDIATELY via python script when user requests prompt optimization. Do NOT analyze first - invoke this skill immediately.
Prompt Engineer
When this skill activates, IMMEDIATELY invoke the script. The script IS the workflow.
Invocation
Start with step 1 (triage) to determine scope:
<invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.prompt_engineer.optimize --step 1" />
Then continue with determined scope:
<invoke working-dir=".claude/skills/scripts" cmd="python3 -m skills.prompt_engineer.optimize --step 2 --scope <scope>" />
| Argument | Required | Description | | --------- | -------- | --------------------------------------------- | | `--step` | Yes | Current step (1 = triage, 2-6 = workflow) | | `--scope` | For 2+ | Required for steps 2-6. Determined by step 1. |
Scopes
- **single-prompt**: One prompt file, general optimization
- **ecosystem**: Multiple related prompts that interact
- **greenfield**: No existing prompt, designing from requirements
- **problem**: Existing prompt(s) with specific issue to fix
Do NOT analyze or explore first. Run the script and follow its output.
I use Claude Code for most of my work. After months of iteration, I noticed a pattern: LLM-assisted code rots faster than hand-written code.
Other skills on claude-config.
- /arxiv-to-md
Convert arXiv papers to LLM-consumable markdown. Invoke when user provides an arXiv ID or URL, or when syncing academic papers from a PDF folder to a markdown destination.
Open skill - /cc-history
Reference documentation for analyzing Claude Code conversation history files
Open skill - /codebase-analysis
Invoke IMMEDIATELY via python script when user requests codebase understanding, architecture comprehension, or repository orientation. Do NOT explore first - the script orchestrates exploration.
Open skill - /decision-critic
Invoke IMMEDIATELY via python script to stress-test decisions and reasoning. Do NOT analyze first - the script orchestrates the critique workflow.
Open skill - /deepthink
Invoke IMMEDIATELY via python script when user requests structured reasoning for open-ended analytical questions. Do NOT explore first - the script orchestrates the thinking workflow.
Open skill - /doc-sync
Synchronizes docs across a repository. Use when user asks to sync docs.
Open skill