CtrlK
BlogDocsLog inGet started
Tessl Logo

product-capability

Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is product-capability in affaan-m/ECC

SKILL.md
Quality
Evals
Security

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 content is a well-structured, actionable process skill with a clear sequenced workflow and a concrete output template. It is efficient but carries a few editorial sentences, and validation is implicit rather than explicit.

Suggestions

Trim editorial sentences (e.g., "This skill turns product intent into explicit engineering constraints", "If this statement is weak, the implementation will drift") to tighten conciseness toward a 5.

Make the quality/validation checkpoint explicit in the workflow (e.g., a step that verifies unresolved questions are marked and conflicts with repo constraints are surfaced) to strengthen workflow clarity.

Tighten abstract step bodies (e.g., "Compress the ask into one precise statement") with a one-line concrete template or rubric the output must satisfy.

DimensionReasoningScore

Conciseness

The body is efficient and free of basic-concept padding, but a few editorial sentences ("This skill turns product intent into explicit engineering constraints", "These are the things that often live only in senior-engineer memory") could be trimmed.

4 / 5

Actionability

Provides concrete structured guidance—an explicit four-step workflow with enumerated constraint fields and a copy-paste-ready output format template—though step bodies like "Compress the ask into one precise statement" remain somewhat abstract.

4 / 5

Workflow Clarity

The workflow is clearly sequenced across four numbered phases with the HANDOFF step acting as a checkpoint; validation is implicit rather than explicit, which is acceptable for a non-destructive planning skill.

4 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep references (template path and downstream ECC lanes) and no nesting; the full output template is inlined rather than split, which is appropriate for a process skill but keeps it just shy of a 5.

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.

The description is strong: it states concrete capabilities, gives an explicit "Use when" trigger, and occupies a distinct niche with low conflict risk. Trigger-term coverage is good but not exhaustive, slightly capping the score there.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"Translate PRD intent, roadmap asks, or product discussions" and "exposes constraints, invariants, interfaces, and unresolved decisions"—giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both "what" (translate product intent into an implementation-ready capability plan exposing constraints, invariants, interfaces, unresolved decisions) and "when" ("Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose").

5 / 5

Trigger Term Quality

Includes natural domain phrases a user would say ("PRD intent", "roadmap asks", "product discussions", "PRD-to-SRS lane") with good coverage, but a few synonym variations are absent and no file extensions apply.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche ("ECC-native PRD-to-SRS lane", "before multi-service work starts") with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.