CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

solo

Work on one hard mathematics problem in this session yourself, with no sub-agents: reason in stages, record each settled step in a notes file so that nothing written is lost if a response is cut off, and end with a self-contained proof.md. Usage: /math-proof:solo <the problem, stated in full, or the path of a file holding it>.

Quality

80%

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 ./plugins/math-proof/skills/solo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is an exceptionally well-engineered behavioral spec: concrete file contracts, exact commands, deterministic branching for every failure mode, and a cut-off recovery protocol. Its one weakness is redundancy — the write-to-notes-as-you-go imperative and its rationale are repeated several times across the task section and could be consolidated to roughly two statements without losing any behavioral force.

Suggestions

Consolidate the repeated write-as-you-go injunction into one normative rule plus one sentence of rationale — "write every settled step to DIR/notes.md before reasoning further; unwritten reasoning is lost on cut-off; keep going after each write" — instead of restating it four times across The task section.

State the output-allowance/cut-off rationale once rather than twice ("a message that is cut off is normally followed by..." and "each message's output allowance also covers your private reasoning" overlap).

The closing reply contract (where proof.md is, and whether it resolves the problem) could move into the Setup section's file-contract list, letting The task section end at the proof.md write.

DimensionReasoningScore

Conciseness

The Arguments and Setup sections are dense but every clause handles a distinct edge case (DIR parsing, bad setting tokens, file-path detection, resume states) — not padding. However, the write-as-you-go rule is restated roughly four times ("write your work product out as you go", "whenever you settle something... write it down before reasoning further", "Writing to the notes is not finishing — keep going after each write", "Many short written steps beat one long unwritten one") and the cut-off rationale is explained twice. Mostly efficient but noticeably tighter possible — anchor 3, not 4 because the repetition goes beyond minor over-explanation.

3 / 5

Actionability

Fully actionable without code: exact paths (DIR/problem.md, DIR/notes.md, DIR/proof.md), exact commands (`mkdir -p`, `cp`, `cmp`), the default DIR ("./math-proof-solo"), verbatim one-sentence error replies for every failure branch, and a concrete resume protocol. An instruction-only skill whose guidance is copy-paste executable — anchor 5.

5 / 5

Workflow Clarity

The sequence is unambiguous (parse arguments → setup/resume check → staged reasoning with mandatory notes writes → write self-contained proof.md → brief reply) and every branch has an explicit checkpoint and recovery path: `cmp` to detect a different problem, detecting an already-completed run, "If a message of yours is cut off, re-read DIR/notes.md and continue from the last thing written there; never start over", and the missing-input usage reply. Explicit validation and error-recovery feedback loops — anchor 5.

5 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ exist) and nothing in the ~60-line body warrants a separate file for this single-task skill. Content is organized into clearly labeled sections (Arguments, Setup, The task) with the deliverable's contract stated up front. Under the simple-skill exception, well-organized sections with no nested references score 5.

5 / 5

Total

18

/

20

Passed

Description

70%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.

A strong, concrete description that clearly states what the skill does with specific actions and a distinctive niche, but it lacks an explicit 'Use when...' trigger clause — the Usage line gives invocation syntax, not when to reach for the skill — and it omits natural trigger synonyms like 'theorem' or 'prove'. These cap completeness and trigger-term quality below the top anchors.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to prove or solve a hard mathematics problem and wants it worked in one session without sub-agents" — this would lift completeness from 3 to 4-5 and sharpen the 'when' beyond the invocation-only Usage line.

Include natural trigger synonyms in the description ("prove", "theorem", "lemma", "solve this problem") so it fires on the phrasings users actually say, not just "hard mathematics problem".

Consider naming the deliverables users would mention ("solution", "write-up") alongside proof.md to broaden trigger coverage without adding vagueness.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "reason in stages", "record each settled step in a notes file so that nothing written is lost if a response is cut off", "end with a self-contained proof.md", "with no sub-agents" — which cover the core workflow. Not 5 because resume/recovery and file-layout specifics live only in the body, leaving minor coverage gaps; clearly above 3's '1-2 concrete actions'.

4 / 5

Completeness

The 'what' is explicit and concrete (work a math problem solo, reason in stages, record steps, produce self-contained proof.md), but the only 'when' is the invocation line "Usage: /math-proof:solo <the problem, stated in full, or the path of a file holding it>", which is syntax rather than 'Use when...' trigger guidance. Per the guideline capping completeness at 3 without an explicit trigger clause, this fits anchor 3 exactly — 'what' clear, 'when' only weakly implied.

3 / 5

Trigger Term Quality

Natural terms like "hard mathematics problem", "proof.md", and "notes file" would be said by users with this need, but common variations such as "prove this theorem", "solve this", "lemma", or "write a proof" are missing. Good coverage without synonyms — matches anchor 4, not 3 (more than 'some relevant keywords') and not 5 (no synonym coverage).

4 / 5

Distinctiveness Conflict Risk

"Work on one hard mathematics problem in this session yourself, with no sub-agents... end with a self-contained proof.md" carves out a clear niche (single-session mathematical proof production) with distinct vocabulary that virtually no other skill would claim. Minimal conflict risk — anchor 5.

5 / 5

Total

16

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

anthropics/claude-plugins-official

Path

plugins/math-proof/skills/solo/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.