CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-maintain-models

Add new AI models to Kiln's ml_model_list.py and produce a Discord announcement. Use when the user wants to add, integrate, or register a new LLM model (e.g. Claude, GPT, DeepSeek, Gemini, Kimi, Qwen, Grok) into the Kiln model list, mentions adding a model to ml_model_list.py, asks to discover/find new models that are available but not yet in Kiln, or wants to add a net-new AI provider to Kiln.

71

Quality

89%

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

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.

An exceptionally actionable, well-sequenced operational skill: nearly every instruction is a copy-paste command or a hard-won gotcha Claude could not know, with strong validation gates and feedback loops. Its one structural weakness is that it is a ~900-line monolith whose reference material (provider quirks, slug lookups, thinking-level constants) is inlined rather than split into bundled reference files.

Suggestions

Move the Provider Quirks Reference, Slug Lookup Reference, Thinking Levels Reference, and Lagging Providers sections (~400 lines) into references/ files, keeping one-line pointers in SKILL.md with a 'read when adding a model on this provider' trigger so the always-loaded body shrinks to the core workflow.

Deduplicate the lagging-provider guidance: Phase 1B restates provider lists and rationale that the Lagging Providers section also covers — state the rule once and link to the endpoint reference.

Move the Phase 5b PR body template into a references file or template asset, since it is only needed at the final step of a successful run.

DimensionReasoningScore

Conciseness

The body is dense with proprietary operational knowledge ("addopts = '-n auto' is active", "the together fork isn't exercised by model-integration tests") and avoids explaining concepts Claude already knows. Minor tightening is possible: the lagging-provider rule appears in both Phase 1B and the Lagging Providers section, and ~66KB is always loaded into context even for a single known-provider model addition.

4 / 5

Actionability

Fully executable throughout: exact curl+jq catalog queries, exact pytest invocations including the bracket-filter "-k 'test_name[glm_5-fireworks_ai]'" syntax, a copy-paste PR body template, exact branch naming ("add-model/MODEL_NAME"), and concrete env-key bridging commands.

5 / 5

Workflow Clarity

Phases 1→5 are explicitly sequenced with validation checkpoints everywhere: the 4b smoke test gates the 4c full suite, 3c requires printing the resulting list order to verify placement, 4e confirms failures are pre-existing before treating them as regressions, and 5.1 hard-gates pushing on test outcomes. A final checklist consolidates the process.

5 / 5

Progressive Disclosure

Internal navigation is good (anchor links like "[Slug Lookup Reference](#slug-lookup-reference)" and the referenced scripts/check_thinking_levels.py exists), but ~400 lines of lookup material (Provider Quirks, Slug Lookup, Thinking Levels constants, Lagging Providers) live inline in SKILL.md rather than in the absent references/ files — content that clearly belongs in separate one-level-deep files.

3 / 5

Total

17

/

20

Passed

Description

91%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 description: concrete actions, explicit and multi-branch 'Use when...' triggers with good synonym coverage, third-person voice, and a clearly anchored niche. The only weaknesses are unmentioned workflow stages (tests, PR) and slight trigger overlap from the generic model-name list.

DimensionReasoningScore

Specificity

"Add new AI models to Kiln's ml_model_list.py and produce a Discord announcement" plus enumerated capabilities ("discover/find new models", "add a net-new AI provider") gives several specific actions with only minor gaps — it doesn't mention the test/PR portions of the workflow. Not 5 because coverage is not comprehensive; not 3 because more than 1-2 concrete actions are listed.

4 / 5

Completeness

Explicitly answers both: the "what" is stated first (add models to ml_model_list.py, produce a Discord announcement) and the "when" is a full "Use when..." clause with multiple concrete trigger phrases. Not below 5 since both halves are explicit and concrete.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: "add, integrate, or register", "discover/find", concrete model names users would say ("Claude, GPT, DeepSeek, Gemini, Kimi, Qwen, Grok"), and the literal file mention "adding a model to ml_model_list.py".

5 / 5

Distinctiveness Conflict Risk

The Kiln/ml_model_list.py anchoring makes the niche clear, but the generic model-name list ("Claude, GPT, DeepSeek, Gemini...") creates minor overlap risk — a user asking to 'add Claude' to some non-Kiln project could match. Mostly distinct, hence 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (910 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Kiln-AI/Kiln

Path

.agents/skills/claude-maintain-models/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.