CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-status

Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an overview of their knowledge base health and completeness. Also use before deciding whether to append or rebuild. Includes an insights mode triggered by "wiki insights", "what's central", "show me the hubs", "central pages", "what's connected", "wiki structure" — analyzes the shape of the wiki itself to surface top hubs, cross-domain bridges, and orphan-adjacent pages. Also includes an equilibrium mode triggered by "is my vault at equilibrium", "wiki equilibrium", "is maintenance done", "is the vault converged", or "are my skills fighting" — runs every maintenance skill's audit-only pass and reports whether any of them still has a pending change.

73

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

88%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 highly actionable and clearly sequenced with strong validation and feedback loops, and it avoids over-explaining known concepts. Its weaknesses are length-driven redundancy in the token-footprint and next-step sections and the absence of any bundle split for the two large mode blocks.

Suggestions

Consolidate the token-footprint material: render the table once and reference it from Step 3b (or vice versa) to remove the duplicated specification.

Split the Insights and Equilibrium modes into one-level-deep reference files (e.g. INSIGHTS.md, EQUILIBRIUM.md) so SKILL.md stays an overview, improving progressive disclosure for this large multi-mode skill.

Tighten Step 4 by either keeping the prose signal-gathering list or the priority table, not both fully fleshed out, to reduce the lowest-scoring conciseness dimension.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no basic-concept explanations) and uses dense tables and exact commands, but is very long with some redundancy — the token-footprint table is rendered in Step 3 then re-specified in Step 3b, and 'What to Do Next' signals are gathered then re-summarized in a table — fitting the 'efficient with minor instances that could be trimmed' anchor rather than the lean top anchor.

4 / 5

Actionability

Fully executable guidance: exact glob patterns, exact commands ('obsidian-wiki graph-analyse "$OBSIDIAN_VAULT_PATH" --pretty --snapshot --diff-against ...'), exact thresholds (cohesion < 0.15, >=5 incoming links, >=90 days), exact scoring bonuses (+3, +2, +2), and copy-paste-ready output templates covering the common cases.

5 / 5

Workflow Clarity

Steps are clearly sequenced (Before You Start -> Steps 1-4 -> Step 3b) with explicit validation/feedback checkpoints — when-to-skip guards, empty-state and overflow handling, oscillation detection across runs, lost_incoming rename detection, and 'if any player's audit can't be run cleanly, omit that row and say which player' error handling — matching the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the skill is a single well-sectioned SKILL.md with clearly signaled external references (llm-wiki/SKILL.md, scripts/manifest.py, WRITING.md), giving good structure; the gap keeping it from the top anchor is that the large Insights and Equilibrium mode blocks are inlined rather than split into one-level-deep reference files.

4 / 5

Total

18

/

20

Passed

Description

96%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 specific, trigger-rich, and fully answers what-and-when in third person across three clearly delineated modes. Its only weakness is mild overlap risk with closely related sibling maintenance skills on a few broad phrases.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across three modes — 'Show the current state', 'analyzes the shape of the wiki itself to surface top hubs, cross-domain bridges, and orphan-adjacent pages', 'runs every maintenance skill's audit-only pass and reports' — with comprehensive coverage, matching the anchor for listing multiple specific concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' (show state, compute delta, analyze graph shape, run audit-only passes) and 'when' ('Use this skill when the user asks...', 'Also use before deciding whether to append or rebuild') with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

Comprehensive quoted natural-language triggers with many synonyms — 'what's the status', 'how much is ingested', 'what's left to process', 'show me the delta', 'what changed since last ingest', 'wiki dashboard' plus insights and equilibrium phrases a user would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (wiki status/delta/insights/equilibrium) with distinct triggers, but the sibling maintenance skill set (wiki-lint, wiki-dedup, cross-linker, tag-taxonomy, wiki-query) creates minor overlap risk on broad phrases like 'wiki structure' and 'wiki dashboard', so it sits just below the minimal-conflict anchor.

4 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (559 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
Ar9av/obsidian-wiki
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.