Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and…
MITAuto-check passed
Install Organize Skills
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a claude-code
Project install by default; add -g for ~/.claude/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .claude/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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.
Type 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.
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .agents/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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.
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .cursor/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .gemini/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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.
Installs 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).
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .github/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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.
skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "organize-skills" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/organize-skills into .opencode/skills/organize-skills/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "organize-skills", 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
organize-skills
GitHub stars
713
Token cost
~1k tokens
SKILL.md length
464 words
Files
1
Skills in repo
74
Repo updated
First seen
Licence
MIT
At a glance
Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and…
Works in 4 steps: Inventory → Classify by backend (the naming rule) → Rename (and fix everything a rename… → …
The user says organize my skills
SKILL.md covers Step 1 — Inventory, Step 2 — Classify by backend…, Step 3 — Rename (and fix… and Step 4 — Verify, plus 1 more section
Calls git
What it does
Organize Skills is an agent skill from OpenClaudia/openclaudia-skills. Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references. Use when the user says "organize my skills", "rename these skills", "clean up the skill library", "enforce a skill naming convention", or "fix broken skill symlinks".
Its SKILL.md is about 1k 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: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.
When your agent uses it
The user says organize my skills
Rename these skills
Clean up the skill library
Enforce a skill naming convention
Example prompts
“organize my skills”
“rename these skills”
“clean up the skill library”
“/organize-skills”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 28bf209. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Organize Skills loads about 1k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 464 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~117
When it runs· the whole SKILL.md, loaded when a task matches
~1k
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.
Download SKILL.mdSave it as .claude/skills/organize-skills/SKILL.md (or your agent's skills folder).
name
organize-skills
description
Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references. Use when the user says "organize my skills", "rename these skills", "clean up the skill library", "enforce a skill naming convention", or "fix broken skill symlinks".
user_invocable
true
argument-hint
[optional: the prefix rule, e.g. 'acme-* if it calls the Acme API, local-* otherwise']
Organize Skills
Reorganize a skill library so names encode what each skill actually touches, and keep symlinks and
cross-references consistent when you rename.
Many setups keep ONE canonical skill library in a shared dir and symlink it into each tool's hub
(e.g. ~/.claude/skills/, ~/.codex/skills/). Some skills live inside a project repo and are
symlinked into the hub. A single rename can therefore touch several symlinks plus every doc that
references the old name — that fan-out is what this skill manages.
Step 1 — Inventory
List every skill and where it really lives. A hub entry is usually a symlink to the canonical dir:
bash
for hub in <hub-1> <hub-2>; do
echo "== $hub =="; ls -la "$hub"
done
Resolve each name to its real directory with readlink -f. Note which skills live in a project repo
versus the shared library — repo-resident renames must be git mv in that repo.
Step 2 — Classify by backend (the naming rule)
The convention: the prefix names the backend the skill depends on, decided by what it actually
calls, not by its topic. Grep each skill dir for the tell-tale dependency:
Calls a specific product's API / database → that product's prefix (e.g. acme-*).
Pure-local (browser automation, offline SOP, file processing, no backend) → a generic/local prefix.
Keep a topical infix when a family is large (e.g. acme-seo-* vs acme-reddit-*) so related skills sort together.
State the classification back to the user before renaming. A skill that feels product-specific but
makes zero backend calls belongs in the local bucket, and vice versa — go by the dependency.
Show full SKILL.md (229 more words)Show less
Step 3 — Rename (and fix everything a rename breaks)
Misplaced in the wrong repo? Move it to the shared library rather than just renaming in place.
Rewire symlinks in every hub. Remove the stale link, create the new one pointing at the
canonical dir. Do this for each tool hub that mirrors the library.
Update the name: frontmatter inside NEW/SKILL.md to match the directory — the loader keys
on it, not on the folder name.
Fix cross-references. Other skills and any long-term memory/notes files may mention OLD by
name or by old path:bash
grep -rln "OLD" <lib> <memory-dirs> 2>/dev/null
Replace the most-specific string first (full old path before the bare name) so a skill that
also moved gets its path updated cleanly.
Step 4 — Verify
bash
# broken symlinks in any hub
for hub in <hub-1> <hub-2>; do
find -L "$hub" -maxdepth 1 -type l ! -exec test -e {} \; -print
done
# no lingering old names
grep -rn "OLD" <lib> 2>/dev/null
# each renamed skill's name: matches its dir
grep -m1 "^name:" <lib>/NEW/SKILL.md
Confirm the loader re-registers each renamed skill under its new name. Remove any pre-existing dead
symlinks you find while sweeping — cheap to fix, confusing to leave.
Notes
Never drop a skill you didn't rename. Only touch what the convention requires.
Renames are cheap and reversible; broken cross-references are the real cost — Steps 3.4 and 4 are the
point of this skill, not the mv.
Commit repo-resident renames one logical rename per commit so they bisect and revert independently.
Organize Skills 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.
Organize Skills compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Organize Skills this skillOpenClaudia/openclaudia-skills
Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
713 GitHub stars~1.7k tokensUpdated today
Auto-check passed
Questions about Organize Skills
What does Organize Skills do?
Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and…. Organize Skills is an agent skill from OpenClaudia/openclaudia-skills. Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references.
When should I use Organize Skills?
Organize Skills fits situations like: the user says organize my skills; rename these skills; clean up the skill library; enforce a skill naming convention.
How do I install Organize Skills in Claude Code?
Run `npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a claude-code`. Or copy the skill folder (skills/organize-skills in OpenClaudia/openclaudia-skills) into .claude/skills/organize-skills in your project. Claude Code loads it when a task matches its description.
How do I install Organize Skills in Codex?
Run `npx skills add OpenClaudia/openclaudia-skills --skill organize-skills -a codex`. Or copy the skill folder (skills/organize-skills in OpenClaudia/openclaudia-skills) into .agents/skills/organize-skills in your project. Codex loads it when a task matches its description.
Can I use Organize Skills 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 OpenClaudia/openclaudia-skills --skill organize-skills -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/organize-skills, .gemini/skills/organize-skills, .github/skills/organize-skills and .opencode/skills/organize-skills in your project.
What does Organize Skills need to run?
Going by SKILL.md and its folder, Organize Skills needs the command-line tools its instructions call (git).
Does Organize Skills access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Organize Skills 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 Organize Skills use?
Organize Skills 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 Organize Skills use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Organize Skills?
Skills that share tags, products or a category with Organize Skills: Test Naming Enforcer (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Organization (thedaviddias/Front-End-Checklist, 74k stars), File Organizer (davila7/claude-code-templates, 33k stars) and Enforce Rules For Typescript (moeru-ai/airi, 50k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Organize Skills?
OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 713 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.
