CtrlK
BlogDocsLog inGet started
Tessl Logo

create-component

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

62

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/create-component/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The content is concise, highly actionable, and well-sequenced with a real validation feedback loop. It appropriately keeps everything inline given there are no bundle files and is cleanly sectioned.

DimensionReasoningScore

Conciseness

The body is lean and instruction-focused with no concept-explanation padding; every section (parse arguments, directory tree, file rules, validation) earns its place and assumes Claude's competence, matching the level-3 anchor.

3 / 3

Actionability

Provides a concrete directory structure, specific file-creation patterns, exact commands ('dda inv create-module', 'dda inv lint-components lint-fxutil-oneshot-test github.lint-codeowner'), and copy-paste-ready usage examples, matching the level-3 anchor.

3 / 3

Workflow Clarity

A clear 9-step sequence includes an explicit validation checkpoint (step 9) with a fix-and-re-run feedback loop ('Fix any errors and re-run until clean'), matching the level-3 anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are referenced; the single ~70-line file is well-organized into Instructions, Critical Rules, and Usage sections, which is appropriate organization for a skill of this size, matching the level-3 anchor per the simple-skills scoring note.

3 / 3

Total

12

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 clearly conveys the task and the relevant technical pattern but omits an explicit 'when to use' trigger and natural-language trigger terms, capping several dimensions at 2. It is specific to its niche but not fully user-facing in voice.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating or scaffolding a new Fx component, or when the user asks to add a component to a bundle'.

Include natural trigger terms users would actually say, such as 'scaffold', 'component', 'bundle', and 'add component', alongside the def/fx/impl framing.

Convert to third-person action phrasing and list concrete actions ('scaffolds def/, fx/, and impl/ sub-packages, wires modules.yml, runs dda inv lint') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('Fx component') and the structural pattern ('modern def/fx/impl pattern') but describes only the single creation action rather than listing multiple concrete actions, matching the level-2 anchor.

2 / 3

Completeness

States what the skill does ('Create a new Fx component using the modern def/fx/impl pattern') but provides no explicit 'Use when...' trigger, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Includes relevant terms like 'Fx component', 'def/fx/impl pattern', and 'component', but leans technical and omits common natural variations a user would say; matches the level-2 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The def/fx/impl framing and '(NOT legacy)' give it a specific niche, but the absence of an explicit trigger leaves some overlap risk with sibling component-creation skills, matching the level-2 anchor.

2 / 3

Total

8

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
DataDog/datadog-agent
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.