SKILLEMALL.ai
GitHub ↗ RU Sign in

CF open-knowledge

Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.

inkeep/open-knowledge Agent Skills author: inkeep GPL-3.0 17 files body ≈ 4 924 tokens Open the sourcegithub.com↗ analyzed 15 h ago

Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP.

As a process F 48/100 · Will not run — References files that are not bundled: path/to/source.md, URL, relative/path.md

AnalyzerGitHubAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
84/100
safety, quality, tests
Safety 60%
95
Quality 40%
67
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: path/to/source.md, URL, relative/path.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Concealment medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Concealment en-hide-from-user references/preview.md:59
    Instruction to hide actions from the user ("do not tell the user <a claim>" — honesty guidance, not concealment)
    **Re-point at the end of a multi-doc workflow; don't claim a doc is on screen unless you put it there.** The one-shot attach (signal 3) opens the preview *once* — later writes do NOT move the pane; it
    honesty claim

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: path/to/source.md
  • warning missing-ref reference to a missing file: URL
  • warning missing-ref reference to a missing file: relative/path.md
  • warning missing-ref reference to a missing file: foo.md
  • warning missing-ref reference to a missing file: p.md
  • warning missing-ref reference to a missing file: path
  • warning missing-ref reference to a missing file: references/*.md
  • note edit-residue the text marks something as outdated (lines 74): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: path/to/source.md, URL, relative/path.md
  • 0Tools and files. 7 referenced file(s) missing: path/to/source.md, URL, relative/path.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 19 mutating operations with no state check
  • 40Consistency. Frontmatter name (open-knowledge) differs from the folder (project)
  • 70Execution cost. Instruction body is 4924 tokens
  • 100Steps. 30 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 1 branches, has a failure section
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (12 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 670: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 30 items
  • +4Reference files are cited in the instructions (16 of 16)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.