CtrlK
BlogDocsLog inGet started
Tessl Logo

configuring-pi

Configures Pi settings, models, resources, trust, and environment behavior. Use when editing settings.json or models.json, selecting tools or models, changing package/resource loading, or diagnosing configuration precedence.

71

Quality

86%

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

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

A well-structured instruction skill: concise, layered-config framing with a checkpointed workflow and clean one-level references. Actionability and the error-recovery feedback loop have minor gaps that keep it just short of top marks.

Suggestions

Replace the <plugin-root> and <target> placeholders in the validate command with a concrete example or a one-line note on how to resolve them.

Add an explicit feedback loop in step 5 (e.g., "If validation reports errors, fix the flagged keys and re-run validation before proceeding").

Include one minimal concrete settings.json or models.json edit snippet to ground step 4's "smallest valid change" directive.

DimensionReasoningScore

Conciseness

The body is lean and dense: a one-line framing, a five-step workflow with tight completion criteria, short boundaries, and two references, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides concrete commands (validate-pi-harness.py, pi --list-models, pi config) and clear directives, but the validation path uses placeholder tokens (<plugin-root>, <target>) and the instruction-heavy steps lack a concrete config-edit example, leaving minor gaps.

4 / 5

Workflow Clarity

Five sequenced steps each carry an explicit "Complete when:" checkpoint and step 5 includes validation plus a smoke check, but the validate-fails-then-fix-and-revalidate feedback loop is implied rather than spelled out as an explicit loop.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with two well-signaled, one-level-deep references (settings.md, models.md) that both exist as self-contained files, with detail appropriately split out and easy navigation.

5 / 5

Total

18

/

20

Passed

Description

87%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 that cleanly states purpose and trigger conditions with Pi-specific file names, giving it good distinctiveness and completeness. Specificity and trigger coverage are solid but not exhaustive enough to top out.

DimensionReasoningScore

Specificity

Names five concrete configuration facets (settings, models, resources, trust, environment) and pairs each with a triggering operation, but the actions are categorized areas rather than a list of explicit concrete verbs, so it sits just below a fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both what (configures settings, models, resources, trust, environment behavior) and when via a concrete "Use when..." clause enumerating multiple triggers, matching the anchor for clear and explicit coverage.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("editing settings.json or models.json", "selecting tools or models", "diagnosing configuration precedence") with real file names, though a few common variants like "add a custom model" or "trust a package" are absent.

4 / 5

Distinctiveness Conflict Risk

The Pi-specific file names and operations (settings.json, models.json, package/resource loading, configuration precedence) carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

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
slurpyb/skills
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.