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.

64

Quality

81%

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

82%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.

An excellent, disciplined style-guide skill: every rule is paired with concrete Good/Bad examples, real tool commands are given, and the create-vs-edit decision workflow is explicit. The only slack is a modest amount of generic writing advice Claude already knows, which could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

The body is dense and example-driven with no tutorial padding, but it includes general writing wisdom Claude already knows ("One idea per sentence. One theme per paragraph," "Vary sentence length for rhythm"), keeping it at 'efficient; minor instances that could be trimmed' rather than anchor 5.

4 / 5

Actionability

Fully concrete instruction-only guidance: real commands (wiki_list, wiki_search, wiki_read), exact link syntax '[display text](wiki:slug)', and paired Good/Bad examples for tone, lead sentences, headings, and edit summaries covering the common cases.

5 / 5

Workflow Clarity

A clear decision workflow ('Before Writing': check existing coverage → expand vs. create → six-month durability test) and a coherent editing sequence (read the full page → match style → verify corrections → preserve content). Checkpoints exist but as implicit criteria rather than explicit validate-and-retry loops, placing it between anchors 4 and 5.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well organized under clear ##/### sections with nothing that clearly demands separation. The word-list and style-rule sections are sizable enough that a reference file could be argued, matching 'good structure; most content is appropriately placed; minor organization gaps.'

4 / 5

Total

17

/

20

Passed

Description

73%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 focused, well-targeted description with an explicit trigger clause and a distinct wiki niche. Its main weakness is that the 'what' is expressed as a list of topics rather than concrete actions, which slightly undersells the skill's capabilities. It stays appropriately concise without fluff or over-claims.

Suggestions

Convert the topic list into 2-3 concrete capability actions (e.g., 'Structure wiki pages with encyclopedic tone, choose the right page type, and apply linking discipline' or similar) so the 'what' reads as capabilities rather than topics.

Add a few natural trigger synonyms users would say, such as 'write an article,' 'add to the wiki,' or 'documentation page,' to broaden keyword coverage.

State the tool context explicitly (e.g., mention the wiki tools or page types the skill operates on) to sharpen the what-component for completeness.

DimensionReasoningScore

Specificity

The description names concrete sub-areas ("language, tone, structure, page types, linking discipline") but the only actions are "creating or substantially editing" — these are topics rather than the enumerated concrete capability actions of the level-4 anchor, so it sits at 'names domain and concrete actions but not comprehensive.'

3 / 5

Completeness

Both elements are present: an explicit "Use when creating or substantially editing wiki pages" trigger and a topic list conveying what the skill covers. It falls short of 5 because the 'what' is delivered as a colon-separated topic list rather than an explicit capability statement.

4 / 5

Trigger Term Quality

"creating or substantially editing wiki pages" is the natural phrase a user would say, with strong topic keywords; common variants like "documentation," "article," or "add to the wiki" are missing, matching 'good keyword coverage; a few natural terms missing.'

4 / 5

Distinctiveness Conflict Risk

"Wiki pages" is a clear, repeated niche with distinct triggers and minimal conflict risk — a user mentioning wiki pages would unambiguously intend this skill over any general writing or documentation skill.

5 / 5

Total

16

/

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: 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.