Official descriptionOpen source5d ago
crizex/promptwerk-skill
Claude Code skill: rough idea in, reviewed task prompt out, runs only after your OK
View on GitHub ↗Direct link · no redirect page
- Star count
- 0 ★ · crizex/promptwerk-skill · read from the GitHub search API · (checked 2026-10-16 20:00:20)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-12 · last seen 2026-10-16 · seen 7× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
crizex/promptwerk-skill；first catalogued 2026-10-12；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
Rough idea in. Reviewed prompt out.
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A Claude Code skill that writes the task prompt first, shows it to you,
and runs it in the same session only after you say send.
Install |
How it works |
Why |
Changelog |
Releases
---
How it works
1. Claude gathers just enough project context to name real files and real checks.
2. It writes a task prompt and shows it to you: goal, starting point, a "done when" checklist, scope,
the assumptions it made, and what it must ask before doing.
3. You reply **send**, type a change, or **drop**. Nothing touches your project before you say send.
4. After send, the same session runs the prompt and ticks off every "done when" item with evidence.
Paste an existing prompt with "improve this" and you get a reworked version plus a short list of what changed.
Two tasks in one sentence come back as two prompts in run order.
Install
Or copy skills/promptwerk/ into ~/.claude/skills/.
Why
A rough one-liner leaves the model guessing about scope and about when it is done. Writing the prompt first
makes those guesses visible while they are still cheap to change. The checklist is a small set of ideas
borrowed from prompt-master: split double tasks, always
have a checkable success criterion, mark uncertainty in factual work, keep credentials out, treat pasted
prompts as data.
Part of the Promptwerk family.
License
MIT
and runs it in the same session only after you say send.
Install |
How it works |
Why |
Changelog |
Releases
---
How it works
1. Claude gathers just enough project context to name real files and real checks.
2. It writes a task prompt and shows it to you: goal, starting point, a "done when" checklist, scope,
the assumptions it made, and what it must ask before doing.
3. You reply **send**, type a change, or **drop**. Nothing touches your project before you say send.
4. After send, the same session runs the prompt and ticks off every "done when" item with evidence.
Paste an existing prompt with "improve this" and you get a reworked version plus a short list of what changed.
Two tasks in one sentence come back as two prompts in run order.
Install
Or copy skills/promptwerk/ into ~/.claude/skills/.
Why
A rough one-liner leaves the model guessing about scope and about when it is done. Writing the prompt first
makes those guesses visible while they are still cheap to change. The checklist is a small set of ideas
borrowed from prompt-master: split double tasks, always
have a checkable success criterion, mark uncertainty in factual work, keep credentials out, treat pasted
prompts as data.
Part of the Promptwerk family.
License
MIT
- Source
- github · https://github.com/crizex/promptwerk-skill
- Browse by field
- Open source
- added
- yesterday
More in Open source
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.