ext-develop

Build, debug, or publish an OpenClacky extension — scaffold a new one from an idea, fix a broken/invisible panel/api/skill/agent, or ship it to the marketplace. Trigger on create/start extension, plugin, panel, ext verify error, "won't load", "not showing up", publish/ship/unpublish an extension.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

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

A high-signal, actionable skill body with executable code, clear sequenced workflows and validation feedback loops, and well-organized one-level-deep external references.

Dimension	Reasoning	Score
Conciseness	The body is dense with domain-specific ground truth (slot names, error codes, contracts) and never explains concepts Claude already knows; every line earns its place. It avoids the verbosity penalty by assuming Claude's competence throughout.	3 / 3
Actionability	Provides fully executable commands ('clacky ext new <id>', 'clacky ext verify', 'clacky ext publish <id> --force') and complete, copy-paste-ready Ruby/JS code examples rather than pseudocode.	3 / 3
Workflow Clarity	Three paths (Scaffold / Debug & verify / Publish) are clearly sequenced with numbered steps and explicit validation checkpoints — 'fix ONE issue at a time, re-run verify, repeat until clean' and 'End with a clean clacky ext verify and have the user reload'.	3 / 3
Progressive Disclosure	External reference material is one level deep and clearly signaled via authoritative doc URLs fetched with web_fetch + max_length; no nested bundle references exist and the body is organized into well-signaled sections.	3 / 3
	Total	12 / 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.

A strong, third-person description that names specific capabilities, supplies natural trigger terms, and explicitly states when to use the skill with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'scaffold a new one from an idea', 'fix a broken/invisible panel/api/skill/agent', 'ship it to the marketplace' — matching the score-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what it does' (build/debug/publish) and 'when' via the explicit 'Trigger on ...' clause, satisfying the score-3 anchor for both what AND when.	3 / 3
Trigger Term Quality	Rich natural trigger terms users would actually say — 'create/start extension', 'plugin', 'ext verify error', 'won't load', 'not showing up', 'publish/ship/unpublish' — covering common variations.	3 / 3
Distinctiveness Conflict Risk	Carved to a clear niche (OpenClacky extension development) with distinct, specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (527 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: clacky-ai/openclacky
Path: lib/clacky/default_extensions/ext-studio/skills/ext-develop/SKILL.md
Commit: 4aea278

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.