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.

68

Quality

83%

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

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

A highly actionable, well-sequenced skill body with concrete commands, thresholds, and fallback paths. Its weaknesses are length/redundancy and a lack of progressive disclosure — the insights mode and full report template could be offloaded to reference files.

Suggestions

Move the large Insights Mode section into a separate reference file (e.g. references/INSIGHTS.md) and summarize it in SKILL.md with a one-level-deep pointer, reducing the monolithic length.

De-duplicate the token-footprint guidance: keep the methodology in Step 3b and reference it from the Step 3 template rather than rendering the full table twice.

Trim or externalize the full manifest JSON example to a reference, retaining only the fields the status/delta logic actually reads.

DimensionReasoningScore

Conciseness

Mostly efficient and domain-specific rather than padded with general knowledge, but the ~460-line body duplicates the token-footprint block (shown in the Step 3 template then re-explained in Step 3b) and embeds a large manifest JSON example that could be tightened.

3 / 5

Actionability

Fully executable guidance throughout: copy-paste `obsidian-wiki graph-analyse` command with flags, explicit glob patterns, concrete thresholds (90 days, 100000 tokens, 4 chars/token), and clear QMD commands with fallback handling.

5 / 5

Workflow Clarity

Clear sequenced steps (Before You Start → Steps 1–4 → Insights) with checklists (priority table, empty state, overflow) and a real feedback loop for QMD (update → embed if stale → verify), but the core read-only report flow lacks explicit validation checkpoints.

4 / 5

Progressive Disclosure

Well-organized into labeled sections, but it is a ~460-line monolithic file with no bundle files; the large Insights Mode block and full report template are inlined content that would read better split into a one-level-deep reference file.

3 / 5

Total

15

/

20

Passed

Description

95%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 strong, third-person description that clearly conveys both capability and trigger conditions with rich natural-language invocations and an explicit distinction from sibling skills. Minor specificity gaps (token footprint, next-action ranking) keep it just short of fully comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions ('what's been ingested, what's pending, and the delta', 'surface top hubs, cross-domain bridges, and orphan-adjacent pages'), but omits token-footprint and the ranked 'What to Do Next' work, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly states both what ('Show the current state of the wiki... delta between sources and wiki content') and when ('Use this skill when the user asks...', 'Also use before deciding whether to append or rebuild') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and variants ('what's the status', 'wiki dashboard', 'show me the delta', 'wiki insights', 'show me the hubs', 'wiki structure') that a user would plausibly say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (wiki audit/delta/insights) with distinct triggers; explicitly distinguishes from wiki-lint ('Complements wiki-lint... by surfacing interesting structure') and from ingest skills, minimizing conflict risk.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

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.