CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-creator

Create and configure AiderDesk agent profiles by defining tool groups, approval rules, subagent settings, and provider/model selection. Use when setting up a new agent, creating a profile, or configuring agent tools and permissions.

95

1.28x
Quality

Does it follow best practices?

Impact

100%

1.28x

Average score across 3 eval scenarios

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.

The body is token-efficient, actionable, and well-structured with verified one-level-deep references. The main gap is informal validation guidance in the create step, which lacks an explicit validate-fix-retry loop for the destructive file-writing operation.

Suggestions

Replace the Step 6 instruction "Verify structure against references/profile-examples.md" with an explicit validation checkpoint, e.g. a concrete check (schema fields present, tool keys match tool-approval-guide.md) followed by an error-recovery loop: if validation fails, report mismatches and re-validate before writing files.

Add a concrete post-creation verification step (e.g., confirm `config.json` parses as valid JSON and the tool keys resolve to known tools) so the workflow has a clear feedback loop rather than an informal pre-write check.

State the default `maxIterations` (250) and `contextMemory` ("off") choices inline in the minimal config example or a brief defaults note so reviewers need not infer them from the prose.

DimensionReasoningScore

Conciseness

Lean and scannable with no padding of concepts Claude already knows; every section (Q&A steps, approval strategy, subagent config, minimal example) earns its place, matching the score-3 anchor.

3 / 3

Actionability

Provides a complete copy-paste config.json example plus exact mechanics (key format `{group}---{tool}`, approval values "always/ask/never", file paths) — fully executable guidance rather than pseudocode.

3 / 3

Workflow Clarity

A clear 6-step Q&A sequence with a single final approval checkpoint exists, but validation ("Verify structure against references/profile-examples.md") is informal and lacks an explicit validate-fix-retry feedback loop for a file-writing operation, matching the score-2 anchor of sequence present but checkpoints implicit.

2 / 3

Progressive Disclosure

A concise overview with a clearly signaled Resources section pointing to six real, one-level-deep bundle files (verified to exist with no nested references), matching the score-3 anchor.

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.

The description is concise, third-person, and answers both what the skill does and when to use it with concrete actions and explicit trigger guidance. It is clearly scoped to AiderDesk agent profiles, minimizing conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "defining tool groups, approval rules, subagent settings, and provider/model selection" — matches the score-3 anchor of several specific concrete actions rather than a single domain.

3 / 3

Completeness

Clearly answers both "what" (create/configure agent profiles via named properties) and "when" via an explicit "Use when..." clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Explicit "Use when setting up a new agent, creating a profile, or configuring agent tools and permissions" provides natural user phrasings; broad enough coverage of how a user would phrase the request, though it lacks product-name variants.

3 / 3

Distinctiveness Conflict Risk

Tied to the distinct "AiderDesk agent profiles" niche with triggers specific to agent setup and configuration, making overlap with unrelated skills unlikely.

3 / 3

Total

12

/

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

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
hotovo/aider-desk
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.