Internal Comms Anthropic
sickn33/agentic-awesome-skills
Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.
Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references.
MITAuto-check passed
Install Rename Skill
$ npx skills add yamcodes/arkenv --skill rename-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yamcodes/arkenv rename-skill --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/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rename-skill .claude/skills/rename-skill && 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 "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .claude/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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/yamcodes/arkenv/tree/v1/skills/rename-skillType 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 yamcodes/arkenv --skill rename-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yamcodes/arkenv rename-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rename-skill .agents/skills/rename-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .agents/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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 yamcodes/arkenv --skill rename-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yamcodes/arkenv rename-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rename-skill .cursor/skills/rename-skill && 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 "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .cursor/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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/yamcodes/arkenv.git --path skills/rename-skill--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 yamcodes/arkenv --skill rename-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yamcodes/arkenv rename-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rename-skill .gemini/skills/rename-skill && 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 "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .gemini/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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 yamcodes/arkenv rename-skillInstalls 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 yamcodes/arkenv --skill rename-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rename-skill .github/skills/rename-skill && 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 "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .github/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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 yamcodes/arkenv --skill rename-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yamcodes/arkenv rename-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yamcodes/arkenv.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rename-skill .opencode/skills/rename-skill && 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 "rename-skill" agent skill from https://github.com/yamcodes/arkenv/tree/v1/skills/rename-skill into .opencode/skills/rename-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rename-skill", 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
rename-skill- GitHub stars
- 145
- Token cost
- ~694 tokens
- SKILL.md length
- 292 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references.
- Works in 5 steps: Gather Information → Rename the Directory → Update Frontmatter and Attribution → …
- The user requests to rename a skill
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Change a skills identifier
What it does
Rename Skill is an agent skill from yamcodes/arkenv. Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references. Use when the user requests to rename a skill, change a skill's identifier, or restructure a skill's folder.
Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.
When your agent uses it
- The user requests to rename a skill
- Change a skills identifier
- Restructure a skills folder
Example prompts
- “s identifier, or restructure a skill”
- “/rename-skill”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 74b3732. 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 (its code samples are bash and yaml).
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
Rename Skill loads about 694 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 292 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 yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 292 words, ~694 tokens.
Download SKILL.mdSave it as
.claude/skills/rename-skill/SKILL.md (or your agent's skills folder).- name
- rename-skill
- description
- Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references. Use when the user requests to rename a skill, change a skill's identifier, or restructure a skill's folder.
- metadata.internal
- true
Rename Skill
This skill guides you through safely and comprehensively renaming an existing skill (either internal or external) in the workspace.
Workflow
1. Gather Information
- Identify the skill to rename (e.g.,
old-name). - Determine the target name (e.g.,
new-name). - Locate the skill directory. Typically, it will be under:
skills/old-name(internal skills).agents/skills/old-name(external/cache skills)
2. Rename the Directory
Rename the skill directory on the filesystem:
# For internal skills:
mv skills/<old-name> skills/<new-name>
# For external skills:
mv .agents/skills/<old-name> .agents/skills/<new-name>3. Update Frontmatter and Attribution
Open SKILL.md in the newly renamed directory and update the name field in the frontmatter:
---
name: <new-name>
...
---Ensure you handle attribution and metadata correctly:
- Preserve Attribution: Do NOT delete existing attribution metadata in the frontmatter (e.g.,
original_author,origin). These track the provenance of the skill. - Update Maintainer (Optional): If you are taking over maintenance or updating the skill extensively, you can update or add the
authorfield to yourself/your team, but keeporiginal_authorintact. - Update Internal Flag: Ensure
metadata.internal: trueis set if it is an internal skill. - Update Credits Section: If the bottom of
SKILL.mdcontains a## Creditsor## Acknowledgementssection, preserve it and update any local folder/file links to reflect the renamed directory.
4. Search and Update References
Scan the codebase and docs for any references to the old skill name and update them to the new skill name. Look specifically for:
- Markdown links to the skill or its files (e.g.,
[link](file:///.../skills/old-name/SKILL.md)). - References to the old name in descriptions or lists of available skills.
- Importing/requiring any scripts inside the skill.
You can find references using grep or the grep_search tool:
# Search for old name references in skills and docs
grep -rn "old-name" skills/ .agents/skills/ docs/ README.md5. Verify the Rename
Ensure the renamed skill is healthy:
- Check that
skills/<new-name>/SKILL.mdexists and contains valid markdown and YAML frontmatter. - If there are tests associated with the skill, verify they still run successfully.
- Check that all updated links/references point to valid files.
© yamcodes, 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/rename-skill of yamcodes/arkenv.
Open the folder on GitHubat commit 74b3732
Compare with similar skills
Rename Skill 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 |
|---|---|---|---|---|---|---|
| Rename Skill this skillyamcodes/arkenv | 145 | — | ~694 | Automated safety check: Pass | MIT | |
| Internal Comms Anthropicsickn33/agentic-awesome-skills | 47k | 1 repos | ~702 | Automated safety check: Pass | Apache-2.0 | |
| Internal Commsalirezarezvani/claude-skills | 28k | — | ~3.4k | Automated safety check: Pass | MIT | |
| Openclaw Updateopenclaw/openclaw | 392k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Internal Communicationsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Update Docsvercel/next.js | 143k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Internal Comms
alirezarezvani/claude-skills
A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…
Openclaw Update
openclaw/openclaw
Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery.
Internal Communication
sickn33/agentic-awesome-skills
Internal communication log: title, type, date, department, host and attendees, agenda, action items, follow-up date, meeting link and delivery status.
- Official
Update Docs
vercel/next.js
This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature"…
- Official
Internal Communications Writer
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
More from yamcodes/arkenv
All 20 skills in this repoHallmark
yamcodes/arkenv
Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.
Bulletproof React
yamcodes/arkenv
Bulletproof React architecture patterns for scalable, maintainable applications.
Arkenv
yamcodes/arkenv
Answer questions about ArkEnv and help implement environment variable validation.
Code Review
yamcodes/arkenv
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.
Forward Port
yamcodes/arkenv
Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.
Groom Issue
yamcodes/arkenv
Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…
Questions about Rename Skill
What does Rename Skill do?
Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references. Rename Skill is an agent skill from yamcodes/arkenv. Rename an existing agent skill (internal or external), updating its directory name, frontmatter name, and codebase-wide references.
When should I use Rename Skill?
Rename Skill fits situations like: the user requests to rename a skill; change a skills identifier; restructure a skills folder.
How do I install Rename Skill in Claude Code?
Run `npx skills add yamcodes/arkenv --skill rename-skill -a claude-code`. Or copy the skill folder (skills/rename-skill in yamcodes/arkenv) into .claude/skills/rename-skill in your project. Claude Code loads it when a task matches its description.
How do I install Rename Skill in Codex?
Run `npx skills add yamcodes/arkenv --skill rename-skill -a codex`. Or copy the skill folder (skills/rename-skill in yamcodes/arkenv) into .agents/skills/rename-skill in your project. Codex loads it when a task matches its description.
Can I use Rename Skill 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 yamcodes/arkenv --skill rename-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rename-skill, .gemini/skills/rename-skill, .github/skills/rename-skill and .opencode/skills/rename-skill in your project.
What does Rename Skill need to run?
SKILL.md names no scripts, command-line tools or credentials: Rename Skill is instructions for the agent only.
Does Rename Skill 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 Rename Skill 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 Rename Skill use?
Rename Skill 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 Rename Skill use?
About 694 tokens (SKILL.md is roughly 2.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 Rename Skill?
Skills that share tags, products or a category with Rename Skill: Internal Comms Anthropic (sickn33/agentic-awesome-skills, 47k stars), Internal Comms (alirezarezvani/claude-skills, 28k stars), Openclaw Update (openclaw/openclaw, 392k stars) and Internal Communication (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rename Skill?
yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.
Source: yamcodes/arkenv on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.