quick-start

Quick start guide for new product development

Quality

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/product-design/skills/quick-start/SKILL.md

Quality

Content

14%

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

This skill is essentially a pointer to another file with no substantive content of its own. It fails to provide any actual quick-start guidance for product development, instead describing meta-instructions for displaying documentation that Claude already knows how to handle. The skill adds no value beyond what a simple file path reference would provide.

Suggestions

Include the actual quick-start content directly in this skill file, or at minimum provide a meaningful summary of the product development process

Remove the meta-instructions about how Claude should read and display files - Claude already knows how to do this

Add concrete, actionable steps for new product development with specific examples or templates

If referencing external files is necessary, provide context about what each file contains and when to use it

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes unnecessary meta-instructions about how Claude should display documentation, which Claude already knows how to do. The actual quick-start content is deferred to another file.	2 / 3
Actionability	The skill provides no concrete guidance for product development - it only describes how to display documentation from another file. There are no executable examples, specific steps, or actual quick-start content.	1 / 3
Workflow Clarity	The numbered steps describe how to display a file, not how to do product development. The actual workflow for the skill's stated purpose (new product development) is completely absent.	1 / 3
Progressive Disclosure	The skill defers all actual content to an external file without providing any overview or summary of what that content contains. This is an empty shell that provides no value on its own.	1 / 3
	Total	5 / 12 Passed

Description

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is critically weak across all dimensions. It reads more like a document title than a functional skill description, providing no concrete actions, no trigger guidance, and no distinguishing characteristics that would help Claude select it appropriately from a skill library.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Creates product requirement documents, defines MVP features, outlines development roadmaps, generates user story templates').

Include an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user mentions PRD, product specs, MVP planning, feature prioritization, or starting a new product').

Narrow the scope to a specific aspect of product development to reduce conflict risk (e.g., focus on PRD creation, or roadmap planning, or user research synthesis).

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('quick start guide') without listing any concrete actions. It doesn't specify what actions Claude would perform - no verbs describing capabilities.	1 / 3
Completeness	Fails to answer both 'what does this do' and 'when should Claude use it'. There's no 'Use when...' clause and the 'what' is extremely vague - it's unclear what specific tasks this skill performs.	1 / 3
Trigger Term Quality	Contains generic terms ('quick start', 'new product development') that are overly broad and not natural trigger phrases users would say when needing specific help. Missing actionable keywords.	1 / 3
Distinctiveness Conflict Risk	Extremely generic description that could conflict with any skill related to products, development, guides, or onboarding. 'Product development' is a broad domain with no distinguishing specifics.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: jpoutrin/product-forge
Commit: 0ebe7ae

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