create-component

Create a new Fx component using the modern def/fx/impl pattern (NOT legacy)

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/create-component/SKILL.md

Quality

Content

77%

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

This is a strong, actionable skill with a clear multi-step workflow and explicit validation steps. It provides concrete file structures, specific function names, and CLI commands that make it directly executable. Minor improvements could be made in conciseness (reducing some repetition between instructions and critical rules) and progressive disclosure (extracting detailed file templates into supporting documents).

Suggestions

Consider extracting detailed file content templates (def/component.go, fx/fx.go, impl/<component>.go) into a separate TEMPLATES.md reference file to improve progressive disclosure and reduce main skill length.

The 'Critical Rules' section partially repeats guidance already given in step 5 — consider consolidating to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary verbosity, such as step 2 asking the user questions that could be more tightly expressed. The critical rules summary at the end is a nice touch but partially repeats what's already stated in the instructions. Overall reasonably lean but could be tightened.	2 / 3
Actionability	Provides concrete directory structures, specific file names and their contents, exact function names to use (fxutil.ProvideComponentConstructor), specific CLI commands for validation and module creation, and clear usage examples. The guidance is specific enough to be directly executable.	3 / 3
Workflow Clarity	The 9-step workflow is clearly sequenced from parsing arguments through validation. Step 3 explicitly instructs reading reference examples before writing code. Step 9 provides a concrete validation command with an explicit feedback loop ('Fix any errors and re-run until clean'). The workflow covers the full lifecycle including registration and wiring.	3 / 3
Progressive Disclosure	The content is well-structured with clear sections, but it's all inline in a single file with no references to supporting documents. For a skill of this complexity (multiple file templates, go.mod patterns, bundle wiring), separate reference files for file templates or detailed patterns would improve organization. However, no bundle files are provided, so this is evaluated in isolation.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 reasonably specific about its niche—creating Fx components with a modern pattern—and clearly distinguishes itself from legacy approaches. However, it lacks an explicit 'Use when...' clause and could benefit from listing additional concrete actions and natural trigger terms to improve discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, scaffold, or add a new Fx component or mentions the def/fx/impl pattern.'

Include additional natural trigger terms users might say, such as 'scaffold component', 'new module', 'Fx dependency injection', or the specific framework name if applicable.

Dimension	Reasoning	Score
Specificity	Names a specific domain (Fx component creation) and a specific pattern (def/fx/impl), but only describes one action ('Create') without listing additional concrete capabilities like testing, modifying, or migrating components.	2 / 3
Completeness	Clearly answers 'what' (create a new Fx component using the modern pattern), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Fx component', 'def/fx/impl pattern', and 'legacy', which are useful triggers. However, these are fairly technical/framework-specific and may miss natural user phrasings like 'new component', 'scaffold', or the framework name itself if it's commonly referred to differently.	2 / 3
Distinctiveness Conflict Risk	The description is highly specific to a particular framework pattern (def/fx/impl) and explicitly distinguishes itself from legacy approaches, making it very unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: DataDog/datadog-agent
Commit: 554e219

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.