Content
77%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with executable examples and clear verification-backed workflows, but it is verbose with significant redundant sections, and its progressive-disclosure structure is undermined by reference files that are signaled but not actually shipped.
Suggestions
Ship the five referenced files under references/ (core-capabilities.md, matrices-linear-algebra.md, physics-mechanics.md, advanced-topics.md, code-generation-printing.md) or remove the dangling references, since the bundle directory is currently missing.
Remove redundant sections — 'Getting Started Examples', 'Quick Reference: Most Common Functions', and the NumPy/Matplotlib/SciPy integration blocks largely repeat code already shown in 'Core Capabilities' and 'Best Practices'.
Trim the body to a lean overview and move detailed API/catalog content into the reference files so SKILL.md earns its token budget rather than restating SymPy basics Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~490-line body is heavily padded with redundancy: 'Getting Started Examples' repeats derivative/integral/eigenvalue/lambdify examples already shown in 'Core Capabilities', 'Quick Reference' repeats shown imports, and 'Integration with Scientific Workflows' duplicates lambdify usage; not level 1 because it avoids conceptual fluff, but not level 3 because most tokens are not lean. | 2 / 3 |
Actionability | Numerous copy-paste-ready executable Python blocks (symbols, diff, integrate, solveset, Matrix, lambdify, dsolve) with expected outputs as comments match the level-3 anchor for fully executable, specific examples; not level 2 because the code is complete, not pseudocode. | 3 / 3 |
Workflow Clarity | Workflows are clearly sequenced with validation: 'Pattern 1: Solve and Verify' includes a verification loop with an assert checkpoint, and 'Pattern 2: Symbolic to Numeric Pipeline' is an explicit 4-step sequence; not level 2 because checkpoints are present rather than implicit. | 3 / 3 |
Progressive Disclosure | References are clearly signaled one level deep ('See references/core-capabilities.md' etc.) with a 'Load when' guide, but the references directory does not exist, so the signaled paths are broken, and heavy inline content that should live in those files makes this a monolithic body rather than a lean overview; not level 3 because the referenced bundle files are absent. | 2 / 3 |
Total | 10 / 12 Passed |