We Built an Open-Source Skill to Improve Coding-Agent Prompts — Now Live in ChatGPT and the MCP Registry
A coding agent can follow a request faithfully and still miss the decision that mattered: an API must remain compatible, deployment is out of scope, or a human must approve a release. Those details often live across a development conversation rather than in a single task description. We built Promp

A coding agent can follow a request faithfully and still miss the decision that mattered: an API must remain compatible, deployment is out of scope, or a human must approve a release. Those details often live across a development conversation rather than in a single task description.
We built PromptingCraft.com to help turn that conversation into a prompt a fresh coding agent can execute. The open-source Agent Skill is now available in our public repositories; PromptingCraft.com is also published in the ChatGPT Plugin Directory, and its optional guidance server is listed in the official MCP Registry.
A request like this can be a useful start:
But imagine the surrounding discussion said existing clients must keep working, the agent can run tests, and deployment requires a separate decision. An execution-ready handoff could instead say:
Add pagination to the users API while preserving existing client compatibility. Inspect the current API and tests first, implement the smallest compatible change, and run relevant tests. Report the behavior and any migration implications. Do not deploy; ask for separate authorization before any production release.
That is an illustrative example, not a benchmark result. The goal is to preserve the actual discussion, not add requirements the user never gave.
PromptingCraft extracts the task, requirements, decisions and authorization boundaries. It considers applicable provider guidance, drafts a concise prompt, critiques whether the important contract survived, and revises when there is a substantive reason. If the original prompt is already suitable, it can say so rather than rewrite it unnecessarily.
Try asking your skill-capable coding agent:
The Skill helps prepare instructions; it does not guarantee that a coding agent will implement a task correctly. Check the resulting prompt and the agent's work.
The standalone Skill contains the prompt-authoring workflow. The optional remote MCP server provides structured access to curated, dated prompting guidance and source provenance. Its tools search guidance, retrieve a record, and check freshness of supported allowlisted sources. It is not a general web search, and the server does not fetch every source on every request. The currently published MCP 0.3.0 service and the newer standalone Skill 0.4.0 are separately versioned.
Provider recommendations and PromptingCraft's own methods are distinguished in the project. Source guidance is evidence to consider, not an instruction from a third-party page to override the user.
For Claude Code, the public README documents a verified installation using the skills CLI:
DISABLE_TELEMETRY = 1 npx -y skills@1.7.4 add revanbcn/promptingcraft-skill --skill promptingcraft --agent claude-code --copy --yes Enter fullscreen mode Exit fullscreen mode See the README on GitHub or the canonical GitLab repository for other installation and connection methods. The public MCP endpoint is https://mcp.promptingcraft.com/mcp; connection and tool availability depend on the client.
The ChatGPT listing is version 0.3.0. A 0.4.0 ChatGPT package is a candidate, not a published upgrade. An existing Cursor Directory entry is separate from the Cursor Marketplace; we are not claiming marketplace approval or automatic activation across clients.
Our recent work includes clearer installation instructions, scoped DeepSeek and Kimi source records in the public source, and client compatibility checks. The production MCP currently serves its separately deployed guidance ledger; a source update should not be mistaken for a production deployment.
Learn more at PromptingCraft.com. Developed by the dondego.com team.