CtrlK
BlogDocsLog inGet started
Tessl Logo

pi-custom-model

Register a custom or variant model (e.g. an OpenRouter ":nitro" / ":floor" / ":exacto" slug) in the Pi Agent so it can be set as the global default. Use when Pi silently falls back to a different model (e.g. moonshotai/kimi-k2.6) after setting defaultModel, or when a model slug isn't in Pi's bundled list. Triggers on "Pi reset my model", "Pi won't use this model", "add a model to Pi", "Pi default keeps reverting".

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, highly actionable skill body: concrete file paths, a copy-ready JSON example, sequenced steps with validation, and well-organized sections with no unnecessary padding. No bundle files are present, which is appropriate for a skill this size.

DimensionReasoningScore

Conciseness

Lean and efficient: the 'When to use' paragraph explains non-obvious Pi registry mechanics rather than concepts Claude already knows, and the JSON block is necessary and copy-ready, so every token earns its place.

3 / 3

Actionability

Provides concrete file paths, a complete copy-ready models.json example, and specific verification commands ('pi --list-models | grep <id>' and a smoke-test invocation), all directly executable.

3 / 3

Workflow Clarity

Five clearly sequenced steps with pre-flight validation checkpoints (confirm slug is real, confirm auth) and an explicit verify step (step 5) including JSON-parse and model-list checks.

3 / 3

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files, organized into clear sections (When to use, Files, Steps, Quirks); per the simple-skills note this qualifies for a top score.

3 / 3

Total

12

/

12

Passed

Description

90%

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, niche description with explicit what/when framing and natural trigger phrases. The only soft spot is specificity, which lists essentially one action (register a model) rather than multiple distinct concrete actions.

Suggestions

Add a second concrete verb to the 'what' clause (e.g. 'Register … and pin it as the global default via enabledModels') to lift specificity from one action to multiple.

Consider trimming the parenthetical fallback example ('moonshotai/kimi-k2.6') from the description to keep it lean and avoid coupling to a specific bundled default that may change.

DimensionReasoningScore

Specificity

It names a concrete action ('Register a custom or variant model … so it can be set as the global default') with variant examples, but centers on a single action rather than listing multiple concrete actions, matching anchor 2 rather than 3.

2 / 3

Completeness

Clearly answers both what ('Register a custom or variant model … as the global default') and when ('Use when Pi silently falls back … or when a model slug isn't in Pi's bundled list') with explicit triggers.

3 / 3

Trigger Term Quality

Explicit 'Triggers on' natural user phrases ('Pi reset my model', 'Pi won't use this model', 'add a model to Pi', 'Pi default keeps reverting') give good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Highly niche scope (Pi Agent, OpenRouter variant slugs, a specific fallback model) gives it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
mishatojk/davidskills
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.