nl-to-constraints
Transforms natural language requirements (user stories, verbal descriptions, business rules) into formal specifications and constraints. Use when converting informal requirements into structured, testable specifications with explicit constraints. Outputs in multiple formats including BDD-style Given-When-Then, JSON Schema, and structured plain text requirements documents.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill nl-to-constraints94
Does it follow best practices?
Validation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It clearly specifies the transformation from informal to formal requirements, includes explicit 'Use when' guidance, and provides distinctive trigger terms that would help Claude select this skill appropriately from a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Transforms natural language requirements into formal specifications', with explicit input types (user stories, verbal descriptions, business rules) and output formats (BDD-style Given-When-Then, JSON Schema, structured plain text). | 3 / 3 |
Completeness | Clearly answers both what ('Transforms natural language requirements into formal specifications and constraints') AND when ('Use when converting informal requirements into structured, testable specifications with explicit constraints'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'user stories', 'business rules', 'requirements', 'specifications', 'constraints', 'Given-When-Then', 'BDD', 'JSON Schema'. Good coverage of domain terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on requirements transformation with distinct triggers like 'user stories', 'BDD', 'Given-When-Then', 'JSON Schema'. Unlikely to conflict with general documentation or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The concrete examples for each output format (BDD, JSON Schema, Plain Text) are particularly strong. The main weakness is some verbosity in the opening sections that explain capabilities Claude can infer from the actual instructions.
Suggestions
Remove or significantly condense the 'Core Capabilities' section - the numbered list of what the skill enables is redundant with the actual workflow instructions that follow.
Trim the opening preamble 'You are an expert requirements engineer...' as this adds no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary explanation (e.g., 'You are an expert requirements engineer' preamble, explaining what the skill enables). The core workflow and examples are useful, but the 'Core Capabilities' section is redundant since Claude can infer these from the actual instructions. | 2 / 3 |
Actionability | Provides concrete, executable examples throughout including regex patterns, complete JSON schema structures, BDD scenarios, and structured markdown output. The constraint extraction example shows exact input-to-output transformation that is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit validation step (Step 5). Each step has clear purpose and deliverables. The 'Validate and Refine' step includes specific checkpoints for completeness, consistency, and gap identification. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate references to external files (references/constraint_patterns.md, assets/specification_schema.json). Content is appropriately structured with quick-reference sections (Signal Words, Output Selection) separated from detailed workflow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
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.