Is naming-strategy safe to install?

SaferSkills independently audited naming-strategy (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/naming-strategy/SKILL.md · 1 file

skills/naming-strategy/SKILL.md1.2 KB · Markdown

name: naming-strategy

description: Product and feature naming, naming conventions, and linguistic considerations.

triggers: ["naming", "product naming", "feature naming"]

Naming Strategy

Product Naming Approaches

Type	Example	Pros	Cons
Descriptive	Microsoft Teams	Clear function	Generic
Invented	Spotify	Unique, ownable	Needs marketing
Metaphor	Slack	Memorable	Can confuse
Founder	Bloomberg	Personal, trustworthy	Limited scalability
Acronym	IBM	Short	Meaningless initially

Feature Naming Rules

Descriptive over clever (users need to find it, not enjoy the pun)
Consistent vocabulary (don't call it 'workspace' in one place and 'project' in another)
Verb-first for actions ('Create project' not 'Project creation')
Avoid internal jargon (what engineers call it isn't what users should see)
Test with users: 'What would you expect this to do?'

Linguistic Testing

Does it translate well? (no accidental meanings in other languages)
Is it easy to pronounce? (for word-of-mouth growth)
Is it searchable? (unique enough to rank in Google)
Is the domain available? (.com or relevant TLD)
Is the social handle available?

naming-strategy— agent skill

Is naming-strategy safe to install?

Naming Strategy

Product Naming Approaches

Feature Naming Rules

Linguistic Testing

Audit the pieces. Scan the whole. Decide.