Agent skill

Skill Management

List, inspect, patch, or delete skills from ~/.claude/skills/.

MITAuto-check passedProduct & Project Management

Install Skill Management

skills CLI

$ npx skills add Szotasz/marveen --skill skill-management -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/seed-skills/skill-management .claude/skills/skill-management && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .claude/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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

$skill-installer install https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management

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 Szotasz/marveen --skill skill-management -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/seed-skills/skill-management .agents/skills/skill-management && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .agents/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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 Szotasz/marveen --skill skill-management -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/seed-skills/skill-management .cursor/skills/skill-management && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .cursor/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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

$ gemini skills install https://github.com/Szotasz/marveen.git --path seed-skills/skill-management

--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 Szotasz/marveen --skill skill-management -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/seed-skills/skill-management .gemini/skills/skill-management && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .gemini/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management

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 Szotasz/marveen --skill skill-management -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .github/skills && cp -r skills-src/seed-skills/skill-management .github/skills/skill-management && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .github/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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 Szotasz/marveen --skill skill-management -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Szotasz/marveen skill-management --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Szotasz/marveen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/seed-skills/skill-management .opencode/skills/skill-management && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "skill-management" agent skill from https://github.com/Szotasz/marveen/tree/develop/seed-skills/skill-management into .opencode/skills/skill-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-management", 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: skill-management
GitHub stars: 117
Token cost: ~1.9k tokens
SKILL.md length: 558 words
Files: 1
Skills in repo: 18
Repo updated: Oct 10, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

List, inspect, patch, or delete skills from ~/.claude/skills/.

Works in 3 steps: Read ~/.claude/skills/{name}/SKILL.md → If it has a references/ subdirectory,… → Present the full content
The user asks about available skills
SKILL.md covers When to use, Arguments, Procedure and Skill Index Regeneration, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Skill Management is an agent skill from Szotasz/marveen. List, inspect, patch, or delete skills from ~/.claude/skills/. Use when the user asks about available skills, wants to modify an existing skill, or when a retrospective proposes skill changes. Trigger on "/skills" command or skill-related retrospective actions.

Its SKILL.md is about 1.9k 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 Product & Project Management, covering Skill management and Retrospectives. The repository describes itself as: AI csapatod, ami fut amíg te alszol. The licence is MIT.

When your agent uses it

The user asks about available skills
Wants to modify an existing skill
A retrospective proposes skill changes
/skills command

Example prompts

“/skills”
“/skill-management”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Read ~/.claude/skills/{name}/SKILL.md
If it has a references/ subdirectory, list those files too
Present the full content

What it can do on your machine

Read from SKILL.md and the folder at commit e1ac6cc. 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 markdown).
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

Skill Management loads about 1.9k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 558 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~70
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

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 Szotasz/marveen at commit e1ac6cc, republished under its MIT licence (© Szotasz). 558 words, ~1,872 tokens.

Download SKILL.mdSave it as .claude/skills/skill-management/SKILL.md (or your agent's skills folder).

name: skill-management
description: List, inspect, patch, or delete skills from ~/.claude/skills/. Use when the user asks about available skills, wants to modify an existing skill, or when a retrospective proposes skill changes. Trigger on "/skills" command or skill-related retrospective actions.

Skill Management -- CRUD for the Skill Library

When to use

User asks "what skills do I have?" or "list skills"
User wants to inspect a specific skill's content
A /retrospective proposes CREATE, PATCH, or DELETE actions on skills
User says "update skill X" or "fix skill Y"
Periodic audit: check for stale or duplicate skills

Arguments

Argument	Required	Description
`action`	YES	One of: `list`, `show`, `create`, `patch`, `delete`, `audit`
`name`	for show/patch/delete	Skill directory name (e.g. `github-pr-rebase-merge`)
`scope`	no	`global` (default, ~/.claude/skills/) or `local` (./claude/skills/)

Examples:

/skills action=list -- list all skills with descriptions
/skills action=show name=github-pr-rebase-merge -- show full SKILL.md
/skills action=create name=new-skill -- interactive skill creation
/skills action=patch name=existing-skill -- modify specific sections
/skills action=delete name=old-skill -- remove with confirmation
/skills action=audit -- find stale, duplicate, or oversized skills

Procedure

action=list

bash

SKILL_DIR="${HOME}/.claude/skills"
if [ "$SCOPE" = "local" ]; then SKILL_DIR="./.claude/skills"; fi

echo "=== Skills in $SKILL_DIR ==="
for dir in "$SKILL_DIR"/*/; do
  skill_file="$dir/SKILL.md"
  if [ -f "$skill_file" ]; then
    name=$(basename "$dir")
    # Extract description from frontmatter
    desc=$(sed -n '/^description:/{ s/^description: *//; p; q; }' "$skill_file")
    printf "  %-35s %s\n" "$name" "$desc"
  fi
done

Present as a compact table. If both global and local exist, show both.

action=show

Read ~/.claude/skills/{name}/SKILL.md
If it has a references/ subdirectory, list those files too
Present the full content

