CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-context-pack

Produce a token-bounded, citation-ready context slice from an existing Obsidian vault for a downstream agent or task. Use for "/wiki-context-pack", "use my vault as context", "context slice for X", "pack the wiki for my agent", or "bounded context for Y".

Quality

84%

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

73%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 tight, operational single-file skill with an unambiguous read-only workflow and explicit failure handling. Its main costs are redundancy — the same invocation repeated four times — and examples that hardcode the default budget instead of the parsed value.

Suggestions

Consolidate the repeated invocation examples: keep the single if/elif/else fallback block and drop the duplicate plain-command snippets, noting flag substitutions once.

Use the parsed '--budget N' value in the command templates instead of hardcoding '--budget 8000', which is already documented as the default.

Replace the comment-only else branch with the exact user-facing message to emit when neither the executable nor the clone is available.

DimensionReasoningScore

Conciseness

No concept padding and a lean overall structure, but the core command ('obsidian-wiki context-pack --vault "$OBSIDIAN_VAULT_PATH" ... --budget 8000') is repeated four times across the plain examples and the if/elif/else fallback block, which could be consolidated — matching anchor 3's 'could be tightened' rather than anchor 4's minor trims.

3 / 5

Actionability

Concrete, executable bash including a complete executable-or-clone fallback chain, matching anchor 4; minor gaps keep it from anchor 5: the else branch contains only comments rather than a ready message, and examples hardcode '--budget 8000' instead of the parsed '--budget N'.

4 / 5

Workflow Clarity

Clear numbered sequence (resolve config, read AGENTS.md, canonicalize vault path, parse args) into execute and return, with explicit error checkpoints ('If this fails, report that the configured vault path is invalid'; fallback guidance 'pip install obsidian-wiki'), matching anchor 5; it is a read-only, non-destructive skill so the validation cap does not apply.

5 / 5

Progressive Disclosure

Well-organized sections (Before You Start / Execute / Return) with no bundle files to disclose and a clearly signaled one-level reference to llm-wiki/SKILL.md, matching anchor 4; the body is ~80 lines, above the under-50-line simple-skill case that would justify a 5, and the cross-skill dependency cannot be verified from this bundle.

4 / 5

Total

16

/

20

Passed

Description

87%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 description: it states a concrete, precisely qualified capability and follows it with an explicit 'Use for' clause of natural trigger phrases. The only weaknesses are placeholder-style triggers ('context slice for X', 'bounded context for Y') and missing a few natural synonyms.

Suggestions

Replace the abstract 'context slice for X' / 'bounded context for Y' placeholders with concrete example utterances a user would actually say.

Add one or two common synonyms (e.g. 'wiki context', 'Obsidian vault as context') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and a precisely characterized action ('Produce a token-bounded, citation-ready context slice from an existing Obsidian vault for a downstream agent or task'), matching anchor 4's several-specific-actions-minus-coverage; it is a single action rather than the multiple distinct actions of anchor 5, but far more concrete than anchor 3's generic domain-plus-action.

4 / 5

Completeness

It explicitly answers both 'what' (produce a token-bounded, citation-ready context slice from an existing Obsidian vault for a downstream agent) and 'when' ('Use for "/wiki-context-pack", "use my vault as context", ...') with concrete trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'use my vault as context', 'context slice for X', and 'pack the wiki for my agent' give good keyword coverage, but the 'X'/'Y' placeholders are abstract and obvious synonyms (e.g. 'wiki context', 'Obsidian context') are missing, falling short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The Obsidian-vault-to-bounded-context-pack niche with slash-command and vault-specific triggers is clearly distinct from other skills with minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Ar9av/obsidian-wiki

Path

.skills/wiki-context-pack/SKILL.md

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.