CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-name

Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience. Use when naming a new product, rebranding, or exploring product name ideas.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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-structured, self-contained prompt skill whose instructions are specific and executable, with clean sectioning appropriate to its size. The only refinements are minor: remove the duplicated intro line and optionally add one example output.

Suggestions

Delete the opening paragraph that restates the description almost verbatim; the H1 plus When to Use section already orient the reader.

Add a brief worked example (one sample name with its rationale fields filled in) to make the expected output format unambiguous.

Merge the "Prioritize names that are..." criteria into the per-name rubric where they already appear (distinctive, brand-aligned) to remove overlap.

DimensionReasoningScore

Conciseness

The prompt template is lean and assumes Claude's competence, with only minor trimmable redundancy: the opening paragraph repeats the frontmatter description nearly verbatim, and the "Prioritize names that are..." list overlaps the per-name rubric (e.g., distinctive, aligned with brand tone). Not a 3 because there is no concept-explanation padding and every section serves a purpose.

4 / 5

Actionability

The guidance is concrete and copy-paste ready: a role, a $ARGUMENTS input slot, an exact deliverable (five names each with Name, Rationale, Brand Fit, Memorability, and Domain & Trademark Considerations), plus selection criteria and context tips. Not a 5 because no worked example of expected output is included, leaving the common case shown rather than exemplified.

4 / 5

Workflow Clarity

This is a simple single-task skill (under 50 lines): one unambiguous action — run the fully-specified prompt with the user's context. Per the rubric's simple-skill exception, workflow clarity scores 5 since the single action is unambiguous, and no destructive or batch operations exist to require validation checkpoints.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references (references/, scripts/, assets/ are absent and none are referenced), and the body is organized into well-labeled sections (When to Use, Prompt, Tips for Best Results). Per the rubric's simple-skill guidance, this earns a 5.

5 / 5

Total

18

/

20

Passed

Description

78%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 description in third-person voice with an explicit what-and-when structure and natural trigger phrases. The main gaps are single-action coverage and a few missing natural synonyms that live only in the body.

Suggestions

Fold additional concrete actions into the description (e.g., vet domain and trademark availability, or check candidate names against brand guidelines) to lift specificity beyond one action.

Add missing natural trigger variations to the description itself, such as "what to call" or "brand name ideas", rather than keeping them only in the body's trigger list.

DimensionReasoningScore

Specificity

"Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience" names the domain and essentially one concrete action (brainstorming 5 names) with its criteria — matching the '1-2 concrete actions, but not comprehensive' anchor. Not a 4 because it does not list several distinct actions (e.g., checking domain/trademark availability or comparing names against brand guidelines, which appear only in the body).

3 / 5

Completeness

Explicitly answers both questions: the what ("Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience") and the when ("Use when naming a new product, rebranding, or exploring product name ideas") with concrete trigger phrases. Not a 4 because the 'when' clause is already explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

"Use when naming a new product, rebranding, or exploring product name ideas" provides natural phrases users would actually say. Not a 5 because common variations like "what to call", "brand name", or "come up with a name" are missing from the description itself (they appear only in the body's trigger list).

4 / 5

Distinctiveness Conflict Risk

Product naming with triggers like "naming a new product" and "rebranding" is a clear niche with distinct triggers. Not a 5 because "rebranding" and general name-idea requests create minor overlap risk with broader branding/brainstorming skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

phuryn/pm-skills

Path

pm-marketing-growth/skills/product-name/SKILL.md

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.