This description is severely underdeveloped, functioning more as a topic label than a functional skill description. It lacks concrete actions, trigger terms, and explicit guidance on when Claude should select this skill. Without these elements, Claude cannot reliably choose this skill from a pool of alternatives.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Designs syntax and grammar rules, creates type systems, generates parser specifications, defines semantics'

Include a 'Use when...' clause with natural trigger terms like 'create a language', 'DSL', 'domain-specific language', 'syntax design', 'language grammar', 'compiler design'

Specify the scope and deliverables, e.g., 'Produces language specifications, BNF grammars, and implementation guidance for custom programming languages or DSLs'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language with no concrete actions. 'Designing a new programming language' doesn't specify what actions the skill performs (e.g., syntax design, type system creation, parser generation).	1 / 3
Completeness	Missing both clear 'what' (no specific capabilities listed) and 'when' (no explicit trigger guidance or 'Use when...' clause). The description is essentially just a topic label.	1 / 3
Trigger Term Quality	Contains only the generic phrase 'programming language' with no natural variations users might say like 'create a language', 'language design', 'syntax', 'grammar', 'compiler', or 'DSL'.	1 / 3
Distinctiveness Conflict Risk	The domain of 'programming language design' is somewhat specific and wouldn't overlap with most common skills, but the vague phrasing could still conflict with general coding or documentation skills.	2 / 3
	Total	5 / 12 Passed

Implementation

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

This skill content is completely empty aside from a TODO placeholder. It provides zero value in its current state - no instructions, examples, workflows, or references for designing a programming language. The skill needs to be fully written before it can be useful.

Suggestions

Add concrete steps for the language design process (e.g., defining syntax, semantics, type system, parser implementation)

Include executable code examples showing how to implement key language components (lexer, parser, AST)

Provide a clear workflow with validation checkpoints (e.g., grammar validation, test suite execution)

Structure content with a quick start section and references to detailed guides for advanced topics like optimization or runtime implementation

Dimension	Reasoning	Score
Conciseness	The content is essentially empty with only a TODO placeholder, providing no actual instructions or guidance whatsoever.	1 / 3
Actionability	No concrete guidance, code, commands, or examples are provided - just a placeholder indicating content needs to be added.	1 / 3
Workflow Clarity	No workflow, steps, or processes are defined; the skill body contains no actionable sequence for designing a programming language.	1 / 3
Progressive Disclosure	No structure, organization, or references exist - the content is a single TODO line with no navigation or content hierarchy.	1 / 3
	Total	4 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

7 days ago

Table of Contents

Discovery Implementation Validation