fix: resolve duplicate skill name brand-guidelines (B7, B8)

[xiaolai]

Automated audit: This PR was generated by NLPM, a natural language programming linter, running via claude-code-action. Please evaluate the diff on its merits.

Bug

Two skills in cli-tool/components/skills/business-marketing/ both declare name: brand-guidelines in their YAML frontmatter:

• brand-guidelines-anthropic/SKILL.md
• brand-guidelines-community/SKILL.md

In Claude Code's skill registry, the name field is the install key. When a user installs both skills, the second one silently overwrites the first, meaning one skill is permanently inaccessible regardless of which path it was installed from.

Fix

Rename each skill's name field to match its directory name:

File	Before	After
brand-guidelines-anthropic/SKILL.md	name: brand-guidelines	name: brand-guidelines-anthropic
brand-guidelines-community/SKILL.md	name: brand-guidelines	name: brand-guidelines-community

The skill in enterprise-communication/brand-guidelines/SKILL.md already has a unique directory and is not affected.

Why it matters

Users who install both skills from this repo get only one of them — with no error or warning. Renaming them to unique keys ensures both are independently installable and accessible by name.

The fix is minimal (two one-line frontmatter changes) and does not touch any skill content.

---

Summary by cubic

Fixes a silent install conflict by giving two brand-guidelines skills unique name keys so both can be installed and used independently.

• Area: components (cli-tool/components/)
• Change: Renamed frontmatter name to brand-guidelines-anthropic and brand-guidelines-community in their SKILL.md files
• Why: Prevents key collision where one skill overwrote the other during install
• No new components; no docs/components.json regeneration needed
• No new environment variables or secrets

^{Written for commit 3fcf87f. Summary will update on new commits.}

[vercel]

@claude is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for contributing, @xiaolai!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

1. 🤖 Automated security audit runs and posts results on this PR.
2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
3. ✅ Merge — once approved, your PR is merged to main.
4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

• Check the Security Audit comment below for any issues to fix.
• Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

[cubic-dev-ai]

No issues found across 2 files