CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

math-help

Guide to the math cognitive stack - what tools exist and when to use each

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/math-help/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, executable command reference with excellent actionability and clearly sequenced workflows that include a verification checkpoint. Its main costs are triple-stated tool-selection guidance (table + layers + decision tree), inconsistent script invocation styles, and everything inlined in SKILL.md with no progressive disclosure to reference files.

Suggestions

Collapse the task→tool mapping into one navigation aid (keep the Quick Reference table OR the decision tree, not both) to cut significant duplication.

Unify the script invocation pattern — the body mixes `uv run python -m runtime.harness scripts/...`, `uv run python scripts/cc_math/...`, and `uv run python -m scripts.mpmath_compute` for the same script family; pick the one that actually runs.

Move the per-layer command catalogs and hint-level tables into one-level-deep reference files (e.g. references/sympy.md, references/tutor.md) and keep SKILL.md as the overview + tool-selection guide.

DimensionReasoningScore

Conciseness

The body is command-focused with no concept padding (no explaining what SymPy or Z3 is), but the task→tool mapping is stated three times — the Quick Reference table, the per-layer "When/Best For" sections, and the "Choosing the Right Tool" decision tree — and "Common Workflows" repeats earlier commands verbatim. That is more than minor duplication, so it matches anchor 3 rather than 4, but well above 2 since there is no over-explanation of known concepts.

3 / 5

Actionability

Nearly every entry is a concrete, worked, copy-paste-ready command (e.g. `solve "x**2 - 5*x + 6 = 0" --var x --domain real`, `prove "x + y == y+x" --vars x y --type int`), covering the common cases. It falls short of 5 because the invocation style is inconsistent across the same script family — `uv run python -m runtime.harness scripts/sympy_compute.py`, `uv run python scripts/cc_math/math_tutor.py`, and `uv run python -m scripts.mpmath_compute` — leaving uncertainty about which form actually runs, and a few examples elide arguments (`hint "..."`, `--constraints "..."`).

4 / 5

Workflow Clarity

The three "Common Workflows" are numbered, each with inline commands, and Workflow 1 embeds an explicit validation checkpoint (verify solutions with math_scratchpad.py). Not 5 because Workflows 2 and 3 have no checkpoints or error-recovery guidance, and Workflow 3's final step is only a comment deferring to another skill.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), yet the body inlines ~330 lines of per-tool command reference plus hint-level tables that would naturally live in per-tool reference files. Section structure and headers are good — above anchor 2 — but content that should be separate is inline with no one-level-deep reference pointers, matching anchor 3.

3 / 5

Total

14

/

20

Passed

Description

45%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly identifies the domain and the tool-selection purpose but stays at a meta level: no concrete capabilities and no explicit use-when trigger guidance. It would benefit from naming the actual operations (solve, verify, prove, plot) and an explicit "Use when..." clause.

Suggestions

Add 2-3 concrete capabilities to the description, e.g. "Solve equations symbolically with SymPy, verify reasoning steps, prove theorems with Z3/Lean".

Add an explicit "Use when..." clause with natural trigger phrases, e.g. "Use when the user asks to solve, integrate, prove, or verify mathematical statements".

Differentiate from the sibling /math orchestration skill by stating this is the guide that chooses among the math tools.

DimensionReasoningScore

Specificity

The description names the domain ("math cognitive stack") but the actions are purely generic — "Guide", "what tools exist and when to use each" — with no concrete capability named (solving, proving, plotting, etc.). It sits at anchor 2: domain named, actions minimal or generic; it is not 3 because unlike "Processes PDF files and extracts content" it lists zero concrete actions.

2 / 5

Completeness

It has a "what" (a guide to the math tool stack, tool selection) but the "when" is only meta-described ("when to use each") with no explicit "Use when..." clause or concrete trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the when-guidance is neither explicit nor specific.

3 / 5

Trigger Term Quality

Relevant keywords present in the description ("math", "tools", "guide") but common natural phrases users would say — "solve", "integrate", "equation", "prove", "calculate" — are absent, matching anchor 3 ("Works with PDF files"-level coverage). It is above 2 because the domain term "math" is explicitly present rather than pure generic language, but below 4 because synonyms and variations are missing.

3 / 5

Distinctiveness Conflict Risk

The math focus gives it a niche, but the framing "what tools exist and when to use each" is generic guide language that could describe any tool-selection skill and overlaps with the closely related /math orchestration skill referenced in the body. Somewhat specific but overlap risk remains — anchor 3.

3 / 5

Total

11

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 40 missing, 32 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/math-help/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.