Conciseness

At ~1,190 lines the body repeats the same traps multiple times: the LIVE-vs-DEGRADED `ob.read()` semantics are explained in the Step 0 trap box, again in Step 2.5a, again in the Step 4 slug-check warning, and again as Rule 19; the heredoc prohibition appears in Step 4 and Rules 4-5. Dated incident notes ("Measured 2026-09-22", "observed 2026-09-17 → 09-19", "caught 2026-10-02") are time-sensitive and inline rather than in a changelog/deprecated section. This matches "noticeably verbose; several unnecessary explanations or padded sections". Not 1 because none of it explains concepts Claude already knows — every trap is genuinely environment-specific; not 3 because the repetition and incident-log padding could realistically halve the token count.

Actionability

Every step has copy-paste-ready commands: the preflight probe one-liner, `python .github/skills/obsidian-linked-research/scripts/fetch.py "<url>"`, the executable `prune_recently_added()` function, the exact image-filter token list (`w_150`, `profile_images`, `default-light`), and the exact `chr(0x1F5FA) + chr(0xFE0F)` filename construction. Fully executable with specific examples covering tweets, web pages, threads, and degraded mode.

Workflow Clarity

Steps 0-8 are clearly sequenced with explicit validation checkpoints and feedback loops: the preflight probe ("run this first, every time"), the mandatory URL-dedup stop gate ("If a match is found, stop"), the `note_text()` assert on the MOC, the explicit truncation check `len(result.get('content', '')) >= 8000`, the transient retry ("retry once... if it fails twice, report"), post-write read-back verification, and the Substack archive-API fallback. This matches the anchor's validate-fix-retry pattern.

Progressive Disclosure

The body is well-sectioned with clear step headers, and the one bundle file (scripts/fetch.py, 767 lines) is real and correctly referenced. But there are no reference files at all: content that clearly belongs in separate files is inlined — the 13-row routing table, the full note template, the Windows/PowerShell gotcha compendium, and the pruning code all live inside a monolithic ~1,200-line SKILL.md. This matches "some structure but could be better organized; content that should be separate is inline". Not 2 because the structure and navigation within the file are strong; not 4 because essentially all reference-worthy material is inlined rather than split out one level deep.

Specificity

Quotes: "Fetch a URL, summarize it, and save as a structured research note in the current Obsidian Research/Library taxonomy" plus "source of truth for tags, folder routing, and freshness updates" — several concrete actions with routing/tag specifics, matching the anchor "lists several specific actions; minor gaps in coverage". Not 5 because real capabilities (tweet/X enrichment, URL dedup, thesis drift check) are unmentioned; not 3 because more than 1-2 actions are named with concrete routing detail.

Completeness

The "what" is clear ("Fetch a URL, summarize it, and save as a structured research note..."), but there is no "Use when..." clause or equivalent trigger guidance — "Use the master Research Library MOC as the source of truth" is an instruction, not a trigger. Per the judging guideline, a missing 'Use when' clause caps completeness at 3.

Trigger Term Quality

Natural terms present: "Fetch a URL", "summarize", "research note", "Obsidian" — phrases a user would plausibly say. Not 5 because common user phrasings like "save this article", "tweet", "link", or "web page" are absent; not 3 because coverage goes beyond a single generic keyword to include the domain vocabulary users of this vault would actually use.

Distinctiveness Conflict Risk

The niche is distinct: "structured research note in the current Obsidian Research/Library taxonomy" and "master Research Library MOC" would not fire for generic PDF/document skills. Not 5 because "Fetch a URL, summarize it" overlaps with sibling skills in this vault (obsidian-daily-research, last30days) and generic summarize/save requests; not 3 because the taxonomy-specific vocabulary keeps it mostly distinguishable.