Petshare Setup
portons/codex-pet-share
A skill your agent uses when an agent needs to fork, rebrand, deploy, adapt, or rebuild a Codex Pet Share style app with animated pet uploads, generated previews, gallery downloads, provider…
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement.
Install Rebranding Strategy
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kostja94/marketing-skills rebranding-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/strategies/brand/rebranding .claude/skills/rebranding-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .claude/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebrandingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kostja94/marketing-skills rebranding-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/strategies/brand/rebranding .agents/skills/rebranding-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .agents/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kostja94/marketing-skills rebranding-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/strategies/brand/rebranding .cursor/skills/rebranding-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .cursor/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kostja94/marketing-skills.git --path skills/strategies/brand/rebranding--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kostja94/marketing-skills rebranding-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/strategies/brand/rebranding .gemini/skills/rebranding-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .gemini/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kostja94/marketing-skills rebranding-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/strategies/brand/rebranding .github/skills/rebranding-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .github/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kostja94/marketing-skills --skill rebranding-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kostja94/marketing-skills rebranding-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kostja94/marketing-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/strategies/brand/rebranding .opencode/skills/rebranding-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "rebranding-strategy" agent skill from https://github.com/kostja94/marketing-skills/tree/main/skills/strategies/brand/rebranding into .opencode/skills/rebranding-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rebranding-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
rebranding-strategy- GitHub stars
- 1k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 640 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement.
- Works in 4 steps: Scope: Full rebrand (name, domain,… → Domain change: Yes or no; old → new… → Timeline: Target launch date; typical… → …
- Execute a rebrand—domain change
- SKILL.md covers Initial Assessment, Rebranding Timeline (Typical), 301 Redirect Best Practices and Domain Migration Checklist, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rebranding Strategy is an agent skill from kostja94/marketing-skills. When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Brand strategy and identity. The repository describes itself as: Agent Skills for Marketing — SEO, Social, Influencer & More. 160+ open-source skills for SEO, content, 40+ page types, paid ads, channels, and strategies. Add project context… The licence is MIT.
When your agent uses it
- Execute a rebrand—domain change
- The user mentions rebranding
- Domain migration
- Change domain name
Example prompts
- “rebranding,”
- “rebrand,”
- “domain change,”
- “/rebranding-strategy”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Scope: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
- Domain change: Yes or no; old → new mapping
- Timeline: Target launch date; typical 4–12 weeks
- Channels: Website, social, product UI, directories, email
What it can do on your machine
Read from SKILL.md and the folder at commit 8dd89c5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Rebranding Strategy loads about 1.4k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 640 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from kostja94/marketing-skills at commit 8dd89c5, republished under its MIT licence (© kostja94). 640 words, ~1,438 tokens.
Download SKILL.mdSave it as
.claude/skills/rebranding-strategy/SKILL.md (or your agent's skills folder).- name
- rebranding-strategy
- description
- When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
- metadata.version
- 1.0.1
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
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
- Scope: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
- Domain change: Yes or no; old → new mapping
- Timeline: Target launch date; typical 4–12 weeks
- Channels: Website, social, product UI, directories, email
Rebranding Timeline (Typical)
| Phase | Duration | Focus |
|---|---|---|
| Audit & plan | Weeks 1–2 | Brand audit; inventory touchpoints; migration plan |
| Prepare | Weeks 2–6 | New assets; redirect mapping; staging; backup |
| Pre-launch | Week 6–8 | Internal announcement; social handle check; teasers |
| Launch | Week 8+ | Go live; 301 redirects; multi-channel announcement |
| Post-launch | 2–4 weeks | Monitor 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
| Practice | Purpose |
|---|---|
| 1:1 mapping | Each 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/loops | Old URL → final destination directly; avoid A→B→C |
| Redirect mapping sheet | Document every old→new mapping; prevents ~80% of migration failures |
| Don't block in robots.txt | Redirected 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
Show full SKILL.md (253 more words)Show less
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
| Phase | Actions |
|---|---|
| Pre-Launch | Finalize new identity; audit social presence; secure handles across platforms; internal alignment |
| Build Anticipation | Tease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon |
| Execute | All 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
© kostja94, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/strategies/brand/rebranding of kostja94/marketing-skills.
Open the folder on GitHubat commit 8dd89c5
Compare with similar skills
Rebranding Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Rebranding Strategy this skillkostja94/marketing-skills | 1k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Petshare Setupportons/codex-pet-share | 136 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Brand Architecturearnabbagxd/Brand-building-skills | 729 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Linkedin Employee Advocacysergebulaev/linkedin-skills | 4.4k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Brand Contextarnabbagxd/Brand-building-skills | 729 | — | ~842 | Automated safety check: Pass | MIT |
Similar skills
Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Brand Architecture
arnabbagxd/Brand-building-skills
Define how multiple brands, sub-brands, and product lines relate to each other under one organization.
Linkedin Employee Advocacy
sergebulaev/linkedin-skills
Stand up and run a LinkedIn employee advocacy program for a marketing or sales team.
Brand Context
arnabbagxd/Brand-building-skills
Foundation skill that captures and stores core brand context — identity, audience, positioning, values, and voice.
Replica Diff
Jakeschincariol/replica-skill
Compares an app clone against the original: a feature parity score from the feature matrix (weighted by must, should, could) with the missing list in build order, plus a screenshot layout diff that…
More from kostja94/marketing-skills
All 102 skills in this repoGrokipedia Recommendations
kostja94/marketing-skills
When the user wants to add recommendations, links, or content to Grokipedia.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
Analytics Tracking
kostja94/marketing-skills
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions).
Brand Visual Generator
kostja94/marketing-skills
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics).
Canonical Tag
kostja94/marketing-skills
When the user wants to configure canonical URLs, fix duplicate content, or consolidate URL signals.
Content Strategy
kostja94/marketing-skills
When the user wants to plan content for SEO, create content calendar, or build topic clusters.
Related
Categories
Questions about Rebranding Strategy
What does Rebranding Strategy do?
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Rebranding Strategy is an agent skill from kostja94/marketing-skills. When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement.
When should I use Rebranding Strategy?
Rebranding Strategy fits situations like: execute a rebrand—domain change; the user mentions rebranding; domain migration; change domain name.
How do I install Rebranding Strategy in Claude Code?
Run `npx skills add kostja94/marketing-skills --skill rebranding-strategy -a claude-code`. Or copy the skill folder (skills/strategies/brand/rebranding in kostja94/marketing-skills) into .claude/skills/rebranding-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Rebranding Strategy in Codex?
Run `npx skills add kostja94/marketing-skills --skill rebranding-strategy -a codex`. Or copy the skill folder (skills/strategies/brand/rebranding in kostja94/marketing-skills) into .agents/skills/rebranding-strategy in your project. Codex loads it when a task matches its description.
Can I use Rebranding Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kostja94/marketing-skills --skill rebranding-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rebranding-strategy, .gemini/skills/rebranding-strategy, .github/skills/rebranding-strategy and .opencode/skills/rebranding-strategy in your project.
What does Rebranding Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Rebranding Strategy is instructions for the agent only.
Does Rebranding Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Rebranding Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Rebranding Strategy use?
Rebranding Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rebranding Strategy use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Rebranding Strategy?
Skills that share tags, products or a category with Rebranding Strategy: Petshare Setup (portons/codex-pet-share, 136 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars), Brand Architecture (arnabbagxd/Brand-building-skills, 729 stars) and Linkedin Employee Advocacy (sergebulaev/linkedin-skills, 4.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rebranding Strategy?
kostja94 (a GitHub user) maintains it in kostja94/marketing-skills, which has 1,025 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 6, 2026.
Source: kostja94/marketing-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.