CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-init

One-time, guided setup of a standalone LLM-maintained wiki — a Karpathy "LLM Wiki" style knowledge base for a problem domain and your general architecture best practices. Scaffolds an external wiki vault (its own git repo) with /ingest, /query, /lint commands and a conventions doc. Use when a developer wants to start, create, bootstrap, or initialize a wiki / second-brain / knowledge base to understand a problem space before building. The front of the Human Loop's Understanding phase.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A well-structured guided-setup skill: clear sequenced workflow with approval/confirm checkpoints, excellent progressive disclosure to real reference and asset files, and concrete scaffolding guidance. The only drag is conciseness — the "external, own-repo" invariant is restated several times and could be tightened.

Suggestions

Consolidate the "wiki is external, its own git repo, never the app codebase" invariant to one authoritative statement (e.g. Preconditions) and reference it rather than restating it in P2, Step 0, Step 4, and Hard nevers.

Inline the one-line purpose of each generated command (ingest/query/lint) in Step 3 so the in-skill reader needn't open assets/ just to understand the scaffold, while still delegating full bodies to the templates.

Trim the P1–P8 philosophy block by leading each principle with its rule and dropping the secondary framing sentences, preserving the load-bearing disciplines in fewer tokens.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic-concept padding) and every principle is load-bearing, but the "external / own repo / never write into the app codebase" point is restated across the intro, P2, Preconditions, Step 0, Step 4, and Hard nevers; not a 3 because the repetition is intentional emphasis rather than unrelated padding, and not a 5 because some of those restatements could be trimmed.

4 / 5

Actionability

Step 3 gives a concrete directory tree ("wiki/{concepts,entities,workflows,sources,indexes,inbox}/", "_meta/ingest-log.md") and specific template-render and git steps; not a 5 because it delegates the executable command bodies to assets/ rather than inlining them, leaving minor gaps for the in-skill reader, and not a 3 because the guidance given is concrete and executable rather than pseudocode.

4 / 5

Workflow Clarity

Steps 0–5 are clearly sequenced with explicit validation checkpoints — Step 2 "Stop and wait for approval, unless --yolo", Step 4 "Confirm with the user before committing", and the explain→confirm→act→feedback loop plus a re-run/diff idempotency section; not a 4 because checkpoints and feedback loops are explicit rather than implicit.

5 / 5

Progressive Disclosure

SKILL.md is an overview pointing one level deep to real, clearly-signaled references ("See references/llm-wiki-pattern.md", "load references/domain-discovery.md when you reach Step 1") and templates ("render assets/WIKI-CONVENTIONS.md.template"), all of which exist; not a 4 because navigation is clean and content is appropriately split with no nesting.

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.

A strong, well-targeted description: it states concrete scaffolding actions, gives an explicit Use-when clause rich in natural synonyms, and carves out a distinct niche with minimal conflict risk. Every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

"Scaffolds an external wiki vault (its own git repo) with /ingest, /query, /lint commands and a conventions doc" names the domain plus multiple concrete scaffolding actions with specific artifacts, matching the comprehensive-coverage anchor; not a 4 because coverage of what gets created is complete rather than gapped.

5 / 5

Completeness

It explicitly answers both what ("One-time, guided setup... Scaffolds an external wiki vault...") and when ("Use when a developer wants to start, create, bootstrap, or initialize...") with concrete trigger phrases; not a 4 because the when clause is explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

"Use when a developer wants to start, create, bootstrap, or initialize a wiki / second-brain / knowledge base" provides comprehensive natural-term coverage with multiple synonyms a user would actually say; not a 4 because synonyms are thorough rather than missing a few.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — standalone LLM-maintained wiki, its own git repo, "front of the Human Loop's Understanding phase" — with triggers (wiki / second-brain / knowledge base init) unlikely to fire other skills; not a 4 because conflict risk is minimal, not merely reduced.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tdg-ninja/context-specs-factory-ai
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.