Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

rebranding-strategy品牌重塑策略

Agent Skill

rebranding-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

12,901

周安装

527

GitHub Stars

409

下载量

4,174
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:rebranding-strategy(品牌重塑策略)
来源仓库:https://github.com/kostja94/marketing-skills
仓库路径:skills/rebranding-strategy
安装命令:
npx skills add https://github.com/kostja94/marketing-skills --skill rebranding-strategy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/kostja94/marketing-skills --skill rebranding-strategy

简介

rebranding-strategy 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于需要根据关键词或任务场景进行信息检索的营销研究场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前建议确认权限范围和维护状态,注意可能触发联网或文件读写操作。
  • 可结合原始 README 文档进一步了解具体用法和功能细节。

SKILL.md

Strategy: Rebranding

Guides rebranding execution: domain change, 301 redirects, migration checklist, and communication (social media, internal). Plan for months, not days or weeks. See domain-selection for initial domain choice; domain-architecture for domain structure decisions; multi-domain-brand-seo when multiple domains coexist.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand and product info.

Identify:

  1. Scope: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
  2. Domain change: Yes or no; old → new mapping
  3. Timeline: Target launch date; typical 4–12 weeks
  4. Channels: Website, social, product UI, directories, email

Rebranding Timeline (Typical)

PhaseDurationFocus
Audit & planWeeks 1–2Brand audit; inventory touchpoints; migration plan
PrepareWeeks 2–6New assets; redirect mapping; staging; backup
Pre-launchWeek 6–8Internal announcement; social handle check; teasers
LaunchWeek 8+Go live; 301 redirects; multi-channel announcement
Post-launch2–4 weeksMonitor search, traffic; fix 404s; iterate

Principle: Plan for months. Avoid changing domain and major structure in one migration—split into smaller migrations when possible.

301 Redirect Best Practices

PracticePurpose
1:1 mappingEach old URL → most relevant new URL; never redirect all to homepage
301 (permanent)Use 301, not 302; 302 does not fully transfer SEO equity
No chains/loopsOld URL → final destination directly; avoid A→B→C
Redirect mapping sheetDocument every old→new mapping; prevents ~80% of migration failures
Don't block in robots.txtRedirected URLs should not be disallowed

Common Mistakes

  • Redirect chains (multiple hops)
  • Redirect loops
  • Redirecting everything to homepage
  • Using 302 for permanent moves
  • Blocking redirected URLs in robots.txt

Domain Migration Checklist

Pre-Migration

  • Create SEO migration plan
  • Collect benchmarks (GA4, GSC, rankings)
  • Run site crawler; inventory all pages
  • Create redirect mapping sheet (old URL → new URL)
  • Purchase new domain; configure DNS
  • Technical SEO audit
  • Staging environment; backup
  • Check for manual penalties on both domains

Launch

  • Implement 301 redirects
  • Update Google Search Console (change of address)
  • Update sitemaps, robots.txt
  • Verify new site works; test redirects (curl, Screaming Frog)
  • Add GA4 annotation for migration date

Post-Migration

  • Monitor GSC coverage; fix "Page with Redirect" issues
  • Fix 404s immediately
  • Expect temporary ranking fluctuation (2–4 weeks)
  • Do not delete old site as fallback

Social Media Announcement

Three Phases

PhaseActions
Pre-LaunchFinalize new identity; audit social presence; secure handles across platforms; internal alignment
Build AnticipationTease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon
ExecuteAll platforms updated together; new bios, handles, visuals; compelling rebrand story (why, not what)

What to Avoid

  • Don't list steps or technical details—focus on story and benefit
  • Don't announce before all pieces are in place (mixed messaging)
  • Don't rely on one channel—multi-channel rollout
  • Don't bombard with "why we rebranded" unless it resonates

Rebrand Story

  • Anchor: Emotionally resonating narrative; why now; how it benefits customers
  • Avoid: "We changed our logo" / "We updated our website" without context

Internal Communication

  • Brief all employees before public launch
  • Explain strategic reasons; equip them to answer customer questions
  • Update email signatures, Slack, internal docs
  • Internal FAQ for common rebrand questions

Output Format

  • Timeline (phases, milestones)
  • Redirect mapping approach (template, tools)
  • Migration checklist (customized)
  • Social announcement plan (phases, channels, content angles)
  • Internal communication (briefing, FAQ)

Related Skills

  • domain-selection: Domain choice (Brand/PMD/EMD, TLD); informs new domain choice when rebranding
  • domain-architecture: Domain structure before/after rebrand
  • website-structure: New site structure after migration
  • schema-markup: Update Organization schema on new domain
  • multi-domain-brand-seo: When old and new domains coexist during transition
  • branding: Brand strategy, identity; rebranding implements the change
  • brand-protection: Sync impersonation checks when rebranding; update official domain declaration
  • gtm-strategy: Repositioning GTM; when repositioning includes rebrand

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.45%
按下载量换算1,563

Claude

30.3%
按下载量换算1,265

Cursor

19.5%
按下载量换算814

Gemini CLI

9.26%
按下载量换算387

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills