CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-software-requirements

Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.

Quality

78%

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 ./.agents/skills/common/common-software-requirements/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, knowledgeable requirements workflow with concrete paths, ID conventions, and a well-structured template behind it. Main weaknesses are verbatim rule duplication between section 1 and Anti-Patterns, dangling reference files never invoked by the workflow, and a pointer-chain reference structure.

Suggestions

Deduplicate the low-risk ticket-equivalence rule and the NFR threshold/invariant phrasing, each stated twice nearly verbatim across section 1 and Anti-Patterns; state each rule once and let the anti-pattern reference it.

Wire references/frs-checklist.md and references/standards-baseline.md into the workflow (e.g., 'run the FRS checklist before handoff') instead of leaving them dangling in the References section.

Point the References section directly at requirements-standards-baseline.md rather than routing through standards-baseline.md, which is only a link list, to keep references one level deep.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept explanations) but duplicates policy text: the low-risk ticket-equivalence rule appears at length both in section 1 ('Bounded low-risk equivalence (approved ticket with behavioral AC, owner, scope fence, approval, verification lane)') and again in Anti-Patterns ('formal PRD/SRS IDs... replaced only by approved low-risk ticket equivalence (carrying behavioral AC, owner, approval, scope fence, verification lane)'), and the NFR phrasing 'numeric thresholds... categorical verifiable invariants... never fabricate numbers' is repeated nearly verbatim. This is more than minor trimming, matching anchor 3 rather than anchor 4.

3 / 5

Actionability

Concrete, executable guidance throughout: exact paths ('docs/srs/srs-[slug].md'), stable ID schemes ('SRS-*', 'REQ-*', 'AC-*'), enumerated requirement-card and decision-brief fields, and 'Load references/srs-template.md' which supplies a copy-paste card template. Minor gaps keep it below anchor 5: the workflow never says when to run references/frs-checklist.md, and the delivery-mode routing logic is convoluted enough to require re-reading.

4 / 5

Workflow Clarity

A clear discovery-to-drafting-to-verification sequence exists with explicit checkpoints and a feedback loop ('route EVERY affected slice back to requirements/planning', 'omitting an applicable extension is an owned blocker'). It falls short of anchor 5 because references/frs-checklist.md and references/standards-baseline.md are listed but never wired into any workflow step, and the drafting steps are unnumbered bullets with implied rather than explicit ordering.

4 / 5

Progressive Disclosure

The body is a lean overview that defers detail to three clearly signaled, existing reference files, with srs-template.md properly loaded at the point of need. Minor organization gaps hold it at anchor 4: references/standards-baseline.md is itself mostly a pointer to requirements-standards-baseline.md (a two-level chain), and the two '../../product-management/product-requirements/references/requirements-modeling.md' links do not resolve within this bundle.

4 / 5

Total

15

/

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.

A strong description with an explicit what-plus-when structure and concrete trigger phrases. Trigger coverage is good but omits a few natural synonyms (spelled-out 'software requirements specification', 'requirements document', 'FRS').

DimensionReasoningScore

Specificity

"Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping" enumerates five concrete capability areas under a single verb. This lists several specific actions with minor gaps (anchor 4), but the single 'standardize' verb keeps it below anchor 5's comprehensive multi-action coverage.

4 / 5

Completeness

It clearly answers both questions: the 'what' ('Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping') and an explicit 'Use when...' clause with concrete trigger phrases. This matches anchor 5 exactly; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

"Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds" gives good natural keyword coverage a user would actually say. It falls short of anchor 5 because common synonyms like the spelled-out 'software requirements specification', 'requirements document', and 'FRS' are absent from the when-clause.

4 / 5

Distinctiveness Conflict Risk

The SRS/FRS specification niche with triggers like 'functional specification' and 'system behavior requirements' is mostly distinct. Minor overlap risk remains with closely related product-requirements and API-design skills via 'API/data contracts' and 'non-functional thresholds', so anchor 4 fits better than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-software-requirements/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.