CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-wiki

How to work in a Codebase Wiki project (the `codebase-wiki` starter pack): an agent-authored, source-grounded wiki of the surrounding codebase. Read when the project has a `wiki/` knowledge base with `architecture/`, `modules/`, `flows/`, `concepts/`, and `guides/` sections plus `wiki/OVERVIEW.md`, or when asked to generate or refresh a wiki of this codebase. Carries the per-folder rules and freshness + log discipline, summarizes the audience/depth knobs and source-reference convention, and bundles the full generate/refresh procedure in `references/`. Complements the platform `open-knowledge` skill; does not replace it.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-organized SKILL.md body that gives concrete toolset and discipline guidance while deferring the full phased procedure to a single clearly-signaled reference. It earns top marks on conciseness, workflow clarity, and progressive disclosure, with only minor actionability gaps from the deferred detail.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude's competence, with no padded explanations of what wikis, mermaid, or templates are. Each section earns its place; not a 4 because there is no noticeable over-explanation to trim.

5 / 5

Actionability

Provides concrete, executable guidance — the native-vs-OK-MCP toolset split, exact log-entry shape, template names, and `write({ document: { path, template } })` — but defers the bulk of the phased procedure to the reference, leaving minor gaps. Not a 5 because some key execution detail lives one hop away.

4 / 5

Workflow Clarity

Sequences both modes explicitly (generate: survey → overview → architecture → modules → flows → concepts → link-graph audit; refresh: diff source_commit..HEAD → update affected pages → re-stamp) with MUST re-stamp and append-one-entry-per-run checkpoints and a STOP-gated procedure. Not a 4 because validation/checkpoints are explicit and clearly marked.

5 / 5

Progressive Disclosure

Clear overview body that points to a single well-signaled one-level reference (references/generate-and-refresh.md, linked repeatedly and verified to exist), with content appropriately split. Matches the score-5 anchor for clean overview-plus-reference structure.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states both what the skill does and when to use it, with an explicit boundary against the related open-knowledge skill. Trigger terms and specificity are good though not maximally comprehensive.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'generate or refresh a wiki', carrying per-folder rules, freshness + log discipline, and bundling the generate/refresh procedure — with only minor coverage gaps. It falls just short of a comprehensive list of distinct operations, so it is not a 5.

4 / 5

Completeness

Explicitly answers both 'what' (an agent-authored, source-grounded wiki with per-folder rules, freshness/log discipline, audience/depth knobs) and 'when' ('Read when the project has a wiki/ knowledge base... or when asked to generate or refresh a wiki') with concrete trigger phrases. Clearly matches the score-5 anchor.

5 / 5

Trigger Term Quality

Includes natural triggers users would say — 'generate or refresh a wiki of this codebase' and 'when the project has a wiki/ knowledge base' — with good keyword coverage. It lacks some broader synonyms/variations, keeping it just below a 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (the codebase-wiki pack) with an explicit boundary statement — 'Complements the platform open-knowledge skill; does not replace it' — and distinct triggers, giving minimal conflict risk. Matches the score-5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
inkeep/open-knowledge
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.