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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

Highly actionable, well-sequenced content with strong validation feedback loops and copy-paste code. The main weakness is progressive disclosure: a large single-file body inlines reference material that could be moved into separate reference files now that the body exceeds the overview role.

Suggestions

Move the dense 'Reference: the contracts' material (valid slot names, Clacky.ext API surface, error-code fix list, allowed ext.yml fields) into separate reference files under references/ and point to them one level deep, leaving SKILL.md as a tighter overview.

Trim the session-source-grouping paragraph and other long inline rationales to the essential rule plus a one-line reason, since the contract docs they reference already cover the detail.

Add a short table of contents or 'which section do I need' jump links near the top so the three paths (Scaffold / Debug & verify / Publish) and the contracts reference are discoverable without scrolling the whole file.

Dimension	Reasoning	Score
Conciseness	Mostly lean with terse hard-rules, tables, and tight code blocks, but a few dense reference sections (session source grouping, the full slot/field lists) carry explanation that could be trimmed — efficient overall with minor over-explanation.	4 / 5
Actionability	Fully executable guidance throughout — concrete commands (clacky ext new, clacky ext verify), copy-paste-ready code blocks for view.js/handler.rb/tools, and a per-error-code fix table covering the common cases.	5 / 5
Workflow Clarity	Clear sequenced workflows with explicit validation checkpoints and feedback loops — Scaffold runs verify then user-reload confirmation, and Debug & verify fixes one issue, re-runs verify, and confirms only when valid.	5 / 5
Progressive Disclosure	Well-headed section structure and external-doc fetching keep it navigable, but no bundle reference files exist, so dense ground-truth reference (slot lists, error codes, API surface) is inlined in SKILL.md rather than split into one-level-deep reference files.	3 / 5
	Total	17 / 20 Passed

Description

95%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, third-person description that clearly states capabilities and provides an explicit, natural-language trigger clause with concrete error phrases. Minor specificity gap (not every sub-action enumerated) keeps it just below full marks on that one dimension.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('scaffold a new one from an idea, fix a broken/invisible panel/api/skill/agent, or ship it to the marketplace') with only minor gaps in sub-action coverage, matching the anchor that lists several specific actions.	4 / 5
Completeness	Explicitly answers both what (build/debug/publish an OpenClacky extension) and when via the 'Trigger on ...' clause with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms and concrete error phrases — 'create/start extension', 'plugin', 'ext verify error', 'won't load', 'not showing up', 'publish/ship/unpublish' — matching the comprehensive-synonyms anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (OpenClacky extension development) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (592 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

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

Reviewed: 2 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.