CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-agents

Scaffold a multi-agent AI setup for any repo. Scans the codebase, interviews the developer, generates agent configs for whichever AI tools the repo uses (Copilot, Claude Code, Cursor, Codex, Windsurf). Use when asked to "set up agents", "scaffold Copilot agents", or "create an AGENTS.md".

Quality

70%

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 ./plugins/platform-skills/skills/setup-agents/SKILL.md

The canonical home for this skill is setup-agents in nitinjain999/platform-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, well-sectioned router document whose only serious flaw is that everything it routes to is missing: the bundle contains no reference files, so the skill's executable substance exists nowhere. The dangling references sink actionability and progressive disclosure, and the absence of any validation step caps workflow clarity.

Suggestions

Ship the reference files the body depends on: at minimum references/setup-agents.md plus the mode-specific files it routes to, so 'load the appropriate reference file and follow its steps exactly' resolves to real content.

Add a validation checkpoint to the generate/upgrade modes (e.g., verify generated configs parse and match the detected tool list before finishing), since these modes batch-write config files across multiple AI tools.

Remove the duplicated mode descriptions between the Modes section and the wizard block — the wizard can display the mode list without restating each mode's summary twice.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, no padding. Minor redundancy: the four mode descriptions appear twice (Modes section and the wizard block) and the opening line restates the description, so not a 5.

4 / 5

Actionability

The wizard dialog and mode definitions are concrete, but all executable guidance is delegated: "load the appropriate reference file and follow its steps exactly" — and references/setup-agents.md does not exist in the bundle (no references/ directory at all). The specific steps to execute are missing everywhere, matching the 2 anchor (high-level hints, missing steps); not 1 because the routing and wizard text are themselves concrete.

2 / 5

Workflow Clarity

A coherent top-level sequence exists (no args → wizard → load mode reference → follow steps → closing log), but per-mode steps are absent and there are no validation checkpoints for a generate mode that writes many config files across tools — a batch-write operation, which caps workflow_clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Sections are well-organized and the reference index is clearly signaled as a one-level router ("read this first. It routes to mode-specific files"), but scored against the actual bundle structure the referenced files are entirely missing — no references/, scripts/, or assets/ directories exist. The primary navigation target is dangling, so the disclosure structure fails at its main job; not 1 because the SKILL.md body itself remains sectioned and readable rather than a monolith.

2 / 5

Total

11

/

20

Passed

Description

83%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: concrete actions, enumerated target tools, and explicit quoted trigger phrases that answer both what and when. The only weaknesses are incomplete capability coverage (operating modes unmentioned) and trigger terms limited mostly to Copilot phrasing.

DimensionReasoningScore

Specificity

Lists three concrete actions ("Scans the codebase, interviews the developer, generates agent configs") plus five named tools (Copilot, Claude Code, Cursor, Codex, Windsurf). Not 5 because coverage has gaps — the upgrade/add/review operating modes are not mentioned; not 3 because it names several specific actions, not just 1-2.

4 / 5

Completeness

Explicitly answers both questions: what ("Scans the codebase, interviews the developer, generates agent configs") and when ("Use when asked to 'set up agents', 'scaffold Copilot agents', or 'create an AGENTS.md'") with concrete trigger phrases — a direct match to the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say: "set up agents", "scaffold Copilot agents", "create an AGENTS.md". Not 5 because trigger variants for the other supported tools (Cursor, Windsurf, Codex, Claude Code) and common synonyms are missing; not 3 because the quoted triggers are natural and well-chosen, beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (agent-config scaffolding for named AI coding tools) with distinct triggers like "scaffold Copilot agents" and "create an AGENTS.md". Not 5 because "set up agents" is a fairly generic phrase that could overlap with other agent-related skills; not 3 because the domain and most triggers are well differentiated.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

nitinjain999/platform-skills

Path

plugins/platform-skills/skills/setup-agents/SKILL.md

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.