Name: product-skills
Rating: 72 (1 reviews)
Author: alirezarezvani

product-skills

Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

Quality

90%

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

The canonical home for this skill is product-skills in alirezarezvani/claude-skills

Quality

Content

88%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 well-engineered orchestrator body: concrete executable commands, a validation-gated multi-step loop, and clear reference navigation. Minor conciseness and structure gains are available by trimming canon citations and externalizing the forcing-question library.

Suggestions

Trim the canon citations in the forcing-question library to author+title only, or move the full library into a reference file, to recover token budget.

Consider moving the forcing-question library and/or hard rules into a reference doc so SKILL.md stays a tighter overview pointing to detail.

Verify the referenced bundle paths (scripts/*.py, assets/sample_discovery_log.json, references/*.md) actually exist in the bundle, since several referenced files were not present locally.

Dimension	Reasoning	Score
Conciseness	Mostly lean and information-dense, but includes light over-explanation ('Modern discovery is a weekly habit, not a project phase (Torres)') and full canon citations in the forcing-question library that add tokens beyond what Claude strictly needs.	4 / 5
Actionability	Fully executable guidance — copy-paste commands with flags (`product_goal_router.py --text ... --output json`) and explicit exit-code semantics (0/2/3/5) cover routing, cadence, linting, and harness compilation.	5 / 5
Workflow Clarity	The discovery loop is a clearly sequenced 5-step process (Observe→Choose→Act→Verify→Record/Repeat-or-stop) with explicit machine-gated validation (`ost_linter.py` exit 2 = NEEDS-REWORK, cadence tracker refuses <2 interviews) and defined stop/escalation states.	5 / 5
Progressive Disclosure	Good structure with a clear one-level-deep References section and well-signaled markdown links, but the forcing-question library and hard-rules sections are fairly long inline content that could be split out for tighter navigation.	4 / 5
	Total	18 / 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.

A strong, third-person description that concretely states capabilities, gives explicit natural trigger phrases, and explicitly distinguishes itself from adjacent skills. The only gap is moderate synonym coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Forks context to route to one sub-skill via a deterministic signal router and returns a digest', 'drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates)', and a 'full goal→plan→execute→verify→close run' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what (routing + looping + discovery loop + harness runs) and when via an explicit 'Use when coordinating...' clause plus concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides five natural trigger phrases ('help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'), but omits common synonyms surfaced in the sub-skill list (PRD, OKRs, teardown) and there are no file extensions, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	Explicitly carves a clear niche — 'Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness' — minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning
referenced_paths_exist	Referenced path issues: 15 missing	Warning

	Total	13 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/product-skills/SKILL.md
Commit: 19392f7

Reviewed: ~4 hours 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.