CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aet-req-review

Gate pipeline for requirement deliverables — enforces automated quality gates and interactive user validation before handover. Trigger when: (1) structured PRD/spec/SDD reviews are required, (2) executing a Stage demanding review-then-revision cycles, (3) workflows necessitate HCritic automated checks coupled with user-in-the-loop revision.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./jiuwenclaw/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 a well-sequenced, highly actionable orchestration pipeline with explicit validation loops and error handling. Its main cost is redundancy — several rules are restated across <guideline>, <instruct>, <constraint>, and <condition> — which inflates token usage without adding information.

Suggestions

State each rule once (e.g., the 2-iteration halt and never-re-ask rules) in a single canonical section and cross-reference it from <condition> instead of repeating it in <guideline>, <instruct>, and <constraint>.

Reconcile the subagent tooling guidance: R1 prescribes subagent_spawn/subagent_wait with a task_tool caveat, while R2 flatly says "use task_tool" — pick one canonical instruction and apply it to both.

Provide a concrete fill-in template for the R3 review-results output and the R4 transition message instead of bullet-list descriptions.

DimensionReasoningScore

Conciseness

The body is mostly tight operational directives, but the 2-iteration halt rule is repeated in <guideline>, <constraint>, and <condition>, the "never re-ask" rule appears three times, and several rationales (test -f portability, free-text confirmation) run long.

3 / 5

Actionability

Concrete tool calls (subagent_spawn/subagent_wait, task_tool, ask_user, sdd_advance, write_file), a copy-paste JSON template, and a full subagent prompt template make most guidance executable; R2's delegation spec and the R3/R4 output formats are described rather than templated.

4 / 5

Workflow Clarity

R1→R4 are clearly sequenced with explicit IF/THEN routing in <condition>, gate feedback loops capped at 2 iterations, error-recovery options, and a decision table for empty/skip/cancel — explicit validation checkpoints throughout.

5 / 5

Progressive Disclosure

A self-contained single file (no bundle files exist) with clear tag- and header-based structure; only minor gaps such as the inlined subagent prompt template in <example> that could live in a reference file.

4 / 5

Total

16

/

20

Passed

Description

78%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 clearly states both capability and explicit enumerated triggers, with good domain keywords (PRD/spec/SDD). Its main weaknesses are limited enumeration of concrete actions and some internal jargon (HCritic, Stage) that users would not naturally say.

Suggestions

Replace jargon like "HCritic" and "Stage" with user-facing terms (e.g., "automated reviewer checks", "workflow stage") in the trigger clauses.

Add one or two more concrete actions to the capability statement (e.g., "delegates reviews to subagents, applies revisions in place, and routes pass/fail outcomes") and natural variants such as "requirements document review".

DimensionReasoningScore

Specificity

"enforces automated quality gates and interactive user validation before handover" names the domain and 1-2 concrete actions, but does not enumerate a comprehensive list of specific actions (e.g., what the gates check or what revisions entail).

3 / 5

Completeness

It explicitly answers both what ("Gate pipeline for requirement deliverables — enforces automated quality gates and interactive user validation before handover") and when ("Trigger when: (1)... (2)... (3)...") with concrete enumerated trigger phrases.

5 / 5

Trigger Term Quality

"structured PRD/spec/SDD reviews" and "review-then-revision cycles" are natural terms users in this domain would say, but "HCritic" and "Stage" are internal jargon and common variations like "requirements document review" are missing.

4 / 5

Distinctiveness Conflict Risk

The requirement-deliverable gate-pipeline niche with PRD/spec/SDD triggers is mostly distinct, with only minor overlap risk against generic document-review skills.

4 / 5

Total

16

/

20

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.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/tools)

Warning

Total

13

/

16

Passed

Repository

XiaoLuoLYG/GOD

Path

jiuwenclaw/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-review/SKILL.md

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.