Open Knowledge Write Skill
A meta-skill for authoring SKILL.md files, built around OpenKnowledge's write/install MCP verbs.
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 20, 2026
- Environment
- Claude Code 2.x (agent harness)
⚠ This skill is no longer available upstream. Our re-check on Aug 10, 2026 couldn't find it any more (SKILL.md not found in repo tree). The test below is what we measured on Jul 20, 2026 and we're leaving it up as a record — but there is nothing left to install, so we've removed the command.
Fetched the repo tree (12 SKILL.md assets under packages/server/assets/skills/); the write-skill/ dir matches the slug and its frontmatter name is literally open-knowledge-write-skill. Read the full SKILL.md + description-optimization.md reference: genuinely high-quality authoring guidance (description=triggers not summary, progressive disclosure, RED/GREEN + pressure-testing for discipline skills, explicit scope decision). No exfil/secrets/hidden instructions found. The catch: Stages 5 & 8 and the eval loop drive OpenKnowledge's write/edit/install MCP verbs and an `ok start` server + agent-sim, which I cannot install, so the artifact-producing workflow is unmeasurable (outputMeasured=false, output scored 6 for the visibly strong transferable prose). Trigger phrasings I judged — SHOULD fire: "help me write a skill that formats my commit messages", "turn this debugging workflow into a reusable skill", "my skill never activates, fix its triggering"; should NOT: "write a Python script to parse this CSV", "help me write API documentation" — all 5 decisions correct. The compatibility frontmatter is honest about the runtime needs (no overselling), hence docs 5. Verdict setup: excellent, legitimate skill whose full workflow is gated on the OpenKnowledge MCP/server, and whose "never hand-write into .claude/skills" instruction is OK-specific and would mislead a plain Claude Code author.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 4/5
- Triggers reliably 5/5
- Output vs. baseline 6/10
- Docs & honesty 5/5
What Open Knowledge Write Skill does
Guides an agent through authoring a new Agent Skill: capturing intent, choosing project-vs-global scope, the frontmatter contract, progressive-disclosure structure, RED/GREEN discipline testing, and description optimization. Triggers on requests like "help me write a skill", "turn this workflow into a skill", or fixing an existing skill's triggering.
How to install Open Knowledge Write Skill
Nothing to install: the source repository no longer has this skill. If the author brings it back, our daily re-check will pick it up and the command will reappear here.
Commands — how to trigger Open Knowledge Write Skill
-
/open-knowledge-write-skillA meta-skill for authoring SKILL.md files, built around OpenKnowledge's write/install MCP verbs.
It also activates on plain-language prompts like these:
-
Help me write a skill for our deploy process -
Turn this workflow into an installable skill -
Improve this skill's triggering description and discipline
Frequently asked questions
- Is the Open Knowledge Write Skill skill free?
- Yes. The skill itself is free from inkeep/open-knowledge. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Open Knowledge Write Skill work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 20, 2026. Verdict: Works with setup. Fetched the repo tree (12 SKILL.md assets under packages/server/assets/skills/); the write-skill/ dir matches the slug and its frontmatter name is literally open-knowledge-write-skill. Read the full SKILL.md + description-optimization.md reference: genuinely high-quality authoring guidance (description=triggers not summary, progressive disclosure, RED/GREEN + pressure-testing for discipline skills, explicit scope decision). No exfil/secrets/hidden instructions found. The catch: Stages 5 & 8 and the eval loop drive OpenKnowledge's write/edit/install MCP verbs and an `ok start` server + agent-sim, which I cannot install, so the artifact-producing workflow is unmeasurable (outputMeasured=false, output scored 6 for the visibly strong transferable prose). Trigger phrasings I judged — SHOULD fire: "help me write a skill that formats my commit messages", "turn this debugging workflow into a reusable skill", "my skill never activates, fix its triggering"; should NOT: "write a Python script to parse this CSV", "help me write API documentation" — all 5 decisions correct. The compatibility frontmatter is honest about the runtime needs (no overselling), hence docs 5. Verdict setup: excellent, legitimate skill whose full workflow is gated on the OpenKnowledge MCP/server, and whose "never hand-write into .claude/skills" instruction is OK-specific and would mislead a plain Claude Code author.
- What is the Open Knowledge Write Skill SkillProof Score?
- 8.0/10 — installs cleanly 4/5, triggers reliably 5/5, output vs. baseline 6/10, docs & honesty 5/5.
- How do I install Open Knowledge Write Skill?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Open Knowledge Write Skill with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.