knowledge-wiki

Manage the personal knowledge wiki. Use when the user shares articles, documents, or asks to organize knowledge; when a conversation produces insights worth preserving as structured knowledge; or when the user asks about the knowledge base.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%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 content is exceptionally lean and actionable, with concrete templates and a clear three-operation workflow. The only minor gap is the absence of explicit validation/verification steps after ingest and synthesize operations.

Suggestions

Add an explicit verification step after ingest/synthesize (e.g. 'Verify the new page appears in index.md and that cross-reference targets exist') to strengthen the workflow's feedback loop.

Clarify how to handle a broken or missing cross-reference when linking to pages that should already exist, so recovery is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it states mechanics (paths, formats, naming) without explaining what a knowledge base or markdown is, and every line earns its place.	5 / 5
Actionability	Concrete, copy-paste-ready templates for page, index, and log formats with exact file paths and explicit naming rules ('lowercase kebab-case', 'knowledge/<category>/<slug>.md') cover the common cases.	5 / 5
Workflow Clarity	The three core operations are clearly numbered and sequenced with index/log update checkpoints, but ingest/synthesize involve file creation without explicit validation (e.g. verifying the new page links resolve or that index was updated), so it sits just below a 5.	4 / 5
Progressive Disclosure	A single self-contained overview with well-organized sections and no bundle files; for a skill under 50 lines needing no external references, this structure is appropriately navigable.	5 / 5
	Total	19 / 20 Passed

Description

83%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 answers both what the skill does and when to use it, with natural trigger phrases and a recognizable niche. It is slightly less distinctive and could use more synonym coverage for trigger terms.

Suggestions

Add common synonyms and natural phrasings users might say (e.g. 'notes', 'research', 'save this for later', 'remember this') to broaden trigger coverage.

Tighten distinctiveness by emphasizing the persistent knowledge-base index/graph mechanics that separate this from generic note-taking skills.

Dimension	Reasoning	Score
Specificity	Names the domain (knowledge wiki) and concrete actions ('Manage', 'organize knowledge', 'shares articles, documents', 'preserving as structured knowledge'), though actions are framed around input types more than distinct operations.	4 / 5
Completeness	Explicitly states what it does ('Manage the personal knowledge wiki') and when to use it via three distinct 'Use when...' trigger clauses, satisfying both halves concretely.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('shares articles, documents, or asks to organize knowledge', 'asks about the knowledge base'), but lacks synonyms like 'notes', 'research', or file extensions; coverage is good but not exhaustive.	4 / 5
Distinctiveness Conflict Risk	The 'personal knowledge wiki' niche is fairly distinct, but 'organize knowledge' and 'shares articles/documents' could overlap with general note-taking or file-management skills, leaving minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 4 missing, 1 deeper-than-1-level, 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: zhayujie/CowAgent
Path: skills/knowledge-wiki/SKILL.md
Commit: ed5bb34

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.