Small Python utilities for math and text files.
46
32%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skillrun/skills/python_math/SKILL.mdQuality
Discovery
0%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 description is too vague and generic to be useful for skill selection. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing characteristics that would help Claude choose it over other skills.
Suggestions
List specific concrete actions the skill performs, e.g., 'Performs arithmetic calculations, solves equations, reads and writes .txt files, counts words and lines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for simple math calculations, number crunching, or reading/writing plain text (.txt) files.'
Narrow the scope to create a distinct niche, e.g., specify what kinds of math (basic arithmetic, statistics, algebra) and what text file operations (read, write, search, parse) are supported.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is vague — 'small Python utilities' and 'math and text files' are abstract categories, not concrete actions. No specific operations like 'calculate statistics', 'parse CSV', or 'read/write text files' are listed. | 1 / 3 |
Completeness | The description weakly addresses 'what' (utilities for math and text files) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The terms 'math', 'text files', and 'Python utilities' are overly generic and unlikely to match natural user queries. Missing specific trigger terms like 'calculate', 'parse', 'read file', 'write file', or file extensions. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic — 'Python utilities', 'math', and 'text files' could overlap with virtually any coding, data processing, or file manipulation skill. There is nothing to distinguish this from other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise skill that avoids unnecessary verbosity, but it falls short on actionability by referencing a script (`scripts/fib.py`) that isn't provided or described. The workflow is simple enough that elaborate sequencing isn't needed, but some basic error handling guidance and clarification of referenced files would improve it.
Suggestions
Either inline the content of `scripts/fib.py` or provide a link/reference to where it can be found so the example is fully executable.
Add brief guidance on error handling (e.g., what happens if the script fails or input is malformed).
Clarify how to provide input to the sum example (e.g., `echo '1 2 3' | python3 - <<'PY'...`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and wastes no tokens explaining what Python is or how scripts work. Every line serves a purpose. | 3 / 3 |
Actionability | The Fibonacci example references `scripts/fib.py` which is not provided or described, making it not fully executable. The heredoc example is concrete but the sum example lacks input specification (how to pipe data in). | 2 / 3 |
Workflow Clarity | For a simple skill this is mostly adequate, but there's no mention of error handling, validation of outputs, or what to do if scripts fail. The workflow is implicit rather than explicitly sequenced. | 2 / 3 |
Progressive Disclosure | The content is short and well-sectioned with Overview, Examples, and Output Files. However, it references `scripts/fib.py` without linking to it or explaining where to find it, and there's no navigation to any supporting files. | 2 / 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.
09cce3e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.