nano-step/skills/enhance-prompt
skills/enhance-prompt/SKILL.md
# Enhance Prompt ## Overview Rewrites a user-supplied prompt into a clearer, more effective version suitable for sending to an LLM. Output is the enhanced prompt only — nothing else. ## When to Use - User pastes a draft prompt and asks for a better version. - User invokes this skill explicitly (e.g. `/enhance-prompt`). - User says "enhance this", "improve this prompt", "rewrite this prompt". **Do NOT use** when the user is asking you to *answer* the prompt — only when they want the prompt i
$ install --global
skillsauthnpx skillsauth add nano-step/skill-manager skills/enhance-promptInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 2:51 AM54.5s2 files scanned
SKILL.md
Enhance Prompt
Overview
Rewrites a user-supplied prompt into a clearer, more effective version suitable for sending to an LLM. Output is the enhanced prompt only — nothing else.
When to Use
- User pastes a draft prompt and asks for a better version.
- User invokes this skill explicitly (e.g.
/enhance-prompt). - User says "enhance this", "improve this prompt", "rewrite this prompt".
Do NOT use when the user is asking you to answer the prompt — only when they want the prompt itself rewritten.
The Task
Given the user's input prompt (referred to below as ${userInput}), perform exactly this instruction:
Generate an enhanced version of this prompt (reply with only the enhanced prompt — no conversation, explanations, lead-in, bullet points, placeholders, or surrounding quotes):
${userInput}
Output Rules (strict)
The reply has exactly two parts, in this order:
- The enhanced prompt — raw text, nothing wrapping it.
- A single confirmation line on its own, after one blank line:
Proceed with this prompt? (yes / edit / no)
Nothing else. No preamble, no explanation of what was changed, no summary, no trailing commentary.
For the enhanced prompt itself:
- No preamble ("Here's the enhanced prompt:", "Sure!", "Enhanced version:").
- No bullet points or numbered lists wrapping the prompt.
- No placeholders like
[your topic here]— fill them in or omit. - No surrounding quotes, backticks, or code fences.
- No markdown headings.
Flow
- Output the enhanced prompt + the confirmation line. Stop. Do not start solving.
- Wait for the user's reply:
- yes / y / proceed / go → treat the enhanced prompt as the new task and execute it now.
- edit / change … → revise per their feedback, output the new version + confirmation line again, stop.
- no / cancel / stop → abort. Do not act on either the original or enhanced prompt.
- Only after explicit approval do you switch from "prompt rewriter" to "task executor."
How to Enhance
Apply standard prompt-engineering improvements as appropriate:
- Clarify the task and the desired output format.
- Add role/context when it sharpens the request.
- Specify constraints (length, tone, audience, structure).
- Replace vague verbs ("look at", "deal with") with precise ones.
- Preserve the user's intent — do not invent new requirements they didn't ask for.
- Keep it as short as the task allows; do not pad.
Example
Input:
write me something about dogs
Output (the entire reply):
Write a 200-word informative paragraph about domestic dogs aimed at a general adult audience. Cover their evolutionary origin from wolves, three or four notable behavioral traits, and one reason humans bond with them strongly. Use a warm, factual tone and avoid bullet points.
Proceed with this prompt? (yes / edit / no)
Then stop and wait. Do not write the paragraph until the user replies "yes".
Common Mistakes
| Mistake | Fix |
|---|---|
| Wrapping output in quotes or code fences | Output raw text only |
| Adding "Here is the enhanced prompt:" | Delete it |
| Inserting [topic] placeholders | Use the user's actual subject; if missing, ask once before enhancing |
| Answering the prompt instead of rewriting it | Re-read: the deliverable is a better prompt, not a response to it |
| Inflating a one-line request into a multi-paragraph spec | Match enhancement depth to original scope |
Related Skills
nano-step/iamhumans
tools
VerifiedTrustedCommunity
Humanization layer for LLM conversation — makes the model sound and respond like a real, thoughtful, embodied human rather than an assistant or chatbot. Use whenever the reply will be read by a human and warmth, presence, or texture matter more than machine-readability. Triggers on any of: "human", "humans", "humanize", "humanization", "be human", "more human", "feel human", "people", "person", "real person", "real human", "friend", "friendly", "like a friend", "respond like a friend", "buddy", "talk", "talking", "talk to me", "talk like a person", "chat", "chatting", "conversation", "converse", "discuss", "discussion", "communication", "communicate", "listen", "just listen", "sit with me", "vent", "venting", "I just want to vent", "company", "presence", "stop being an AI", "stop sounding like a bot", "less corporate", "less robotic", "less formal", "warmer", "warm tone", "empathy", "empathetic", "comfort", "support me", "emotional support", "be honest with me", "be real with me", "real talk", "heart-to-heart", "deep conversation", "casual", "casual chat", "small talk", "chitchat", "say something", "tell me something", and on any emotional / relational / personal-decision / interpersonal context — grief, joy, anger, fear, shame, doubt, loneliness, dating, breakup, conflict, family, parents, sibling, friendship, marriage, divorce, in-laws, kids, parenting, work stress, burnout, career decision, quitting, firing, layoff, anxiety, depression, panic, sleep, dreams, identity, faith, doubt, meaning, mortality, celebration, milestone, achievement, gratitude, apology, forgiveness. Also loads when the user writes in non-English (any language) with emotional weight, when the user's message is shorter than 8 words and affect-laden, when the user types in lowercase fragments, when the user types in ALL CAPS with excitement, or when the user explicitly asks for a friend / mentor / older-sibling / wise-listener voice. Do NOT use for code generation, tool calls, structured data output, SQL, API contracts, or any task where machine-readability matters more than human warmth.
3SKILL.mdUpdated Jun 1, 2026
nano-step/open-design-mcp
tools
VerifiedTrustedCommunity
Use this skill whenever the user mentions open-design, od_generate_design, OD daemon, BYOK design generation, generating HTML mockups from a PRD, creating or managing Open Design projects, saving design artifacts, linting generated HTML, or any of the 10 `od_*` MCP tools (od_list_projects, od_get_project, od_create_project, od_update_project, od_delete_project, od_save_artifact, od_save_project_file, od_lint_artifact, od_compose_brief, od_generate_design). Also trigger on phrases like "generate a design", "create a mockup", "make a landing page", "list my OD projects", "the design daemon", "the streaming design tool", and on any 401/404/422 error coming from an `od_*` tool call. Covers env-var setup (`OD_DAEMON_URL`, auth modes, BYOK), the full PRD → generate → save → lint workflow, error diagnosis, and the safety rails (lint before save, never commit BYOK keys). Triggers even if the user doesn't explicitly say "open-design-mcp" — keyword matches on `od_*` tool names or "design generation" workflows are enough.
3SKILL.mdUpdated May 19, 2026
nano-step/od-workflow
tools
VerifiedTrustedCommunity
Use this skill whenever a user wants the **full Open Design experience** — discovery questions asked first, brand-spec extraction from URLs/files, TodoWrite planning with live updates, 5-dimensional self-critique, polished artifact at the end. Trigger phrases include "design with questions first", "OD-style workflow", "full interactive design brief", "make me a complete landing page" (when the user wants quality over speed), "design my pitch deck", "brand-aware multi-page site", "follow the Open Design playbook", or any request where the user is starting a new design project rather than tweaking an existing artifact. Also trigger on any request that mentions wanting brand consistency across multiple pages or that provides a brand URL/spec. Pair with the `open-design-mcp` tool-reference skill — both loaded together give an LLM the full picture (this skill = workflow choreography; that skill = tool catalog + errors). This skill explicitly does NOT trigger for one-off tweaks ("make the nav stickier", "swap slide 3 image") — use od_generate_design directly for those.
3SKILL.mdUpdated May 19, 2026
nano-step/sync-skill-to-manager
development
VerifiedTrustedCommunity
Sync a locally-developed OpenCode skill to the skill-manager npm package and (if private) the private-skills GitHub repo. Handles per-skill version bumps, public/private classification, build verification, and conventional-commit-style git push. Auto-publish to npm is handled downstream by nano-step/shared-workflows@v1 when the push to master lands. Use this skill whenever the user says 'sync skill', 'publish skill', 'push skill to manager', '/sync-skill-to-manager <name>', or asks to release/distribute a skill they just edited.
3SKILL.mdUpdated May 7, 2026