Prompt Leverage
Turn the user's current prompt into a stronger working prompt without changing the underlying intent. Preserve the task, fill in missing execution structure, and add only enough scaffolding to improve reliability.
Workflow
- Read the raw prompt and identify the real job to be done.
- Infer the task type: coding, research, writing, analysis, planning, or review.
- Rebuild the prompt with the framework blocks in
references/framework.md.
- Keep the result proportional: do not over-specify a simple task.
- Return both the improved prompt and a short explanation of what changed when useful.
Transformation Rules
- Preserve the user's objective, constraints, and tone unless they conflict.
- Prefer adding missing structure over rewriting everything stylistically.
- Add context requirements only when they improve correctness.
- Add tool rules only when tool use materially affects correctness.
- Add verification and completion criteria for non-trivial tasks.
- Keep prompts compact enough to be practical in repeated use.
Framework Blocks
Use these blocks selectively.
Objective: state the task and what success looks like.
Context: list sources, files, constraints, and unknowns.
Work Style: set depth, breadth, care, and first-principles expectations.
Tool Rules: state when tools, browsing, or file inspection are required.
Output Contract: define structure, formatting, and level of detail.
Verification: require checks for correctness, edge cases, and better alternatives.
Done Criteria: define when the agent should stop.
Output Modes
Choose one mode based on the user request.
Inline upgrade: provide the upgraded prompt only.
Upgrade + rationale: provide the prompt plus a brief list of improvements.
Template extraction: convert the prompt into a reusable fill-in-the-blank template.
Hook spec: explain how to apply the framework automatically before execution.
Hook Pattern
When the user asks for a hook, model it as a pre-processing layer:
- Accept the current prompt.
- Classify the task and risk level.
- Expand the prompt using the framework blocks.
- Return the upgraded prompt for execution.
- Optionally keep a diff or summary of injected structure.
Use scripts/augment_prompt.py when a deterministic first-pass rewrite is helpful.
Quality Bar
Before finalizing, check the upgraded prompt:
- still matches the original intent
- does not add unnecessary ceremony
- includes the right verification level for the task
- gives the agent a clear definition of done
If the prompt is already strong, say so and make only minimal edits.
1---2name: prompt-leverage3description: Upgrade raw prompts into execution-ready instructions. Use when asked to improve a prompt, add context, tool, verification, or done rules, extract a template, or design an enhancement hook.4metadata:5 source: https://skillmd.com/skills/hoangnb24/prompt-leverage6---78# Prompt Leverage910Turn the user's current prompt into a stronger working prompt without changing the underlying intent. Preserve the task, fill in missing execution structure, and add only enough scaffolding to improve reliability.1112## Workflow13141. Read the raw prompt and identify the real job to be done.152. Infer the task type: coding, research, writing, analysis, planning, or review.163. Rebuild the prompt with the framework blocks in `references/framework.md`.174. Keep the result proportional: do not over-specify a simple task.185. Return both the improved prompt and a short explanation of what changed when useful.1920## Transformation Rules2122- Preserve the user's objective, constraints, and tone unless they conflict.23- Prefer adding missing structure over rewriting everything stylistically.24- Add context requirements only when they improve correctness.25- Add tool rules only when tool use materially affects correctness.26- Add verification and completion criteria for non-trivial tasks.27- Keep prompts compact enough to be practical in repeated use.2829## Framework Blocks3031Use these blocks selectively.3233- `Objective`: state the task and what success looks like.34- `Context`: list sources, files, constraints, and unknowns.35- `Work Style`: set depth, breadth, care, and first-principles expectations.36- `Tool Rules`: state when tools, browsing, or file inspection are required.37- `Output Contract`: define structure, formatting, and level of detail.38- `Verification`: require checks for correctness, edge cases, and better alternatives.39- `Done Criteria`: define when the agent should stop.4041## Output Modes4243Choose one mode based on the user request.4445- `Inline upgrade`: provide the upgraded prompt only.46- `Upgrade + rationale`: provide the prompt plus a brief list of improvements.47- `Template extraction`: convert the prompt into a reusable fill-in-the-blank template.48- `Hook spec`: explain how to apply the framework automatically before execution.4950## Hook Pattern5152When the user asks for a hook, model it as a pre-processing layer:53541. Accept the current prompt.552. Classify the task and risk level.563. Expand the prompt using the framework blocks.574. Return the upgraded prompt for execution.585. Optionally keep a diff or summary of injected structure.5960Use `scripts/augment_prompt.py` when a deterministic first-pass rewrite is helpful.6162## Quality Bar6364Before finalizing, check the upgraded prompt:6566- still matches the original intent67- does not add unnecessary ceremony68- includes the right verification level for the task69- gives the agent a clear definition of done7071If the prompt is already strong, say so and make only minimal edits.