ac-spec-parser

Parse and validate project specifications. Use when loading YAML/JSON specs, validating spec structure, extracting requirements, or converting between spec formats.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ac-spec-parser/SKILL.md

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.

The body is well-structured and actionable, with executable Quick Start code and clear sectioning that points to a real bundle file for full implementation. The main gaps are a redundant Purpose section and a workflow that omits an explicit validation feedback loop.

Suggestions

Add an explicit validation feedback loop to the Workflow, e.g. after 'Validate': 'If validation fails, review the errors against the Validation Rules, fix the spec, and re-validate before exporting.'

Remove or merge the 'Purpose' section into the intro line, since it restates the frontmatter description verbatim and adds no new information.

Make the Workflow steps runnable by adding the corresponding script/command for each (e.g., the parse invocation from Quick Start) so the sequence is copy-paste ready rather than labeled.

Dimension	Reasoning	Score
Conciseness	The body is efficient with executable code, a schema example, and terse lists; the only over-explanation is the 'Purpose' section restating the frontmatter description, so it fits 'efficient; minor instances that could be trimmed' rather than the lean level-5.	4 / 5
Actionability	Provides an executable Quick Start snippet and concrete validation rules, but the workflow steps are high-level labels without runnable commands and the API detail lives entirely in the referenced file, leaving minor gaps versus fully copy-paste-ready level 5.	4 / 5
Workflow Clarity	The 5-step Workflow (Load, Parse, Validate, Normalize, Export) is a clear sequence with validation called out as a distinct step; it lacks an explicit validate-then-fix feedback loop, but parsing specs is non-destructive so the level-3 cap does not apply, placing it at level 4 with minor validation gaps.	4 / 5
Progressive Disclosure	Well-organized sections with a one-level-deep, real reference to scripts/spec_parser.py (verified to exist) that holds the bulk of the API; the inlined schema example is reasonable for an overview, giving good structure with minor organization gaps rather than the cleanly-split level 5.	4 / 5
	Total	16 / 20 Passed

Description

83%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.

The description is strong: it states concrete capabilities and pairs them with an explicit, multi-trigger 'Use when' clause that answers both what and when. Minor room to improve distinctiveness and trigger synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Parse and validate', 'loading YAML/JSON specs', 'extracting requirements', 'converting between spec formats' — with only minor gaps in coverage, matching the 'several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	Explicitly answers both what ('Parse and validate project specifications') and when ('Use when loading YAML/JSON specs, validating spec structure, extracting requirements, or converting between spec formats') with concrete trigger phrases, matching the level-5 anchor exactly.	5 / 5
Trigger Term Quality	Good keyword coverage with natural user phrases ('loading YAML/JSON specs', 'validating spec structure', 'extracting requirements') and explicit format names, though a few natural synonyms are missing, so it sits below the comprehensive level-5 anchor.	4 / 5
Distinctiveness Conflict Risk	The 'project specifications' niche with spec-format triggers is mostly distinct from generic parsing skills, with only minor overlap risk against general file-parsing skills, fitting level 4 rather than the clear-niche level 5.	4 / 5
	Total	17 / 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: fernandezbaptiste/Skrillz
Path: skills/ac-spec-parser/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.