Skills product-naming
📦

product-naming

Content revision r1 Safe ⚙️ External commands

Create Product Names With Strategy

Product naming often becomes a rushed list of options without clear strategy. This skill guides Claude, Codex, and Claude Code through discovery, naming routes, validation, and final selection.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "product-naming" from https://skillstore.io/skills/yunshu0909-product-naming.md and its manifest at https://skillstore.io/api/skills/yunshu0909-product-naming/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yunshu0909-product-naming.md Signed manifest GET /api/skills/yunshu0909-product-naming/manifest Signed lockfile GET /api/skills/yunshu0909-product-naming/lockfile

Test it

Using "product-naming". Name an async standup tool for remote developer teams.

Expected outcome:

The skill first asks about users, tone, boundaries, and constraints. It then presents routes such as action words, rhythm metaphors, and coined names.

Using "product-naming". We chose the rhythm metaphor route for a planning product.

Expected outcome:

The skill develops three to five focused candidates, explains each name, and keeps the exploration within the selected direction.

Using "product-naming". Compare our finalist name with products in the same category.

Expected outcome:

The skill summarizes competitor naming patterns, checks likely collision risk, and recommends a final naming strategy.

Security Audit

Safe
v4 • 7/8/2026 Open versioned report

The external command findings are false positives caused by Markdown fenced examples, not executable shell or Ruby backtick usage. The entropy finding is also a false positive because SKILL.md is readable product-naming guidance with no obfuscation or prompt injection evidence.

1
Files scanned
174
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (7)
SKILL.md:47-55 SKILL.md:55-68 SKILL.md:68-84 SKILL.md:84-121 SKILL.md:121-127 SKILL.md:127-135 SKILL.md:135-144
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/yunshu0909-product-naming/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yunshu0909-product-naming/security.svg)](https://skillstore.io/skills/yunshu0909-product-naming?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yunshu0909-product-naming?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yunshu0909-product-naming/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yunshu0909-product-naming.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

yunshu0909. (2026). product-naming security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yunshu0909-product-naming/audits/4

BibTeX citation

@techreport{yunshu0909-yunshu0909-product-naming-2026, author = {yunshu0909}, title = {product-naming security audit report (audit version 4)}, institution = {Skillstore}, year = {2026}, number = {4}, url = {https://skillstore.io/skills/yunshu0909-product-naming/audits/4}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "product-naming security audit report (audit version 4)" version: "unspecified" type: report authors: - name: "yunshu0909" date-released: "2026-07-08" url: "https://skillstore.io/skills/yunshu0909-product-naming/audits/4" identifiers: - type: other value: "skillstore:yunshu0909-product-naming:audit:4" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
91
Spec Compliance

What You Can Build

Name a New Startup Product

Move from a rough product idea to naming routes, candidates, and a final naming strategy.

Rename an Internal Tool

Clarify users, boundaries, and tone before choosing a clearer project or module name.

Validate Shortlisted Names

Compare finalist names against competitor patterns and decide whether a slogan or local name is needed.

Try These Prompts

Start a Naming Session 
Help me name a new product. Start by asking about users, positioning, boundaries, tone, language, length, and words to avoid.
Extract Naming Constraints 
Review this product brief and extract naming constraints. Identify strategic tensions, priorities, and missing questions before suggesting any names.
Create Naming Routes 
Based on our confirmed constraints, propose two to four naming routes. Include sample names, advantages, drawbacks, and a recommendation.
Validate Finalists 
Validate these finalist names against competitor naming patterns. Recommend one final name, slogan needs, and the decision rationale.

Best Practices

  • Share the target users, main use case, brand tone, and words to avoid before asking for names.
  • Choose a naming route before requesting detailed candidate names.
  • Validate finalist names with competitor research and legal review before launch.

Avoid

  • Do not ask for a long name list before clarifying product positioning.
  • Do not choose a name only because it sounds pleasant.
  • Do not skip competitor, trademark, domain, and localization checks.

Frequently Asked Questions

Does this skill create names immediately?
No. It first clarifies the product, audience, constraints, and brand tone before suggesting names.
Can it help with Chinese and English names?
Yes. It can discuss language strategy and whether one name, two names, or a slogan is appropriate.
Does it check trademarks?
No. It can flag likely collision concerns, but trademark review needs a qualified legal process.
How many naming routes does it provide?
It usually provides two to four routes so users can choose a strategic direction before detailed naming.
Can it rename existing products?
Yes. Provide current positioning, user feedback, and reasons the current name no longer works.
What tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

yunshu0909

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/yunshu0909/yunshu_skillshub/tree/master/product-naming

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/22/2026

Usage

9 downloads · 121 views

File structure

📄 SKILL.md