CtrlK
BlogDocsLog inGet started
Tessl Logo

okf-knowledge-base

Open Knowledge Format (OKF) v0.2 guidance. Use when creating, reading, reviewing, or maintaining an OKF bundle; responding to OpenKnowledge `okf` plugin warnings; or choosing types, provenance, links, indexes, or logs.

72

Quality

89%

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.

A tight, well-structured instruction-only skill that conveys OKF semantics efficiently with concrete inline format examples and clear reading/maintenance sequencing. The only gaps are a missing complete worked frontmatter example and an explicit write-time validation checkpoint in the maintenance workflow.

Suggestions

Add one complete worked frontmatter example (type, sources with id, generated/verified, stale_after) so authors can copy the exact shape rather than reassembling it from scattered rules.

In 'Read and maintain a bundle', insert an explicit validation checkpoint — after writing a concept, run the `okf` plugin audit / consult `.ok/okf/*.schema.json` before adding the log entry — to close the validate→fix loop for durable writes.

DimensionReasoningScore

Conciseness

The body is a lean, dense set of bullet rules that assumes Claude knows Markdown/YAML/links and adds only OKF-specific semantics; nearly every token (e.g. the reserved-file rules, the ISO-timestamp constraint) earns its place.

5 / 5

Actionability

Concrete format examples are inline ('## YYYY-MM-DD: Summary', 'stale_after: 2026-12-31T00:00:00Z', 'human:'/'process:' prefixes), but there is no single complete worked frontmatter example for authors to copy, leaving a minor gap.

4 / 5

Workflow Clarity

'Read and maintain a bundle' gives a clear sequence (nearest index.md → inspect frontmatter → follow relevant links → write discoveries back → add log entry) with judgment checkpoints ('trust the bundle; if missing or inconsistent, say so'), but an explicit post-write conformance validation step is only implied via the plugin section.

4 / 5

Progressive Disclosure

Under ~50 lines with no external references needed and no bundle files, the content is cleanly split into four well-signaled sections (Core rules, Authoring judgment, Read and maintain, okf plugin), meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

92%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, third-person description that pairs a clear domain statement with an explicit, multi-clause 'Use when' trigger and concrete sub-areas. It is comprehensive on completeness, specificity, and distinctiveness, with only minor gaps in natural-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating, reading, reviewing, or maintaining an OKF bundle; responding to OpenKnowledge okf plugin warnings; or choosing types, provenance, links, indexes, or logs' — giving comprehensive coverage of the domain's tasks rather than generic verbs alone.

5 / 5

Completeness

Explicitly answers both what ('Open Knowledge Format (OKF) v0.2 guidance') and when (a full 'Use when...' clause enumerating concrete trigger situations), matching the anchor for clear what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Good natural-term coverage for the niche ('OKF bundle', 'okf plugin warnings', 'types, provenance, links, indexes, or logs'); a few natural variations (e.g., 'knowledge bundle', file extensions) are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('OKF bundle', 'OpenKnowledge okf plugin warnings') with distinct triggers and minimal overlap with unrelated skills.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

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.