process-links
Process all queued links from the web capture queue into Obsidian notes. Use when the user wants to process their captured links.
80
Quality
76%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/process-links/SKILL.mdQuality
Discovery
75%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 has good structure with explicit 'what' and 'when' clauses, and targets a distinct niche combining web capture and Obsidian. However, it lacks specificity about what 'processing' actually involves and could benefit from more natural trigger terms users might use when requesting this functionality.
Suggestions
Expand on what 'process' means - e.g., 'converts captured web links into formatted Obsidian notes with extracted content, metadata, and tags'
Add more natural trigger terms users might say: 'reading list', 'saved articles', 'bookmarks', 'web clippings', 'import from browser'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (web capture queue, Obsidian notes) and one action (process links), but lacks detail on what 'processing' entails - does it extract content, summarize, format, or just create links? | 2 / 3 |
Completeness | Explicitly answers both what ('Process all queued links from the web capture queue into Obsidian notes') and when ('Use when the user wants to process their captured links') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('captured links', 'queued links', 'Obsidian notes') but misses common variations users might say like 'reading list', 'saved articles', 'bookmarks', 'web clippings', or 'import links'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'web capture queue' and 'Obsidian notes' creates a clear, specific niche that is unlikely to conflict with general web scraping or note-taking skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear workflow sequencing and good error handling. The main weakness is length - the skill packs substantial detail inline (6 view file specifications, intent detection rules, deduplication logic) that could be referenced externally. Conciseness suffers slightly from some redundancy with the capture skill.
Suggestions
Extract the 6 view file specifications into a separate VIEWS.md reference file to reduce inline bulk
Consider referencing the capture skill more directly rather than partially re-specifying its logic (e.g., 'Follow capture skill steps 2-5' with link)
Move intent detection rules to a shared INTENT-DETECTION.md if used across multiple skills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating 'Use the same logic as /capture' while also detailing the steps). Some sections like intent detection could be more compact. | 2 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, JSON structures, bash commands, and exact output formats. Steps are copy-paste ready with clear examples of queue item fields and view file formats. | 3 / 3 |
Workflow Clarity | Clear numbered sequence with explicit validation points (Step 2 deduplication, Step 4 status updates, Step 5 regeneration). Error handling is explicit with continue-on-failure behavior and status tracking for each link. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~120 lines of instruction) and could benefit from splitting detailed view generation specs or intent detection rules into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.