CtrlK
BlogDocsLog inGet started
Tessl Logo

modify-agent

Modify agent code, add tools, or change configuration. Use when: (1) User says 'modify agent', 'add tool', 'change model', or 'edit agent.py', (2) Adding MCP servers to agent, (3) Changing agent instructions, (4) Understanding SDK patterns.

73

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-organized, highly actionable skill body dominated by executable code with minimal prose and good delegation to sibling skills and external docs. Its main gap is the absence of explicit validation checkpoints in the workflow sections.

Suggestions

Add an explicit validate/verify checkpoint after the MCP-server and model-change steps (e.g. test the agent runs locally before granting permissions), which would lift workflow_clarity to 3.

Move or mark the hardcoded model name list as workspace-dependent to fully insulate conciseness from version drift.

DimensionReasoningScore

Conciseness

The body is lean and code-heavy with brief notes and no explanation of concepts Claude already knows; the version-specific model list is mitigated by 'check workspace for current list', matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Fully executable Python blocks (SDK setup, McpServer construction, Agent instantiation, streaming conversion) plus specific file paths make the guidance copy-paste ready, matching the level 3 anchor.

3 / 3

Workflow Clarity

Content is organized as a clear task catalog with a loose 'Next Steps' sequence, but there are no explicit validation checkpoints or feedback loops, matching level 2's 'sequence present but checkpoints missing or implicit' rather than level 3.

2 / 3

Progressive Disclosure

A clear overview with well-signaled one-level-deep references to sibling skills and external docs, with detail appropriately delegated out of SKILL.md, matching the level 3 anchor.

3 / 3

Total

11

/

12

Passed

Description

92%

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, concise description with concrete actions, natural trigger terms, and an explicit 'Use when' clause covering both what and when. Its main weakness is overlap with the sibling add-tools skill on the 'add tool' / MCP-server triggers.

Suggestions

Narrow the 'add tool' / 'Adding MCP servers' triggers to distinguish from the add-tools skill, e.g. reserve this skill for agent.py-level changes and route pure tool-permission grants to add-tools.

Consider dropping the generic 'change configuration' in favor of a more specific action to reduce residual overlap with neighboring skills.

DimensionReasoningScore

Specificity

"Modify agent code, add tools, or change configuration" lists multiple concrete actions in third-person imperative voice with no first/second-person usage, matching the 'lists multiple specific concrete actions' anchor rather than the less comprehensive level 2.

3 / 3

Completeness

It explicitly answers both 'what' (modify/add/change) and 'when' via a four-item 'Use when:' clause, matching the level 3 anchor for explicit triggers on both questions.

3 / 3

Trigger Term Quality

Natural trigger terms a user would actually say ('modify agent', 'add tool', 'change model', 'edit agent.py') give good coverage, matching the level 3 anchor rather than level 2's 'missing common variations'.

3 / 3

Distinctiveness Conflict Risk

Triggers 'add tool' and 'Adding MCP servers to agent' overlap with the sibling add-tools skill referenced in the body, so it could still trigger the wrong skill — matching level 2 rather than level 3's 'unlikely to conflict'.

2 / 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
databricks/app-templates
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.