product-lens

Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/product-lens/SKILL.md

Quality

Content

68%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 concise, well-structured product-diagnostic skill with clear modes and integration guidance, but the checklists are prompts rather than executable guidance and workflows lack explicit validation checkpoints for the scored/batch outputs.

Suggestions

Replace or supplement the numbered question blocks in each mode with concrete, executable steps (e.g., exact files to read, commands to run, or the structure of the output document to generate).

Add explicit validation checkpoints to the workflows — e.g., after producing PRODUCT-BRIEF.md or PMF scores, a step that verifies the output against a checklist before declaring the go/no-go recommendation.

Clarify the product-capability handoff as an explicit link/reference and note where output artifacts (PRODUCT-BRIEF.md, roadmap) should be written.

Dimension	Reasoning	Score
Conciseness	Lean throughout: numbered question lists and terse mode descriptions assume Claude's competence and avoid explaining concepts Claude already knows; every section earns its place.	5 / 5
Actionability	Each mode gives a clear checklist of questions and steps, but the "code" blocks are question prompts rather than executable commands or code, and there are no concrete tool invocations, scripts, or copy-paste-ready artifacts.	3 / 5
Workflow Clarity	Modes are clearly sequenced into numbered steps, but there are no validation checkpoints or feedback loops for the diagnostic/recommendation outputs; the Founder Review and User Journey Audit modes involve batch/scored operations that lack explicit verification of the resulting PRODUCT-BRIEF.md or scores.	3 / 5
Progressive Disclosure	Well-organized into modes with clear section headers and a single one-level-deep handoff reference (product-capability); no bundle files exist to verify, and structure is appropriate for a self-contained skill, with only minor gaps in explicit reference signaling.	4 / 5
	Total	15 / 20 Passed

Description

87%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 well-crafted description that clearly states both capability and trigger context with concrete, third-person phrasing and explicit handoff boundaries. Minor gains possible by adding concrete trigger synonyms users would naturally say.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "validate the 'why' before building", "run product diagnostics", and "pressure-test product direction" — but the actions are somewhat abstract (no file types or concrete operations), leaving minor coverage gaps versus a 5.	4 / 5
Completeness	Explicitly answers both what ("validate the 'why'... run product diagnostics... pressure-test product direction") and when ("Use this skill to... before the request becomes an implementation contract") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Includes natural trigger phrases like "before building", "product diagnostics", and "before the request becomes an implementation contract"; missing a few common synonyms a user would naturally say (e.g. "product review", "prioritize features"), so just shy of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (product validation/diagnostics pre-spec) with distinct triggers, and explicitly hands off the implementation-contract work to product-capability, minimizing overlap with sibling skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/product-lens/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.