CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-writing

Use when creating or substantially editing wiki pages: language, tone, structure, page types, linking discipline, what separates useful articles from filler.

59

Quality

68%

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 ./skills/builtin/wiki-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured, actionable wiki-writing standards document with concrete commands, formats, rules, and good/bad examples. Its primary weakness is conciseness: a meaningful fraction restates general writing principles Claude already knows, even though they are reframed as wiki house style.

Suggestions

Trim the general writing advice in Language (voice/tense, sentence-paragraph discipline, Words to Watch) to the wiki-specific deviations, since Claude already knows active-voice and plain-language basics.

Add an explicit post-edit verification step (e.g., re-read the page or check that wiki links resolve) to close the workflow-clarity validation gap.

Consider extracting the page-type definitions into a reference file so the main body reads as an overview with one-level-deep detail.

DimensionReasoningScore

Conciseness

The body is purposeful and example-driven, but sizable portions of the Language section (active vs passive voice, plain language, one-idea-per-sentence, the 'Words to Watch' and 'Avoid' lists) restate general writing principles Claude already knows; while recontextualized as wiki house style, they could be tightened, matching the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

Guidance is concrete and actionable for an instruction-only skill: specific commands (wiki_list, wiki_search, wiki_read), the link format [display text](wiki:slug), numeric rules (3-5 related slugs, 15-25 word average), and good/bad examples covering tone, leads, links, and edit summaries; a few areas stay principle-based rather than step-based, holding it at 4.

4 / 5

Workflow Clarity

Clear sequences exist for 'Before Writing' (search, decide expand vs create) and 'Editing Existing Pages' (read full page, match style, verify corrections, preserve info) with real checkpoints (read-before-edit, verify-before-apply, six-month accuracy test); the only gap is the absence of an explicit post-edit verification/re-read loop, so it stays at 4.

4 / 5

Progressive Disclosure

The single file is well-organized with logical ## and ### headings, no nested references, and easy navigation; with no bundle files present, content is appropriately kept inline in one cohesive standards document, but the page-type definitions or words-to-watch lists could in principle be split out, leaving minor organization gaps at 4.

4 / 5

Total

15

/

20

Passed

Description

70%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 well-structured with an explicit 'Use when' trigger, natural keywords, and a distinct wiki niche. Its main weakness is that the capability is conveyed as a list of editorial aspects rather than several concrete, executable actions.

Suggestions

Lead with concrete actions (e.g., 'Draft, structure, and link wiki pages') before the topical list so the 'what' reads as capabilities rather than aspects.

Add a couple of natural synonyms such as 'wiki article' or 'knowledge-base page' to broaden trigger coverage.

Tighten the colon-list into a tighter phrase so the description scans as actions first, concerns second.

DimensionReasoningScore

Specificity

Names the domain ('wiki pages') and two actions ('creating or substantially editing') but the colon-list ('language, tone, structure, page types, linking discipline, what separates useful articles from filler') enumerates topical aspects rather than several concrete executable actions, so it is not comprehensive enough for a 4.

3 / 5

Completeness

Both 'what' (the colon-list of editorial concerns) and 'when' ('Use when creating or substantially editing wiki pages') are present and explicit; the 'what' is conveyed as a list of aspects rather than a crisp action statement, so it does not reach the fully concrete 5 anchor.

4 / 5

Trigger Term Quality

The natural phrase 'creating or substantially editing wiki pages' is exactly what a user would say, with good coverage of 'wiki pages' and the create/edit verbs; a few synonyms (wiki article, knowledge base, documentation) are missing, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

'Wiki pages' is a clear, fairly distinct niche with an explicit trigger, but the craft/process framing carries minor overlap risk with general writing or documentation skills, placing it just below the minimal-conflict 5 anchor.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository
spacedriveapp/spacebot
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.