term-check — Claude Code skill: what it does, how to install
Tests candidate names for fields, tables, or enum values using blind prompts across three AI models. Helps pick terms that developers understand without docs.
npx skills add timschoch/skilly --skill term-check -a claude-codeWhat term-check does
This skill checks if an identifier conveys its purpose before someone checks documentation. You draft a brief neutral scenario with a {TERM} marker instead of the real name. The probe expects three options at once; when you only supply two, it suggests adding a third synonym to keep tests balanced.
The included probe.sh script queries three language models across two iterations per candidate in parallel. It formats findings into a comparison matrix showing correct, partial, or incorrect classifications, accompanied by model interpretations.
A leaky prompt ruins the run by making every synonym look accurate. Keep in mind that while runs execute in a blank workspace without repository context, global directives from ~/.claude/CLAUDE.md still load on every pass.
What it helps with
- pick clear names for database columns or enum entries
- validate glossary words against blind model interpretations
- compare competing identifier choices in identical contexts
- detect confusing terminology before writing production code
Example prompts for the agent
- Prepare a benchmark scenario for
term-checkcomparingcarryandcarryOver - Execute
bash .agents/skills/term-check/probe.sh scenario.txt active live enabled - Review the
term-checkmatrix and propose extra synonyms if the leader has low confidence
How to install term-check
1Skills CLI (Vercel)
npx skills add timschoch/skilly --skill term-check -a claude-code2Manually: put the files in place
~/.claude/skills/term-check/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/term-check/
1Skills CLI (Vercel)
npx skills add timschoch/skilly --skill term-check -a codex2Manually: put the files in place
.agents/skills/term-check/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add timschoch/skilly --skill term-check -a cursor2Manually: put the files in place
.cursor/skills/term-check/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install timschoch/skilly term-check2Manually: put the files in place
.github/skills/term-check/SKILL.md1Skills CLI (Vercel)
npx skills add timschoch/skilly --skill term-check -a gemini-cli2Platform CLI
gemini skills install https://github.com/timschoch/skilly --path bundles/workflow/skills/term-checkManually: put the files in place
.devin/skills/term-check/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add timschoch/skilly --skill term-check -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about term-check
How to install term-check in Claude Code?
Run npx skills add timschoch/skilly --skill term-check -a claude-code. The skill file is placed at ~/.claude/skills/term-check/SKILL.md.
What does term-check do?
It tests how three different AI models interpret candidate terms inserted into a neutral scenario. The output table reveals which word communicates the intended role most clearly.
What does it mean when every term receives matching scores?
Identical scores usually indicate the scenario text accidentally gave away the intended meaning. Refactor the scenario prompt to eliminate leading clues and re-run probe.sh.