CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-tuning

Use when changing agent model or effort configuration, per-run Pi profile pins, adapter mappings, or eval candidate profiles.

Quality

60%

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 ./.agents/skills/agent-tuning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a dense, high-signal internal reference: every line is project-specific invariant knowledge with exact symbols, files, and regression tests. Its weaknesses are structural — the per-run Pi profile section is one unbroken paragraph mixing semantics, validation ordering, and a wall of test names, and no sequenced workflow ties the rules together.

Suggestions

Break the 'Per-Run Pi Profile Pin' section into labeled sub-points (immutability, validation-before-supersede, trust-policy behavior, enforcement, regressions) instead of one paragraph, and move the regression test lists into a compact trailing 'Regressions' block or a reference file.

Add a short worked example of the precedence resolution and the eval candidate spelling (e.g., 'agent,model=pi[,effort=high]') so maintainers have copy-paste-ready syntax rather than prose descriptions.

Sequence the main rules as an ordered decision path (where to add a harness, how a request flows through agent.NewWithOptions, how precedence is resolved, how eval replay is checked) so the invariants double as a workflow.

DimensionReasoningScore

Conciseness

All content is project-specific with no explanations of concepts Claude already knows, but the second section is a monolithic paragraph that buries core semantics under an inline flood of regression test names and could be substantially tightened.

3 / 5

Actionability

Concrete directives name exact symbols and locations ("Add a harness there, not in an adapter or in eval", "Never re-derive a model or effort flag at a call site", "centralized in `agentcfg.ServedMatchesRequested`") with real file and test paths, though no copy-paste examples of candidate syntax or precedence resolution are given.

4 / 5

Workflow Clarity

The body presents invariants and precedence rules rather than a sequenced process, and no validation checkpoints exist; the rules themselves are unambiguous but there is no workflow structure to attach checkpoints to.

3 / 5

Progressive Disclosure

The body is under 50 lines with two clear sections and one-level-deep references to repo docs (eval.md, global-config.md), but the second section is a single dense bullet and semantics ownership is scattered rather than navigable.

4 / 5

Total

14

/

20

Passed

Description

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

The description is a well-scoped trigger clause with distinctive internal terminology, but it completely omits what the skill does when invoked. Adding a concrete capability statement before the "Use when" clause would materially improve it.

Suggestions

Add a 'what' clause before the trigger, e.g., 'Owns the harness-neutral agent model/effort configuration surface and its mapping to each harness's native flags. Use when changing agent model or effort configuration...' so both what and when are explicit.

Include natural trigger variations users might phrase differently, such as 'model override', 'reasoning effort', 'pin the model for a run', or 'eval replay candidate', to broaden keyword coverage.

State the outcome the skill produces (e.g., 'validates and maps profile pins to native harness flags') so it is distinguishable from a generic configuration-editing skill.

DimensionReasoningScore

Specificity

Names several concrete domain items ("per-run Pi profile pins, adapter mappings, eval candidate profiles") but the only action stated is the generic "changing", so coverage of concrete actions is not comprehensive.

3 / 5

Completeness

The description is entirely a "Use when..." trigger clause; the skill's actual actions (the "what") are never stated, matching the anchor for only "when" present without "what".

2 / 5

Trigger Term Quality

Terms like "agent model", "effort configuration", and "Pi profile pins" match what a user of this codebase would say, but common variations and synonyms (e.g., "model override", "reasoning effort", "change the model for this run") are missing.

3 / 5

Distinctiveness Conflict Risk

Niche internal terminology (Pi profile pins, eval candidate profiles, adapter mappings) makes wrong-skill triggering unlikely, though "changing agent model or effort configuration" broadly overlaps generic configuration skills.

4 / 5

Total

12

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/agent-tuning/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.