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.

70

Quality

88%

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

86%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.

The content is a well-engineered skill body: lean and operational, with concrete commands, a copy-paste log template, an explicit phase sequence, and clean single-level delegation to a real, well-structured reference file. The main residual gap is that executable procedure details (STOP-gate specifics, per-phase commands) live entirely in the reference, which is by design but leaves the body one step short of fully self-contained guidance.

DimensionReasoningScore

Conciseness

The body is dense and load-bearing throughout — the wiki layout, knob values, per-folder rules, and log-entry shape are all operational, with no padding or explanation of concepts Claude already knows ('DeepWiki, but living in the repo' is a one-clause aside, not a tutorial). Every token earns its place, matching the 5 anchor.

5 / 5

Actionability

Concrete, executable guidance throughout — a copy-paste log-entry markdown template, 'Create with write({ document: { path, template: "<name>" } })', 'diff source_commit..HEAD', explicit knob enums. It sits at the 4 anchor because the bulk of the executable procedure (phase commands, STOP gates) is delegated to references/generate-and-refresh.md rather than present inline, so it is not fully copy-paste-ready for the common cases by itself.

4 / 5

Workflow Clarity

The sequence is explicit ('survey → overview → architecture → modules → flows → concepts → link-graph audit'), mode auto-detection is concrete (stubbed vs. stamped source_commit), and validation checkpoints are named (STOP-gated procedure, link-graph audit, brokenLinks feedback). It fits the 4 anchor — most checkpoints present, with their detailed execution living in the reference rather than fully inline as the 5 anchor requires.

4 / 5

Progressive Disclosure

A clean overview body that delegates exactly one level deep to references/generate-and-refresh.md (verified to exist and to reference no further markdown files), with the delegation clearly and repeatedly signaled ('Don't free-hand it — read references/generate-and-refresh.md', 'the full rules ... live in references/generate-and-refresh.md'). Content is appropriately split and easy to navigate, matching the 5 anchor.

5 / 5

Total

18

/

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.

The description is strong: it states a clear what, an explicit and concrete two-condition 'Read when' trigger, and proactively disambiguates against the nearest competing skill. Trigger terms are natural and specific to the wiki workflow, with only minor synonym gaps.

DimensionReasoningScore

Specificity

Names the domain and several concrete capabilities ('generate or refresh a wiki', 'carries the per-folder rules and freshness + log discipline', 'summarizes the audience/depth knobs and source-reference convention'). It lists multiple specific actions with only minor gaps, matching the 4 anchor rather than the fully comprehensive action list of the 5 anchor.

4 / 5

Completeness

Explicitly answers both: what ('an agent-authored, source-grounded wiki of the surrounding codebase' plus what the skill carries) and when ('Read when the project has a wiki/ knowledge base ... plus wiki/OVERVIEW.md, or when asked to generate or refresh a wiki of this codebase') with concrete trigger phrases — a direct match to the 5 anchor.

5 / 5

Trigger Term Quality

Contains natural trigger phrases users would say — 'wiki', 'generate or refresh a wiki of this codebase', folder names (architecture/, modules/, flows/, concepts/, guides/), 'OVERVIEW.md'. Coverage is good but misses synonyms users might reach for ('documentation', 'DeepWiki'), so it sits below the synonym-complete 5 anchor and clearly above the 3 anchor's missing variations.

4 / 5

Distinctiveness Conflict Risk

A clear niche (repo-hosted codebase wiki with its own directory signature) with distinct triggers, plus explicit disambiguation from the adjacent platform skill ('Complements the platform open-knowledge skill; does not replace it') — minimal conflict risk, matching the 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.

Validation — 14 / 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.