Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sweetcornna/mathodology-project-orientation
Use when maintaining the skills-only repository or checking whether a change belongs here.
Passed 21 of 23 test cases with the skill, and 7 of 23 without it.
and 14 more in the full report
14 fixed7 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am adding a new specialized prompt skill to our project. Standard Claude conventions usually put skill definitions directly inside ./skills/ or .agents/skills/. Where should skill files be authored in this project structure?
| Checked | Without skill | With skill |
|---|---|---|
| identifies .claude/skills/ as the primary directory for authoring skills | Missed | Passed |
| identifies .agents/skills/ as a local mirror rather than an authoring folder | Missed | Passed |
The instructions your model reads when the skill loads.
The maintained source is .claude/skills/, with roles in .claude/agents/,
workflow prompts in .claude/workflows/, and user documentation in docs/.
The root retains AGENTS.md, the two READMEs, LICENSE, .gitignore and .mcp.json.
Skill directories may include reference Markdown, attributed source snapshots, small licensed images, generated demonstration figures and optional scripts. A reference figure is teaching material, not contest evidence. Keep synthetic previews visibly labeled and reproducible. Do not add a dataset collection, application runtime, CI, package manifest or deployment framework.
.agents/skills/ is an ignored local mirror, never a second authoring source.
Before replacing this project's installed skills, back up its Mathodology
entries outside the checkout. Leave other skills and global directories alone.
.mcp.json is a client configuration for the keyless search MCP. It is retained;
custom user configurations and secrets do not belong in source control.
Contest output can live in ignored work/ or another working directory.
Historical application implementation is available through Git history.
For maintenance, optionally run the repository checker described in maintenance. The checker verifies metadata, references and boundaries; it does not assess mathematical quality.
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.