CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-init

Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/wiki-init/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 an exemplary lean overview: concrete commands, examples, an exact output tree, and clean one-level-deep pointers with zero padding. Its only real weakness is the destructive --force flag with no validation/confirmation guidance, which caps workflow clarity. Adding a safety checkpoint for overwriting non-empty directories would raise the content score substantially.

Suggestions

Add a validation checkpoint before --force overwrites a non-empty directory (e.g., list existing files and require explicit user confirmation, or suggest backing up the directory first).

Include a brief post-run verification step (e.g., confirm the expected tree was created before reporting success).

Name the schema file(s) or summarize their contents so the promise "installs the schema file(s)" is concrete without reading the script.

DimensionReasoningScore

Conciseness

The ~57-line body is lean: three usage forms, three concrete examples, a file tree, a 3-item next-steps list, and two pointers. No concept explanations, no padding, and it fully assumes Claude's competence — every token earns its place.

5 / 5

Actionability

Commands are concrete and copy-paste ready with real examples ("/wiki-init ~/vaults/research --topic 'LLM interpretability'") plus an exact target directory tree. Minor gaps: "three-layer structure" and the schema/template contents are referenced but never specified, and the script's interface is not shown.

4 / 5

Workflow Clarity

The single init action is unambiguous and post-init steps are sequenced (open vault, drop source, run /wiki-ingest), but the skill offers "--force # overwrite non-empty dir" — a destructive operation — with no validation or confirmation checkpoint. Per the rubric's precedence rule, missing validation for a destructive flag caps workflow clarity at 3 even for a simple skill.

3 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references (Script section pointing to init_vault.py, Skill Reference pointing to the full SKILL.md), and template content is appropriately delegated to .templates/ in the vault rather than inlined. Navigation is trivial.

5 / 5

Total

17

/

20

Passed

Description

58%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 clearly and concretely states what the skill creates, but omits any "Use when..." trigger guidance and leans on niche jargon ("three-layer structure") without natural synonyms a user would say. It is distinct from other skills yet under-specified for triggering. Strengths are concrete deliverables and niche vocabulary; weaknesses are trigger phrasing and completeness.

Suggestions

Add an explicit trigger clause, e.g., "Use when initializing or setting up a new LLM Wiki vault, or when the user wants to create a fresh wiki for a project or research topic."

Include natural synonyms such as "create", "set up", "initialize", and "new vault" so users' phrasings match the trigger terms.

Briefly clarify what the "three-layer structure" consists of (raw sources, wiki pages, synthesis) so the description's promise is concrete.

DimensionReasoningScore

Specificity

"Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates" lists several concrete deliverables (structure, schema files, templates), matching the 'several specific actions; minor gaps' anchor. It is not 5 because "three-layer structure" is unexplained jargon and coverage of created artifacts (index, log, tool config files) is partial.

4 / 5

Completeness

The "what" is clear and concrete (bootstrap vault with structure, schemas, templates), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. The trailing usage string documents invocation syntax, not when the skill should trigger.

3 / 5

Trigger Term Quality

Relevant keywords exist ("Bootstrap", "LLM Wiki", "vault", "init") but natural user phrasings like "set up", "create", or "initialize a new wiki" are absent, and there is no explicit trigger sentence. It is not 2 because multiple genuinely relevant, non-generic keywords are present.

3 / 5

Distinctiveness Conflict Risk

"LLM Wiki vault" establishes a clear niche with distinct vocabulary and minimal conflict risk; only minor overlap with closely related sibling skills (e.g., wiki-ingest) is plausible. Not 5 because the description does not explicitly differentiate it from those related suite skills.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/wiki-init/SKILL.md

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.