From namecast
Use this skill when the user wants to compare multiple brand name fates side-by-side to divine which is destined for success.
How this skill is triggered — by the user, by Claude, or both
Slash command
/namecast:compare-namesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compare multiple brand name candidates side-by-side to help users divine the best destiny.
Compare multiple brand name candidates side-by-side to help users divine the best destiny.
For each name being compared, evaluate:
Total: 100 points possible
## Brand Name Comparison
Comparing: {Name1} vs {Name2} vs {Name3}
### Quick Summary
| Criteria | {Name1} | {Name2} | {Name3} |
|----------|---------|---------|---------|
| Availability | X/25 | X/25 | X/25 |
| Linguistic | X/25 | X/25 | X/25 |
| Brand Fit | X/25 | X/25 | X/25 |
| Practical | X/25 | X/25 | X/25 |
| **Total** | **X/100** | **X/100** | **X/100** |
### Winner: {Name}
{1-2 sentence explanation of why this name wins}
### Detailed Breakdown
#### {Name1}: X/100
**Strengths:**
- {strength 1}
- {strength 2}
**Weaknesses:**
- {weakness 1}
- {weakness 2}
**Best for:** {scenario where this name excels}
#### {Name2}: X/100
...
#### {Name3}: X/100
...
### Recommendation
{Final recommendation with reasoning. If scores are close, explain the tradeoffs and what factors should drive the decision.}
### Next Steps
- Run full availability checks on top choice
- Test pronunciation with target audience
- Check trademark availability in detail
When scores are close (within 5 points):
When one name clearly wins:
Handling ties:
User: "Compare 'Luminary', 'Brightpath', and 'Eduvance' for an education technology company focused on corporate training"
Then provide full comparison using the framework, noting that:
npx claudepluginhub maxghenis/namecast --plugin namecastGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.