CtrlK
BlogDocsLog inGet started
Tessl Logo

cross-linker

Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.

73

Quality

91%

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.

A well-engineered, highly actionable skill body: concrete code, a scored candidate pipeline with confidence gating, and a real safety checkpoint (git snapshot before writes) for a destructive batch operation. The main improvement lever is conciseness — a few explanatory asides and the dense inline scoring/affinity tables could be trimmed or extracted into a reference file.

Suggestions

Tighten prose asides (e.g., 'This is your vocabulary — every entry in this table is a valid wikilink target') and move the Step 3 scoring table and Step 5 affinity rules into a references/ file to reduce the main body's token load.

The diacritic-normalization rule is useful but the inline explanation of NFKD decomposition could be shortened to the single command line Claude needs.

Consider a short 'When NOT to run' note so the skill is not triggered on read-only linting requests that belong to wiki-lint.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no padding about what wikilinks/Obsidian are — with concrete tables for scoring signals, confidence labels, and relationship inference; a few prose asides like 'This is your vocabulary' could be trimmed, keeping it just below the lean anchor 5.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste bash for the git pre-write snapshot and QMD refresh, exact point values in the scoring table, before/after markdown examples, and a concrete NFKD normalization rule, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints — a pre-write git snapshot that aborts the run on failure, confidence labels that gate which candidates are acted on, and a QMD failure-handling feedback loop — satisfying the explicit-validation anchor for a destructive batch operation.

5 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with one-level-deep references to a sibling skill (llm-wiki/SKILL.md for Retrieval Primitives, Writing Profile, Config Resolution, Link Format) and no nested references; not a 5 because no bundle files exist and some dense inline reference material (scoring/affinity tables) could live in a separate file.

4 / 5

Total

18

/

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 description: it states concrete capabilities, gives exhaustive natural-language triggers, and explicitly contrasts itself with the related wiki-lint skill to avoid misfiring. Minor specificity gaps (e.g., no mention of the affinity/promotion or typed-relationship features) keep it just off a perfect specificity score.

DimensionReasoningScore

Specificity

Names the domain ('Obsidian wiki') and several concrete actions — 'discover missing cross-references between pages' and 'actually modifies pages to add links' — with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the single-action anchor 3.

4 / 5

Completeness

Explicitly answers both what (scan wiki, discover missing cross-references, modify pages to add links) and when via a clear 'Use this skill when...' clause with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and paraphrases — 'link my pages', 'find missing links', 'cross-reference', 'connect my wiki', 'add wikilinks', 'orphan pages', 'my wiki feels disconnected' — matching the comprehensive-coverage anchor; not a 4 because no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cross-linking the Obsidian wiki) with distinct triggers and an explicit contrast — 'unlike wiki-lint which just reports issues' — minimizing conflict risk, matching the clear-niche anchor.

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: 1 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.