CtrlK
BlogDocsLog inGet started
Tessl Logo

customizations-in-the-agent-host

Architecture and hard-won debugging lessons for customization enablement (plugins, MCP servers, agents, skills, instructions) in the agent host. Use when changing how customizations are discovered, published, enabled/disabled, or handed to a provider SDK; when a customization shows the wrong enabled state in the UI; or when a disabled MCP server or plugin is still reaching the model.

72

Quality

88%

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

90%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 excellent, hard-won knowledge skill: lean, highly actionable, and well-structured with concrete file paths, named functions, and validation commands. It assumes competence and rewards the reader with specific failure modes and reproduction steps; only progressive disclosure and workflow-formality are slightly below top marks.

DimensionReasoningScore

Conciseness

Dense, high-signal prose that assumes Claude's competence — invariants, specific file paths, and production-bug causes with no padding about what plugins or MCP servers are; every line conveys non-obvious domain knowledge.

5 / 5

Actionability

Provides concrete executable guidance throughout — exact file paths, a copy-paste-ready Validation command block, named functions to route through, and a specific reproduction recipe; per the rubric, instruction-only skills are not penalized for lack of code when guidance is this specific.

5 / 5

Workflow Clarity

The debugging playbook and reproduction recipe give a clear ranked sequence with validation signals, and the Validation section provides explicit checkpoints; not a 5 because the primary form is a mental-model/reference rather than a single end-to-end workflow with error-recovery feedback loops.

4 / 5

Progressive Disclosure

Well-organized into clear headers (mental model, enforcement, debugging playbook, gotchas, validation) with one-level signaled pointers to companion skills (agent-host-logs, launch); not a 5 because the skill exceeds 50 lines with no bundle files, so some inline gotcha/playbook detail could conceivably be split, though it reads cohesively.

4 / 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, third-person description that explicitly pairs a concrete 'what' with multiple specific 'when' triggers tied to real debugging symptoms. It is distinctive and low-conflict; the only minor gap is action enumeration vs. scenario framing.

DimensionReasoningScore

Specificity

Names the domain and several concrete enablement actions/scope ('discovered, published, enabled/disabled, or handed to a provider SDK', 'wrong enabled state in the UI', 'disabled MCP server or plugin is still reaching the model'); not a 5 because the actions are framed as change-scope rather than an exhaustive enumerated action list.

4 / 5

Completeness

Explicitly answers both 'what' ('Architecture and hard-won debugging lessons for customization enablement') and 'when' (a multi-clause 'Use when...' with concrete trigger scenarios), matching the anchor for clearly answering both with concrete triggers.

5 / 5

Trigger Term Quality

Natural debugging trigger phrases users would actually say ('shows the wrong enabled state in the UI', 'disabled MCP server or plugin is still reaching the model'); not a 5 because it leans on scenario phrasing rather than a broad set of keyword synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (customization enablement in the agent host) with highly specific triggers unlikely to fire for unrelated skills, giving minimal conflict risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.