leo-laptop/calculate
Use when the user asks you to calculate, compute, evaluate, or solve a math expression or equation. Triggers on arithmetic, order of operations (PEMDAS), fractions, percentages, exponents, and multi-step math problems.
84
78%
Does it follow best practices?
Impact
94%
1.00xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong trigger terms and explicit 'Use when' and 'Triggers on' clauses. Its main weakness is that the specificity of capabilities could be improved by describing what concrete outputs or actions the skill performs (e.g., 'shows step-by-step solutions', 'simplifies expressions'). Overall, it effectively communicates when to select this skill.
Suggestions
Add more specific concrete actions/outputs, e.g., 'Provides step-by-step solutions, simplifies expressions, and shows intermediate calculations' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (math expressions/equations) and lists some action verbs (calculate, compute, evaluate, solve), but doesn't describe specific concrete outputs or capabilities beyond general math solving. It lists categories of math (fractions, percentages, exponents) but not specific actions performed on them. | 2 / 3 |
Completeness | Clearly answers both 'what' (calculate/compute/evaluate/solve math expressions and equations) and 'when' with an explicit 'Use when...' clause and a 'Triggers on...' clause specifying the types of math problems that should activate this skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'calculate', 'compute', 'evaluate', 'solve', 'math expression', 'equation', 'arithmetic', 'PEMDAS', 'fractions', 'percentages', 'exponents'. These are all terms users would naturally use when requesting math help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around mathematical computation and expression evaluation. The specific trigger terms like 'PEMDAS', 'arithmetic', 'exponents', and 'fractions' make it distinct from other skills and unlikely to conflict with non-math skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
54%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured and clearly organized, but its fundamental weakness is that it teaches Claude things it already knows — PEMDAS, basic arithmetic, and order of operations are core knowledge for any LLM. The token budget is spent on redundant information rather than adding genuinely new capabilities or project-specific constraints. The workflow and organization are solid, but the content itself provides minimal value over Claude's existing abilities.
Suggestions
Remove the PEMDAS table, supported operations list, and common mistakes table — Claude already knows all of this. Focus only on the desired output format/style.
If the goal is to enforce a specific step-by-step presentation format, reduce the skill to just the 'How to Respond' section and one example, cutting ~70% of the content.
Consider adding guidance for edge cases Claude might actually struggle with, such as ambiguous notation, implicit multiplication, or how to handle malformed expressions from users.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This skill explains PEMDAS, basic arithmetic operations, and order of operations — all concepts Claude already knows thoroughly. The entire content is teaching Claude things it fundamentally understands, wasting token budget on a PEMDAS table, common mistakes table, and supported operations list that add no new knowledge. | 1 / 3 |
Actionability | The skill provides a clear response format (restate, identify, work through, state answer) and includes a worked example, which is somewhat actionable. However, there's no executable code or tool usage — it's purely instructional guidance for something Claude can already do, and the example is helpful but basic. | 2 / 3 |
Workflow Clarity | The 4-step 'How to Respond' sequence is clear and unambiguous for this single-task skill. The worked example demonstrates the exact workflow expected. Since this is a simple, non-destructive task with no batch or risky operations, the workflow is appropriately complete. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines of meaningful content, the organization is clean with well-structured sections (overview, rules table, workflow, example, supported operations, common mistakes). No external references are needed for this scope. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents