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.
A tightly written, highly actionable instruction skill: concrete formulas, explicit failure protocols, authorization gates, and a realistic worked example. Its main weaknesses are the triple repetition of the denominator rule, long compound sentences in the LTV and STAR steps, and a reference list dominated by cross-repo paths that are unverifiable from this bundle.
Suggestions
State the denominator-verification rule once (e.g., in the Done-when contract or the closing paragraph) and reference it from the other two spots instead of repeating it fully in all three.
Move the detailed LTV-basis requirements (step 6) and the R1-R6 evidence qualifications (step 9) into references/roi-templates.md blocks, keeping only the formula and the gate handoff inline.
Trim the Reference Materials list to the in-bundle template plus the few cross-repo documents actually needed for a run, or group the sibling-skill links under the existing Next Best Skill section to avoid duplication.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and free of beginner-concept padding, but the denominator-verification rule is stated three times (Done-when #4, step 2's rules, and the full closing paragraph after step 10) and steps 6 and 9 run as long compound sentences that could be trimmed. | 4 / 5 |
Actionability | Exact formulas (Simple ROI, ROAS, the LTV formula), an explicit NEEDS_INPUT protocol, ready-to-use invocations, and a complete worked example give fully executable guidance for an instruction-only skill, with each step linked to a concrete template. | 5 / 5 |
Workflow Clarity | Steps 1-10 are clearly sequenced with explicit validation gates (denominator checks, profitability-verification status, authorization required before saves) and NEEDS_INPUT feedback loops for missing or invalid inputs. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview with a clearly signaled one-level-deep reference to references/roi-templates.md (verified present with matching anchors), but most listed references point outside the bundle to unverifiable paths and steps 6/9 carry inline detail that belongs in the templates file. | 4 / 5 |
Total | 18 / 20 Passed |