action=create

Interactive skill creation workflow:

Ask for trigger context: "When should this skill activate?"
Ask for procedure steps: "What does it do, step by step?"
Generate SKILL.md with proper frontmatter:

markdown

---
name: {name}
description: {one-line, specific about triggers}
---

# {Title}

## When to use
{Concrete triggers and contexts}

## Procedure
1. {Step}
2. {Step}
...

## Pitfalls
- {Known issues, if any}

Write to ~/.claude/skills/{name}/SKILL.md
Update .skill-index.md if it exists

Rules:

Keep SKILL.md under 500 lines
Large reference material goes in references/ subdirectory
Description must be specific enough for L0 matching (not "does stuff")
Procedure steps must be concrete and executable

action=patch

Targeted modification of an existing skill:

Read the current SKILL.md
Identify the section to change based on user input or retrospective proposal
Apply targeted edit (old text -> new text), not full rewrite
If adding a pitfall from a runtime discovery, append to the Pitfalls section
Log the patch reason in the Pitfalls section if it came from an error recovery

Rules:

Never rewrite the entire skill for a small change
Preserve existing pitfalls and procedure steps unless explicitly removing
If the patch changes triggers, update the description in frontmatter too

Show full SKILL.md (228 more words)Show less

action=delete

Show the skill content first
Ask for confirmation: "Delete skill '{name}'? This removes the entire directory."
On confirmation:

bash

rm -rf "${HOME}/.claude/skills/${NAME}"

Update .skill-index.md if it exists

Rules:

Never delete without showing content first
Never delete without explicit user confirmation
If the skill is referenced by other skills, warn before deleting

action=audit

Comprehensive skill library health check:

Stale detection: Skills not referenced in any CLAUDE.md and with no git activity in 60+ days

bash

for dir in ~/.claude/skills/*/; do
  name=$(basename "$dir")
  skill_file="$dir/SKILL.md"
  if [ -f "$skill_file" ]; then
    mod_date=$(stat -f '%Sm' -t '%Y-%m-%d' "$skill_file" 2>/dev/null || stat -c '%y' "$skill_file" 2>/dev/null | cut -d' ' -f1)
    echo "$mod_date  $name"
  fi
done | sort

Duplicate detection: Skills with overlapping descriptions or triggers

bash

for dir in ~/.claude/skills/*/; do
  skill_file="$dir/SKILL.md"
  if [ -f "$skill_file" ]; then
    desc=$(sed -n '/^description:/{ s/^description: *//; p; q; }' "$skill_file")
    echo "$(basename "$dir"): $desc"
  fi
done

Review for semantic overlaps manually.

Size check: Skills over 500 lines that should be refactored

bash

for dir in ~/.claude/skills/*/; do
  skill_file="$dir/SKILL.md"
  if [ -f "$skill_file" ]; then
    lines=$(wc -l < "$skill_file")
    if [ "$lines" -gt 500 ]; then
      echo "OVERSIZED ($lines lines): $(basename "$dir")"
    fi
  fi
done

Index sync: Check .skill-index.md matches actual directories

bash

if [ -f ~/.claude/skills/.skill-index.md ]; then
  echo "Index exists, checking sync..."
  # Compare index entries vs actual directories
  indexed=$(grep -oP '(?<=\[)[^\]]+' ~/.claude/skills/.skill-index.md | sort)
  actual=$(ls -d ~/.claude/skills/*/ 2>/dev/null | xargs -I{} basename {} | sort)
  diff <(echo "$indexed") <(echo "$actual")
fi

Present findings as:

## Skill Audit Results

Total skills: {count} (global) + {count} (local)
Disk usage: {size}

### Issues Found
- [STALE] skill-name: last modified 2025-01-15 (130 days ago)
- [DUPLICATE] skill-a / skill-b: overlapping trigger "when deploying..."
- [OVERSIZED] skill-name: 720 lines (max 500)
- [UNINDEXED] skill-name: exists on disk but not in .skill-index.md

### Recommended Actions
1. DELETE skill-a (superseded by skill-b)
2. PATCH skill-c: move 300 lines to references/
3. REINDEX: regenerate .skill-index.md

Skill Index Regeneration

When skills are created, patched, or deleted, regenerate the index:

bash

INDEX_FILE="${HOME}/.claude/skills/.skill-index.md"
echo "# Skill Index" > "$INDEX_FILE"
echo "" >> "$INDEX_FILE"
echo "Auto-generated. Do not edit manually." >> "$INDEX_FILE"
echo "" >> "$INDEX_FILE"

for dir in ~/.claude/skills/*/; do
  skill_file="$dir/SKILL.md"
  if [ -f "$skill_file" ]; then
    name=$(basename "$dir")
    desc=$(sed -n '/^description:/{ s/^description: *//; p; q; }' "$skill_file")
    echo "- **$name**: $desc" >> "$INDEX_FILE"
  fi
done

Pitfalls

