agentleFS
gary2376gary2376/claude-skills/prompt-craft/SKILL.md

prompt-craft

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Use when the user has a vague/underspecified request they want to turn into a well-formed prompt for an AI tool (any AI, not just Claude) — e.g. \"幫我寫封信\" \"幫我看一下這份資料\" \"幫我回這個客訴\" without saying who it's for, what format, or what tone. Also use when the user explicitly asks how to write a better prompt, or says a prompt/reply from an AI came out wrong because they didn't specify enough. Detects which of 6 dimensions (role/context/format/audience-tone/example/constraints) are missing from the raw request, asks ONE consolidated clarifying question for what's missing (does not silently guess), then assembles a structured prompt with a one-line note explaining why each filled-in field matters — grounded in Anthropic/OpenAI/Google's own prompt engineering guides plus workplace-survey data on why non-technical staff struggle to prompt (34% confident at task decomposition, LinkedIn/TalentLMS 2026).

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.