CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-agent

Generates Custom Agent files (.github/agents/*.agent.md) with persona-based configurations, specialized tool sets, and role-specific cognitive architectures. Use when the user requests a specialized role or perspective (Security Auditor, Documentation Writer, Release Engineer, etc.). Creates agents with defined identity, constrained tools, and thinking processes aligned to their role. Not for general capabilities—use generate-agent-skills for those.

83

1.15x
Quality

77%

Does it follow best practices?

Impact

90%

1.15x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/generate-agent/SKILL.md

The canonical home for this skill is generate-agent in canonical/copilot-collections

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-structured, actionable 7-step generator workflow with real validation commands, a checklist, and a genuinely progressive reference bundle (every referenced file exists and is one level deep). Its weaknesses are duplicated example content that belongs in the reference files, and a validation step that relies on a script owned by a sibling skill rather than a local one.

Suggestions

Trim the inline duplicated material from SKILL.md — the two full <thinking_process> XML examples in Step 4, the tool table and per-role tool examples in Step 3, and the 'Examples of Common Agents' section restate content already in references/cognitive_architecture_patterns.md, references/tool_selection_guide.md, and the Overview; keep one compact example each and let the cat-loaded references carry the detail.

Make Step 6 self-contained: either copy or vendor the validation script into this skill's scripts/ directory (the command currently points at .github/skills/generate-agent-skills/scripts/validate_skill.py, which is outside this bundle and may not exist), or provide a fallback check such as a Python YAML parse of the frontmatter.

Add an explicit feedback loop to Step 6 — after each validation command, state what to do on failure (fix the frontmatter/tools list, re-run the check) so the workflow matches the validate → fix → re-validate pattern instead of just listing checks.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries notable duplication: full thinking-process XML examples in Step 4 overlap references/cognitive_architecture_patterns.md, the tool table and per-role tool examples in Step 3 overlap references/tool_selection_guide.md's "Common Agent Types" section, and the "Examples of Common Agents" section restates the Overview's example roles. It could be tightened by trusting the per-step reference loads rather than re-inlining their content, so it fits 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

Concrete executable commands appear throughout — `cat references/...` loads, the `python3 .github/skills/generate-agent-skills/scripts/validate_skill.py --path .github/agents/` validation, the `grep -E "<thinking_process>|</thinking_process>"` check, explicit file-naming conventions, and a final checklist and output template. The main gap is that the validation command depends on a script in a sibling skill's bundle (`.github/skills/generate-agent-skills/scripts/`) rather than this skill's own scripts/ directory, so it may not be copy-paste runnable — 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

The 7-step workflow (intent validation → role analysis → tool selection → architecture → template population → validation → usage guidance) is clearly sequenced with an explicit validation step, commands, and a final checklist in Step 6. It falls short of the top anchor only because there is no explicit error-recovery feedback loop (e.g., what to do when validation fails or the frontmatter check errors) — 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The bundle structure is good: each step signals a one-level-deep reference via an explicit `cat` command, all four referenced paths exist (references/role_analysis_checklist.md, tool_selection_guide.md, cognitive_architecture_patterns.md, assets/agent_template.md), and a Resources section annotates each file. It misses the top anchor because substantial example content that the references exist to carry (thinking processes, tool-set tables, per-role examples) is duplicated inline in SKILL.md, so content is not appropriately split — 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

15

/

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: it states what the skill produces (with the concrete output path), when to use it with natural role-name triggers, and explicitly redirects the closest competing skill. The only weakness is mild redundancy between the first and third sentences, which slightly dilutes specificity without creating conflicts.

DimensionReasoningScore

Specificity

"Generates Custom Agent files (.github/agents/*.agent.md) with persona-based configurations, specialized tool sets, and role-specific cognitive architectures" names the concrete artifact (with path pattern) and several specific components; the later "Creates agents with defined identity, constrained tools, and thinking processes" largely restates the first sentence, which is mild padding rather than added coverage, so it sits at 'several specific actions; minor gaps' rather than the fully comprehensive anchor.

4 / 5

Completeness

It explicitly answers both parts: the "what" ("Generates Custom Agent files... with persona-based configurations, specialized tool sets, and role-specific cognitive architectures") and the "when" ("Use when the user requests a specialized role or perspective"), with concrete trigger examples and an explicit negative boundary ("Not for general capabilities—use generate-agent-skills for those"), matching the top anchor.

5 / 5

Trigger Term Quality

"Use when the user requests a specialized role or perspective (Security Auditor, Documentation Writer, Release Engineer, etc.)" gives natural role-name triggers plus the "Custom Agent" / ".agent.md" terms, but omits common variations users would actually say such as "persona", "create an agent", or role synonyms beyond the three listed examples — good coverage with a few natural terms missing, not the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The explicit disambiguation clause "Not for general capabilities—use generate-agent-skills for those" plus the distinctive "specialized role or perspective" framing carve out a clear niche (role/persona agents vs. capability skills) with minimal conflict risk; no neighboring-anchor fit is better.

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
canonical/copilot-collections
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.