CtrlK
BlogDocsLog inGet started
Tessl Logo

create-skill

Create a new Claude Code skill (slash command) for this project. Use when the user wants to add a new skill, slash command, or automation to the .claude/skills directory.

86

1.73x
Quality

81%

Does it follow best practices?

Impact

99%

1.73x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a solid, well-structured skill that provides actionable guidance for creating new Claude Code skills. Its main strength is the complete frontmatter template with field documentation. Weaknesses include some generic advice Claude doesn't need and a lack of validation steps after skill creation.

Suggestions

Add a validation step after creation, e.g., 'Verify the YAML frontmatter parses correctly and the file is at the expected path'

Remove generic guidelines Claude already knows (e.g., 'Write clear, actionable instructions', 'Include concrete steps') to improve conciseness

DimensionReasoningScore

Conciseness

Mostly efficient but includes some unnecessary guidance that Claude already knows (e.g., 'Ask clarifying questions if the skill name or purpose is unclear', 'Write clear, actionable instructions'). The frontmatter template is useful reference material, but some guidelines are generic advice Claude doesn't need.

2 / 3

Actionability

Provides a concrete, copy-paste-ready YAML frontmatter template with all fields documented, specific naming conventions, and clear process steps. The skill file format section is a fully executable reference that Claude can directly use to create new skills.

3 / 3

Workflow Clarity

The 4-step process is clearly sequenced and includes a conflict-check step, but lacks validation checkpoints — there's no step to verify the created skill file is valid (e.g., checking YAML frontmatter parses correctly, verifying the skill appears in the slash command menu). For a file-creation workflow, a validation step would be valuable.

2 / 3

Progressive Disclosure

For a skill of this size (~50 lines of meaningful content), the structure is well-organized with clear sections (Process, Skill File Format, Guidelines, After Creation). No external references are needed, and the content is appropriately scoped for a single file.

3 / 3

Total

10

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid description that clearly communicates both what the skill does and when to use it, with good trigger term coverage. The main weakness is that the 'what' portion is somewhat thin — it only mentions 'create' without elaborating on specific sub-actions or details of what creating a skill entails. Overall it performs well for skill selection purposes.

Suggestions

Add more specific concrete actions beyond 'create', such as 'generates YAML frontmatter, writes markdown instructions, and saves to .claude/skills/' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (Claude Code skills/slash commands) and one action (create), but doesn't list multiple concrete actions like editing, listing, or configuring skills.

2 / 3

Completeness

Clearly answers both what ('Create a new Claude Code skill (slash command) for this project') and when ('Use when the user wants to add a new skill, slash command, or automation to the .claude/skills directory').

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'skill', 'slash command', 'automation', '.claude/skills directory', 'add a new skill'. Good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Very specific niche — creating Claude Code skills/slash commands in the .claude/skills directory. Unlikely to conflict with other skills due to the precise domain and file path reference.

3 / 3

Total

11

/

12

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.

Validation9 / 11 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

9

/

11

Passed

Repository
anyscale/terraform-kubernetes-anyscale-foundation-modules
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.