Do NOT auto-delete skills without user confirmation
Do NOT create skills for one-off tasks (check the 2+ occurrence rule)
Audit results are advisory, not auto-executed
The .skill-index.md is for L0 matching only; the full SKILL.md is L1
On macOS, stat syntax differs from Linux; the audit commands handle both
If a skill references external APIs or tokens, never include the actual values

Relation to other mechanisms

Mechanism	Skill-management's role
retrospective	Retrospective proposes changes; skill-management executes them
CLAUDE.md	CLAUDE.md references skills; skill-management maintains the library
.skill-index.md	Skill-management regenerates this after mutations
seed-skills/	Seed skills are templates; once installed they become regular skills managed here

Files

Just SKILL.md in seed-skills/skill-management of Szotasz/marveen.

Open the folder on GitHubat commit e1ac6cc

Compare with similar skills

Skill Management 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 Management compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Skill Management this skillSzotasz/marveen	117	—	~1.9k	Automated safety check: Pass	MIT	today
Skill Retrokenneth-liao/ai-launchpad-marketplace	126	—	~2.1k	Automated safety check: Pass	None	6 mo ago
Speckit Opsmill Retrospectopsmill/infrahub	534	—	~2.3k	Automated safety check: Pass	Apache-2.0	today
Retrospective Codifymizchi/skills	360	—	~3.2k	Automated safety check: Pass	None	8 days ago
Retrojellydn/my-ai-tools	123	—	~1.7k	Automated safety check: Pass	MIT	today
Sprint RetroStanshy/AgentHub	202	—	~160	Automated safety check: Pass	MIT	6 mo ago

Similar skills

Skill Retro
kenneth-liao/ai-launchpad-marketplace
A skill your agent uses when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review…
126 GitHub stars~2.1k tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Speckit Opsmill Retrospect
opsmill/infrahub
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
534 GitHub stars~2.3k tokensUpdated today
Product & Project ManagementAuto-check passed
Retrospective Codify
mizchi/skills
Pair "what failed first" with "what finally worked" and codify the should-have-known-it insight as an ast-grep rule, a skill, or a CLAUDE.md rule.
360 GitHub stars~3.2k tokensUpdated 8 days ago
Product & Project ManagementAuto-check passed
Retro
jellydn/my-ai-tools
Review a coding session and propose environment changes that prevent repeated agent mistakes.
123 GitHub stars~1.7k tokensUpdated today
Product & Project ManagementAuto-check passed
Sprint Retro
Stanshy/AgentHub
Generate sprint retrospective by analyzing section 10 data. An agent skill from Stanshy/AgentHub.
202 GitHub stars~160 tokensUpdated 6 mo ago
Product & Project ManagementAuto-check passed
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
136k GitHub stars~2.4k tokensUpdated yesterday
Product & Project ManagementAuto-check passed

Questions about Skill Management

What does Skill Management do?

List, inspect, patch, or delete skills from ~/.claude/skills/. Skill Management is an agent skill from Szotasz/marveen.claude/skills/.

When should I use Skill Management?

Skill Management fits situations like: the user asks about available skills; wants to modify an existing skill; A retrospective proposes skill changes; /skills command.

How do I install Skill Management in Claude Code?

Run `npx skills add Szotasz/marveen --skill skill-management -a claude-code`. Or copy the skill folder (seed-skills/skill-management in Szotasz/marveen) into .claude/skills/skill-management in your project. Claude Code loads it when a task matches its description.

How do I install Skill Management in Codex?

Run `npx skills add Szotasz/marveen --skill skill-management -a codex`. Or copy the skill folder (seed-skills/skill-management in Szotasz/marveen) into .agents/skills/skill-management in your project. Codex loads it when a task matches its description.

Can I use Skill Management 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 Szotasz/marveen --skill skill-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-management, .gemini/skills/skill-management, .github/skills/skill-management and .opencode/skills/skill-management in your project.

What does Skill Management need to run?

SKILL.md names no scripts, command-line tools or credentials: Skill Management is instructions for the agent only.

Does Skill Management 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 Skill Management 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 Skill Management use?

Skill Management 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 Skill Management use?

About 1.9k tokens (SKILL.md is roughly 7.5k 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 Skill Management?

Skills that share tags, products or a category with Skill Management: Skill Retro (kenneth-liao/ai-launchpad-marketplace, 126 stars), Speckit Opsmill Retrospect (opsmill/infrahub, 534 stars), Retrospective Codify (mizchi/skills, 360 stars) and Retro (jellydn/my-ai-tools, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Management?

Szotasz (a GitHub user) maintains it in Szotasz/marveen, which has 117 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 10, 2026.

Source: Szotasz/marveen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Skill Management

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Skill Management -- CRUD for the Skill Library

When to use

Arguments

Procedure

action=list

action=show

action=create

action=patch

action=delete

action=audit

Skill Index Regeneration

Pitfalls

Relation to other mechanisms

Files

Compare with similar skills

Similar skills

More from Szotasz/marveen

Related

Questions about Skill Management