CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

generate-prd

Generate product requirements documents with optional publishing to Confluence or other wiki platforms

Quality

56%

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/generate-prd/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 thin redirect that defers all real guidance to an external playbook and rules file, so it is lean but not self-contained. It lacks the concrete steps, validation checkpoints, and in-bundle references that would make it genuinely actionable.

Suggestions

Inline the core PRD-generation workflow (key steps, output structure) into the body so the skill is actionable without resolving an external playbook.

Add a validation/checkpoint step (e.g., confirm required PRD sections are present before publishing) since publishing is an outward-facing action.

If delegation is intentional, move the referenced files into the skill bundle (references/ or scripts/) and signal them as one-level-deep references for proper progressive disclosure.

DimensionReasoningScore

Conciseness

The body is extremely lean with no padding or over-explanation of known concepts; it earns a 4 rather than 5 only because the entire value is indirection rather than self-contained earning content.

4 / 5

Actionability

It provides only high-level redirection ('Read ... and execute it exactly as written') rather than the concrete, executable PRD-generation steps, which live entirely in an external file.

2 / 5

Workflow Clarity

A rough sequence exists (read and execute the playbook, then follow the rules file) but the real workflow and any validation checkpoints are delegated out and absent from this body.

2 / 5

Progressive Disclosure

No bundle files exist, and the body is a redirect to another SKILL.md as the 'authoritative playbook'; content that belongs in this overview lives elsewhere rather than this being an overview pointing to one-level-deep supplementary references.

2 / 5

Total

10

/

20

Passed

Description

53%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 what the skill does and names a distinct niche, but it lacks an explicit 'when to use' trigger clause and misses common synonyms like the 'PRD' acronym. It is competent but not comprehensive.

Suggestions

Add a 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user asks to write or generate a PRD, product requirements document, or spec').

Include the 'PRD' acronym and synonyms like 'spec' or 'requirements doc' to improve trigger-term coverage.

Consider listing a couple more concrete actions (e.g., structuring requirements, stakeholder review) to lift specificity from 3 toward 4.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Generate product requirements documents' and 'publishing to Confluence or other wiki platforms'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Clearly states the 'what' but provides no 'Use when...' trigger guidance; per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ('product requirements documents', 'Confluence', 'wiki platforms') but omits the common 'PRD' acronym and synonyms like 'spec' or 'requirements doc' that users would naturally say.

3 / 5

Distinctiveness Conflict Risk

Targets a fairly specific niche (PRD generation plus wiki publishing) that is mostly distinct from other skills, with only minor overlap risk against general document skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

.agents/skills/generate-prd/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.