internalize-skill
/internalize-skill
Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal. Use this skill whenever a new skill is installed and needs to be promoted, renamed, or attributed as a project-internal skill.
- Author
- yamcodes ↗
- Repository
- arkenv ↗
- Licence
- MIT
- Last repository change
- 23.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal. Use this skill whenever a new skill is installed and needs to be promoted, renamed, or attributed as a project-internal skill.
Triggers from the description
Original author description
Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal. Use this skill whenever a new skill is installed and needs to be promoted, renamed, or attributed as a project-internal skill.
How it works
- Workflow
- Implementation details
- Safety checks
SKILL.md preview
---
name: internalize-skill
description: "Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal. Use this skill whenever a new skill is installed and needs to be promoted, renamed, or attributed as a project-internal skill."
metadata:
internal: true
---
# Internalize skill
This skill automates the process of moving externally installed skills to the project's internal `skills/` directory, tagging them as internal, and optionally renaming and attributing them.
## Workflow
1. **Identify Target Skills & Options:**
- Check the `.agents/skills/` (or `.agent/skills/`) directory for subdirectories.
- If the user explicitly named a skill (e.g., "internalize the research skill"), focus only on that one.
- If the user was vague, clarify which skill to target.
- **Ask the user** if they would like to:
- Rename the skill (e.g., change `creating-changesets` to `arkenv-changesets`).
- Add attribution details (e.g., `original_author`, original `origin` repository url).
2. **Move/Rename to Internal:**
- Move the identified skill directory to `skills/<new-name>` (where `<new-name>` defaults to the original name if no rename is requested).
3. **Update Frontmatter & Metadata:**
- Update the `name` field in the `SKILL.md` frontmatter to `<new-name>`.
- Update the `metadata` block to include `internal: true`.
- If attribution details were specified, add:
- `original_author`: The original author's name.
- `origin`: The URL or GitHub repository of the original skill.
- `author`: The current maintainer or team name.
4. **Append Markdown Credits (Optional):**
- If the skill was renamed or customized, append a `## Credits` or `## Acknowledgements` section at the bottom of the skill's `SKILL.md` file linking back to the original source.
## Implementation details
The skill should rely on standard bash commands for efficiency and portability.
### Moving & renaming skills
```bash
# If keeping the same name:
mv .agents/skills/<old-name> skills/
# If renaming:
mv .agents/skills/<old-name> skills/<new-name>
```
### Updating metadata
Use code edits or `awk` to update `SKILL.md` frontmatter. The logic should:
- Update `name: <new-name>` at the top.
- Insert or merge the `metadata` block to ensure `internal: true`, plus any specified attribution fields.
Example of expected final frontmatter structure:
```yaml
---
name: arkenv-changesets
description: Creates changesets for semantic versioning.
metadata:
author: Yam Borodetsky
original_author: Ollie Shop
origin: github.com/ollieshop/creating-changesets
version: 1.0.0
internal: true
---
```
## Safety checks
- Ensure the root `skills/` directory exists before moving.
- Verify `SKILL.md` exists in the target directory before attempting to edit it.
- Do not overwrite existing internal skills under `skills/` unless explicitly confirmed by the user.
Versions
The database has no other skills named internalize-skill.
Database snapshot: 13.11.2026 · package version 5252aac25ae2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100skills-atlas
Find, compare, read, install, update and uninstall public Agent Skills (SKILL.md) from a catalog of about 75,000, with the skills-atlas CLI. Use when the user wants a skill for some task ("is there a skill for…", "find me a skill to…"), asks what skills are installed or… - 100vibe-skills-manager
Use when installed skills are messy across IDEs, the user is unsure which skills exist globally vs project-level, needs to sync, clean, or recommend installed skills, is setting up a new worktree, or mentions "/vibe-skills-manager". Do not use for authoring or reviewing `skills/vibe-*` content. - 100find-skills
List installed skills, search the skill registry, install new skills, and manage workspace extensions. Use when the user asks to find, install, list, or configure skills, or mentions skill registry, extensions, or workspace capabilities. - 90skill-update
Use when the user wants to check whether installed agent skills are outdated or update them - "update my skills", "are my skills up to date", "스킬 업데이트", "스킬 최신화" - for skills installed with npx skills, as git clones, or as Claude Code plugins, across Claude Code, Codex, Cursor,… - 100skill-inventory
Lists every Agent Skill installed for the current user and project across Claude Code, Codex, Gemini CLI and Antigravity, and reports duplicate names, skills that fail to load, descriptions that compete for the same request, and the context cost of the skill listing. Use when… - 100using-ecosystem
Ecosystem discovery advisor. Use when the user asks which skill, agent, or workflow fits a task, how to delegate, or what tools are installed. Reads the installed skills and agents at runtime. Triggers include 'which skill', 'which agent', 'orient me'.