CtrlK
BlogDocsLog inGet started
Tessl Logo

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

67

Quality

80%

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

78%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 body is actionable and well-structured with executable bash and a clear sequenced workflow plus a validation checkpoint. Its main weakness is moderate redundancy in presenting the invocation fallback three times.

Suggestions

Collapse the three presentations of the executable/clone invocation into a single if/elif/else block to remove redundancy and tighten conciseness.

Replace the comment-only else branch with a concrete echo/print command so the failure path is fully copy-paste executable.

Add an explicit validation step after the CLI runs (e.g., checking that stdout is non-empty and budget/citations are present) to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no conceptual padding, but the executable/clone invocation is presented three times (separate routes then a combined if/elif/else), a minor redundancy that could be tightened.

4 / 5

Actionability

Concrete, copy-paste-ready bash commands cover topic and recent modes with an explicit executable-or-clone fallback; minor gaps are the `<topic>` placeholder requiring substitution and the comment-only else branch lacking an echo command.

4 / 5

Workflow Clarity

A numbered 'Before You Start' sequence, 'Execute', and 'Return' give a clear order with a path-canonicalization validation checkpoint and fallback error guidance, though validation is not exhaustive across every step.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a single well-signaled one-level-deep reference (the Config Resolution Protocol in llm-wiki/SKILL.md) and no nested references; no bundle files are needed for this single-purpose skill.

5 / 5

Total

17

/

20

Passed

Description

82%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 well-formed: third-person voice, clear 'what' and 'when', and a distinct niche anchored to Obsidian vaults. Its only weakness is that it describes a single composite action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

"Produce a token-bounded, citation-ready context slice from an existing Obsidian vault" names the domain and one concrete action with rich attributes, but offers only a single action verb rather than a comprehensive list of capabilities.

3 / 5

Completeness

It explicitly answers 'what' (produce a token-bounded, citation-ready context slice from an Obsidian vault for a downstream agent) and 'when' with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"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'" supplies five natural trigger phrases users would actually say, though it lacks synonyms and file extensions for full coverage.

4 / 5

Distinctiveness Conflict Risk

The Obsidian-vault context-packing niche with vault-specific triggers ('use my vault as context', 'pack the wiki for my agent') is clearly distinct from other skills with minimal overlap risk.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.