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.

76

Quality

93%

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.

This is a strong, well-structured skill that provides concrete, executable guidance for multiple agent modification tasks. Its main weakness is the lack of validation checkpoints — after modifying agent code, there's no explicit step to verify changes work before proceeding. The progressive disclosure and conciseness are excellent, with clear cross-references to related skills.

Suggestions

Add a brief validation step after each modification type (e.g., 'Run `python -c "from agent_server.agent import agent; print(agent.name)"` to verify changes load correctly') to improve workflow clarity.

Consider adding a short 'After any modification' checklist at the end that sequences: modify → test locally (link to run-locally skill) → deploy (link to deploy skill), making the overall workflow explicit.

DimensionReasoningScore

Conciseness

The content is lean and well-structured. It avoids explaining what MCP servers are, what agents are, or how Python works. Every section provides concrete code without unnecessary preamble. The table format for key files is efficient.

3 / 3

Actionability

Every section provides executable, copy-paste ready Python code with concrete examples — SDK setup, adding MCP servers, changing models, modifying instructions, and running the agent both streaming and non-streaming. Model names and URL patterns are specific.

3 / 3

Workflow Clarity

The skill covers multiple modification tasks but presents them as independent recipes rather than a sequenced workflow. There are no validation checkpoints — e.g., no guidance on verifying the agent works after modification, no 'test locally before deploying' step integrated into the flow. The 'Next Steps' section hints at testing but doesn't integrate it as a validation checkpoint.

2 / 3

Progressive Disclosure

Content is well-organized with clear sections for each task. References to other skills (add-tools, discover-tools, run-locally, deploy) are one level deep and clearly signaled. External resources are listed concisely. The main file is highlighted upfront with a supporting table for context.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its scope around agent code modification and configuration. It uses an explicit 'Use when' clause with numbered trigger scenarios and natural keywords. The description is concise, uses third person voice, and provides enough specificity to distinguish it from other coding-related skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Modify agent code', 'add tools', 'change configuration', 'Adding MCP servers', 'Changing agent instructions', 'Understanding SDK patterns'. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (modify agent code, add tools, change configuration) and 'when' with an explicit 'Use when:' clause listing four specific trigger scenarios with concrete examples.

3 / 3

Trigger Term Quality

Includes highly natural trigger terms users would say: 'modify agent', 'add tool', 'change model', 'edit agent.py', 'MCP servers', 'agent instructions', 'SDK patterns'. These cover common variations of how users would phrase requests.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche around agent code modification, MCP servers, and SDK patterns. The specific mentions of 'agent.py', 'MCP servers', and 'SDK patterns' make it highly distinguishable from general coding or configuration skills.

3 / 3

Total

12

/

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.

Validation11 / 11 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.