Content
67%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.
A thorough, well-structured instruction skill with strong actionability and clear approval-gated workflows for risky Apollo operations. Its main weakness is conciseness: gating rules and credit phrasing are restated across multiple sections and could be consolidated.
Suggestions
Consolidate the repeated Apollo-credit exposure and approval rules so each gating concept is stated once (e.g. merge the Credit-Aware Behavior and Safety Rules credit bullets, and remove the duplicated 'Apollo credit, not API credit' line from Output Rules).
Add an explicit validate-fix-retry feedback loop for batch/mutation failure cases (e.g. what to do when a bulk account/contact create reports duplicate or validation errors) to lift workflow clarity.
Tighten the Connector Boundary and Search And Resolution sections, which overlap on tool-lane enumeration; reference a single canonical lane list to reduce token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with rules and avoids explaining concepts Claude already knows, but it repeats the same gating concepts and 'Apollo credit' phrasing across Credit-Aware Behavior, Safety Rules, and Output Rules, and could be tightened by consolidating those repeated lists. | 3 / 5 |
Actionability | For an instruction-only skill it is highly actionable, naming concrete tool lanes (People Search, Contact Search, Organization Search), exact table column layouts, and specific before-mutation steps (field-level before/after diff, dedupe options), with only minor gaps in edge-case detail. | 4 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced with explicit approval checkpoints (e.g. the 7-step People-to-Company Details flow with 'Ask for explicit approval' at step 6) and full preview gates for batch/mutation work, but explicit validate-fix-retry feedback loops for error recovery are less spelled out. | 4 / 5 |
Progressive Disclosure | Well-organized into clear sections with one-level-deep, clearly signaled external references (../index/SKILL.md anchors for limitations and next steps); no bundle files exist, so the single inline file is reasonable, though some inline reference material could arguably be externalized. | 4 / 5 |
Total | 15 / 20 Passed |