Content
88%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.
An exemplary lean skill body: every fact is non-obvious, the read/approve/write policy is unambiguous with an explicit approval checkpoint, and example prompts make first use immediate. The only real flaws are the unexplained, dangling 'orbs starter' reference and the absence of any setup/configuration guidance for the MCP server.
Suggestions
Resolve the 'orbs starter' reference — either add the referenced file to the bundle and link it clearly (e.g., [orbs-starter.md](references/orbs-starter.md)) or replace the mention with a one-line inline instruction.
Add a brief setup note (one or two lines) telling the agent how to connect the hosted MCP server (e.g., the mcp config command or where Amp discovers it), so first use does not stall on configuration.
Optionally name one or two representative MCP tools (read vs. write) so the 'Start with read tools' rule is directly actionable on first invocation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries non-obvious information Claude could not know (pricing "$0.25 per verified write", approval behavior, OAuth sign-in, expired-connection handling) with zero padding or explanation of known concepts. This matches the 'lean and efficient; every token earns its place' anchor exactly; anchor 4's 'minor instances of over-explanation' does not apply. | 5 / 5 |
Actionability | Concrete directives ("Start with read tools. Show the plan for any write and get explicit approval first") and four copy-paste-ready example prompts give mostly executable guidance. It falls short of anchor 5 because setup is not covered — the body names the hosted MCP URL but gives no configuration/connection command or tool names, leaving a minor gap for first-time use. | 4 / 5 |
Workflow Clarity | This is a simple single-purpose skill where the interaction policy is unambiguous: read first, show the plan, obtain explicit approval before any write — an explicit checkpoint for the risky (money-spending) operations. An error-recovery instruction is also present ("If a tool says a connection expired, tell the user which platform to reconnect"), satisfying the feedback-loop requirement, so the missing-validation cap does not apply. | 5 / 5 |
Progressive Disclosure | At 21 lines with no need for external reference files, the three well-organized sections (intro facts, Good first prompts, Rules) would qualify for a 5 under the short-skill allowance. However, "In orbs, see the orbs starter instead" points to an 'orbs starter' that is neither a file in the bundle (references/, scripts/, assets/ are empty) nor explained, making it a dangling, unsignaled reference — a minor organization gap matching anchor 4. | 4 / 5 |
Total | 18 / 20 Passed |