product-multi-role-analysis

Analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings, or related links; save separate intermediate analyses from seven roles (user, investor, product manager, market operator, brand operator, competitor, partner), then synthesize a sourced illustrated Markdown report. Use when the user asks for product analysis, product teardown, multi-role evaluation, investment/product/marketing/brand/competitive/partnership perspectives, or a report with assumptions, boundaries, verification signals, and scenario updates.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A well-organized, actionable skill body with a clear multi-step workflow, explicit validation, and appropriately split references. Minor tightening and resolution of the inlined-vs-referenced role guidance would lift it further.

Suggestions

Replace the '/path/to/product-multi-role-analysis/' placeholder in the script command with the actual relative path so the command is copy-paste runnable.

Defer the full role-specific question lists to references/role-checklist.md and link to it from the body, keeping only a one-line role summary inline to remove duplication.

Add a short explicit error-retry loop (e.g., on script failure or missing sources) to make the workflow's validation feedback loop fully concrete.

Dimension	Reasoning	Score
Conciseness	Largely lean and efficient — lists, short directives, and no padding or basic-concept explanations; the role-specific focus and common-questions sections repeat a parallel structure that could be tightened slightly.	4 / 5
Actionability	Provides concrete executable guidance: a real script invocation with arguments, named file paths (sources/source-notes.md, 01-user.md), and an SVG reference example; the '/path/to/' placeholder in the script command is a minor gap.	4 / 5
Workflow Clarity	A clear 9-step sequence with an explicit validation checkpoint in step 9 ('Verify that every strong conclusion is supported... or is clearly labeled as inference') plus evidence-rule reinforcement; lacks an explicit error-retry loop, keeping it just below 5.	4 / 5
Progressive Disclosure	Well-structured overview with one-level-deep references to real bundle files (scripts/create_analysis_workspace.py, references/role-checklist.md) and an assets/ folder; minor gap is that role questions are inlined in the body rather than deferred to role-checklist.md, producing light duplication.	4 / 5
	Total	16 / 20 Passed

Description

88%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, specific description with explicit 'Use when' trigger guidance and comprehensive concrete actions. It clearly communicates both capability and invocation context with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across input types ('analyze a product from documentation, websites, PDFs, articles, release notes, pricing pages, app listings, reviews, filings'), saving seven role-specific intermediate analyses, and synthesizing a sourced Markdown report — comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (analyze inputs, save seven role analyses, synthesize illustrated report) and when via a concrete 'Use when the user asks for product analysis, product teardown...' clause with named trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger phrases ('product analysis', 'product teardown', 'multi-role evaluation', 'investment/product/marketing/brand/competitive/partnership perspectives') with good synonym coverage across lenses; a few common user phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	The seven-role framing and sourced-illustrated-report output form a clear niche distinct from generic research skills; minor overlap risk with broad analysis skills keeps it just below a 5.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: digoal/blog
Path: skills/product-multi-role-analysis/SKILL.md
Commit: 3b9c83d

Reviewed: 3 days 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.