Content
57%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-structured and token-efficient with sensible safety rules, but it reads as a summary rather than an operating manual: the workflow names steps without giving any executable commands, endpoint examples, or validation checkpoints. Concrete examples of REST calls (or filesystem conventions) and post-action verification would address the two weakest dimensions.
Suggestions
Add one or two concrete examples of acting on the vault, e.g. a sample request to the Local REST API (endpoint, Authorization header) or the filesystem path/layout convention used to resolve notes and folders.
Insert validation checkpoints into the workflow, such as verifying a note exists after creation, checking that inserted wikilinks resolve to existing notes, and confirming before any delete.
Replace the vague 'Apply configured template' step with where templates live and the placeholder syntax to substitute when applying one.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — no explanation of what Obsidian is or how REST APIs work, and sections are compact. Not a 5 because of minor trims available: the REST API URL is duplicated in both 'MCP' and 'References', and the bare 'Obsidian: https://obsidian.md/' link adds little value, so not quite 'every token earns its place'. | 4 / 5 |
Actionability | The workflow steps are high-level directives with almost no executable specifics: 'Establish connection to Obsidian Local REST API (port 27123)', 'Resolve target note or folder path within vault structure', 'Perform requested operation'. There are no example API calls, endpoint paths, headers (API key), filesystem path conventions, or template syntax — only the port number and a plugin URL are concrete. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute', and it is above a 1 because the port, safety rules, and companion skill mapping do constrain behavior somewhat. | 2 / 5 |
Workflow Clarity | A clear 7-step sequence is present (Connect, Locate, Act, Template, Link, Tag, Log), but there are no validation checkpoints — nothing to verify a note was created, a link resolves, or a template applied correctly. Since the Act step includes delete (a destructive operation) and vault-wide operations, the missing verification steps cap this at 3, matching 'steps listed but validation gaps; checkpoints missing or implicit'. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines with no need for external bundle files (references/ and scripts/ are empty), and the body is organized into clear, well-labeled sections (Purpose, Invocation, Workflow Steps, Safety, MCP, References, Companion Skills). Per the rubric's simple-skill exception, well-organized sections alone merit a 5 here; nothing that belongs in a separate file is inlined. | 5 / 5 |
Total | 14 / 20 Passed |