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.

1.62x

Quality

83%

Does it follow best practices?

Impact

96%

1.62x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

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

Actionable and well-structured with concrete templates and a clear multi-step workflow. The main weakness is conciseness: large inlined format examples and general reference sections inflate the body, and the workflow lacks an explicit validation feedback loop.

Suggestions

Move the full JSON Schema and plain-text worked examples into references and keep only a compact representative snippet in SKILL.md to reduce token load.

Add an explicit feedback loop to Step 5 (e.g., "If validation fails, return to Step 3 to re-extract constraints and regenerate").

Trim the "Best Practices" and "Signal Words Reference" sections to only non-obvious, skill-specific guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the body inlines full worked examples for all three output formats (BDD, a large JSON Schema block, and a plain-text doc) plus general "Best Practices" and "Signal Words Reference" sections that could be tightened or moved to references.	3 / 5
Actionability	Provides copy-paste-ready templates and a fully worked User Registration example across constraint extraction, Gherkin, JSON Schema, and plain-text formats, covering the common cases concretely.	5 / 5
Workflow Clarity	A clear five-step sequence (Analyze → Classify → Extract → Generate → Validate) with a validation checklist in Step 5, but no explicit error-recovery feedback loop ("if validation fails, return to step X").	4 / 5
Progressive Disclosure	Well-signaled one-level-deep references to real files (references/constraint_patterns.md and assets/specification_schema.json) plus a Resources section, but substantial full-format examples are inlined in SKILL.md rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states both what the skill does and when to use it, with concrete output formats and distinct trigger terms. The only minor gap is a few missing natural-phrase synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions—"Transforms natural language requirements ... into formal specifications and constraints" and outputs across "BDD-style Given-When-Then, JSON Schema, and structured plain text"—giving comprehensive coverage of the skill's actions.	5 / 5
Completeness	Explicitly answers both what ("Transforms ... into formal specifications and constraints") and when ("Use when converting informal requirements into structured, testable specifications with explicit constraints") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Good coverage of natural terms ("user stories", "verbal descriptions", "business rules", "BDD-style Given-When-Then", "JSON Schema") but a few common variations a user might say are missing; no file extensions apply to this abstract domain.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (informal-requirements → formal-specification transformation) with distinct triggers like "user stories", "business rules", and "BDD", minimizing overlap with other skills.	5 / 5
	Total	19 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/nl-to-constraints/SKILL.md
Commit: 4f38503

Reviewed: 19 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.