CtrlK
BlogDocsLog inGet started
Tessl Logo

extension-creator

Create AiderDesk extensions by setting up extension files, defining metadata, implementing Extension interface methods, and updating documentation. Use when building a new extension, creating extension commands, tools, or event handlers.

68

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body is highly actionable and workflow-rich with strong validation feedback loops and a well-structured reference bundle. Its main weakness is verbosity from duplicated Process Overview content and a large inlined patterns section that could be pushed to references.

Suggestions

Collapse the 'Process Overview' section or fold it into the 'Rules' flows to remove the duplicated step listings for both Project/Global and In-Repo targets.

Trim the inlined 'Common Situations' patterns to one-line summaries that link to the corresponding reference (event-types.md, extension-interface.md, ui-components.md) instead of reproducing full code blocks in SKILL.md.

De-duplicate the validate-extension-ui.mjs invocation — state the command once in the validation rule and reference it from the flow sections.

DimensionReasoningScore

Conciseness

Content is dense and specific without basic-concept padding, but the 'Process Overview' section largely duplicates the 'Rules' flows and the validate command repeats three times, so it could be meaningfully tightened.

3 / 5

Actionability

Fully executable guidance throughout — copy-paste TypeScript snippets, exact method names, precise validator invocation, and concrete file paths covering the common extension cases.

5 / 5

Workflow Clarity

Both target flows are numbered with explicit validation steps (validate-extension-ui.mjs, type checking), a fix-and-revalidate feedback loop, and a Postconditions checklist for error recovery.

5 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references (all 11 exist) and organized assets, but the ~200-line inlined 'Common Situations' section duplicates API detail that already lives in the reference files.

4 / 5

Total

17

/

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.

The description is well-constructed: third-person voice, concrete actions, and an explicit 'Use when' clause with specific triggers. It carves out a distinct niche and answers both what and when clearly.

DimensionReasoningScore

Specificity

Lists several concrete actions ('setting up extension files, defining metadata, implementing Extension interface methods, and updating documentation') but omits sub-areas like UI components and config, so it falls short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both what (the four creation actions) and when ('Use when building a new extension, creating extension commands, tools, or event handlers') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases ('building a new extension, creating extension commands, tools, or event handlers'), but lacks synonyms and file extensions that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche ('AiderDesk extensions') with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (503 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 8 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 9 deeper-than-1-level

Warning

Total

13

/

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.