CtrlK
BlogDocsLog inGet started
Tessl Logo

wagneripjr/okf-maintain

Adopt and maintain an Open Knowledge Format v0.2 documentation bundle: frontmatter, generated indexes, a fail-closed conformance check, and coverage that names every unindexed document

92

1.71x
Quality

93%

Does it follow best practices?

Impact

91%

1.71x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%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 body is highly actionable with explicit validation-gated workflows and clean one-level-deep references to a real bundle. Its main weakness is conciseness: substantial argumentative rationale inflates the token budget beyond what the instructions strictly require.

Suggestions

Trim the justificatory prose in sections like 'A manifest selects the row shape' and the plugin-payload argument to the operative rule plus one sentence; move the full rationale into a reference file.

Convert long rhetorical sentences (e.g. 'a guard whose condition nothing can satisfy is a defect wearing a guard's clothes') into a plain statement of the rule so the skill reads as instruction rather than argument.

Consider consolidating the two workflow sections' shared commands so the same exit-code and validation guidance is stated once instead of repeated across sections.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no padding about what markdown or YAML is) and is dense, but much of it is argumentative prose justifying design choices — e.g. 'a guard whose condition nothing can satisfy is a defect wearing a guard's clothes' — which is accurate yet noticeably more than the task needs, fitting the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout — 'node "<skill-dir>/scripts/okf.mjs" index <bundle-root>', 'check', 'coverage', 'wire', '--describe requirements=...', with concrete exit codes and a real marker block — covering the common cases.

5 / 5

Workflow Clarity

Two explicit numbered workflows (adopting and maintaining) with concrete validation checkpoints — 'check . must exit 0', 'coverage . must exit 0', and 'Treat 77 as a failure to verify, never as a pass' — including feedback loops for the destructive/batch operations (git rm log.md, index overwrites).

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled one-level-deep references to real bundle files — 'references/frontmatter.md', 'references/index-format.md', 'references/adoption.md', and 'scripts/okf.mjs' (all present on disk) — with no nested reference chains.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: it states a comprehensive set of concrete actions, provides explicit natural-language triggers, and draws sharp negative boundaries. It fully answers both 'what' and 'when' with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'bootstraps a conformant tree', 'stamps and repairs YAML frontmatter', 'regenerates every index.md bottom-up', 'excludes paths ... via .okfignore', 'removes log.md and strips changelog/history sections', 'wires CLAUDE.md/AGENTS.md/GEMINI.md', plus conformance and coverage checks — giving comprehensive coverage with no gaps.

5 / 5

Completeness

Clearly answers both what (the enumerated action list) and when (the explicit 'Triggers on:' phrases), and adds negative scope ('NOT for writing a document's body'), matching the anchor that requires concrete trigger phrases for both.

5 / 5

Trigger Term Quality

An explicit 'Triggers on:' block gives six natural user phrases including 'set up OKF', 'regenerate the docs index', and 'our documentation keeps drifting', covering the natural ways a user would ask for this.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OKF v0.2 bundle maintenance) with explicit 'NOT for ...' boundaries against the adr skill and body-authorship, minimizing conflict risk with adjacent documentation skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents