CtrlK
BlogDocsLog inGet started
Tessl Logo

create-agent

Create a custom agent (.agent.md) for a specific job.

52

Quality

57%

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 ./extensions/copilot/assets/prompts/skills/create-agent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is admirably lean and well-organized into clear phases with concrete extraction and clarification prompts, but its actionability and progressive disclosure are undercut by deferring the actual agent template to an unbundled external file without clear navigation. Validation checkpoints in the iteration loop are also implicit rather than explicit.

Suggestions

Surface the .agent.md template structure inline or as a bundled, clearly-linked reference file so the skill is self-contained and actionable.

Add an explicit validation step in the Iterate loop (e.g. re-read the saved .agent.md and confirm it has name, description, tools, and trigger criteria before finalizing).

Convert external references to proper markdown links and verify the referenced files exist in the bundle so navigation is unambiguous.

DimensionReasoningScore

Conciseness

The body is ~25 lines with no padding and no explanations of concepts Claude already knows; it assumes competence and every line ('Guide the user to create an `.agent.md`', the bullet extraction targets) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete extraction targets (role/persona, tool preferences, domain scope) and specific clarifying questions, but the actual .agent.md format/template is fully deferred to the external 'agents.md', so Claude cannot produce the artifact from this skill alone — 'some concrete guidance but incomplete.'

2 / 3

Workflow Clarity

The Extract → Clarify → Iterate phases are clearly sequenced with numbered iteration steps and a soft feedback loop ('Identify the most ambiguous or weak parts and ask about those'), but there is no explicit validation checkpoint confirming the drafted agent is well-formed or effective, leaving it at the 'sequence present but checkpoints implicit' level.

2 / 3

Progressive Disclosure

The body references external material ('Load and follow **agents.md**', 'Related skill: `agent-customization`') at one level of depth, but these are not clearly signaled as file links (no markdown link syntax) and no bundle files are actually present under references/scripts/assets to back them, fitting 'references present but not clearly signaled.'

2 / 3

Total

9

/

12

Passed

Description

50%

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 concise and third-person/imperative in voice, correctly naming the artifact and action, but it omits any 'Use when...' trigger guidance and only gestures at a single action. It is competent but generic, sitting solidly at the midpoint of the scale.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to create or customize a dedicated agent for a recurring specialized job.'

Broaden trigger term coverage to include natural variations like 'agent file', 'agent configuration', and 'set up an agent'.

Differentiate from the related agent-customization skill in the description so it does not appear to overlap.

DimensionReasoningScore

Specificity

Quotes 'Create a custom agent (.agent.md) for a specific job' — it names one concrete action and the target artifact, but does not list multiple specific actions, so it sits at the 'domain and some actions' level rather than the comprehensive list at level 3.

2 / 3

Completeness

It clearly states what ('Create a custom agent (.agent.md)') but gives no 'Use when...' clause or equivalent trigger guidance for when to invoke it; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Terms 'custom agent' and '.agent.md' are natural things a user might say, but coverage is thin with no common variations such as 'agent file', 'agent configuration', or 'make an agent', matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The '.agent.md' niche is fairly distinct, but the body explicitly names a 'Related skill: agent-customization' and the description could overlap with that sibling skill, leaving it at the 'somewhat specific but could still overlap' level rather than a clearly unconflicted niche.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.