CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/product-lens/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured across four clearly separated modes, but workflow clarity is held back by implicit validation checkpoints and a lack of explicit feedback loops.

Suggestions

Add explicit validation or feedback-loop steps to the diagnostic modes (e.g., 're-assess go/no-go after scoring', 'confirm metrics are measurable before ranking') to lift workflow clarity.

Tighten actionability by specifying the output schema for PRODUCT-BRIEF.md (e.g., required sections and the scoring cutoff that triggers a go) so guidance is closer to copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and token-efficient throughout — numbered checklists and short blocks with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Provides concrete numbered steps and specific scoring rubrics (ICE scores, 0-10 PMF signals, 'top 3 fixes'), but as an instruction-only skill the guidance remains procedural rather than copy-paste executable.

2 / 3

Workflow Clarity

Each of the four modes has a clear sequenced checklist, but validation/checkpoint structure is implicit except for Mode 1's go/no-go gate; error-recovery feedback loops are not spelled out.

2 / 3

Progressive Disclosure

A single self-contained SKILL.md with well-organized sections and one-level references to sibling skills; no nested or deep references, and structure is easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

67%

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 specific and distinct, but it omits explicit 'when to use' trigger guidance and its keywords are not phrased as natural user requests.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when deciding whether to build a feature, running a weekly product review, or turning a vague idea into a product brief.'

Reframe capability terms toward user-utterance phrasing ('decide what to build', 'product brief', 'feature prioritization') rather than abstract phrases like 'pressure-test product direction'.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'validate the why', 'run product diagnostics', 'pressure-test product direction' — covering the product-diagnosis domain specifically.

3 / 3

Completeness

Clearly answers 'what does this do' but lacks any explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Contains relevant domain terms but phrases like 'validate the why' and 'pressure-test product direction' are not natural user utterances; missing common variations like 'product brief' or 'should we build this'.

2 / 3

Distinctiveness Conflict Risk

Carves a clear niche (product diagnosis, not implementation) and explicitly hands off to product-capability, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

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.