# skill-manager

> Comprehensive management tool for local skills in the skills directory. Use when Claude needs to: (1) List all available skills and their descriptions, (2) View detailed information about a specific skill (SKILL.md content and file structure), (3) Create new skills using templates, (4) Delete existing skills, (5) Package skills into .skill files for distribution, or (6) Search skills by name or description keywords.

- Author: Rorance
- Repository: luoz76070-art/my-skill
- Version: 20260122123104
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/luoz76070-art/my-skill
- Web: https://mule.run/skillshub/@@luoz76070-art/my-skill~skill-manager:20260122123104

---

---
name: skill-manager
description: "Comprehensive management tool for local skills in the skills directory. Use when Claude needs to: (1) List all available skills and their descriptions, (2) View detailed information about a specific skill (SKILL.md content and file structure), (3) Create new skills using templates, (4) Delete existing skills, (5) Package skills into .skill files for distribution, or (6) Search skills by name or description keywords."
---

# Skill Manager

Manage local skills with both script tools and direct file operations.

## Quick Reference

Use scripts for automated operations or direct file access for inspection and editing.

## Listing Skills

**Script approach:**
```bash
python skill-manager/scripts/list_skills.py [skills-dir]
```

**Direct approach:**
- Use `glob` tool to find all `**/SKILL.md` files
- Read each SKILL.md to extract name, description, and structure

**When to use:**
- Script: Quick overview of all skills
- Direct: Need to parse or filter skill metadata programmatically

## Creating Skills

**Script approach:**
```bash
python skill-manager/scripts/create_skill.py <skill-name> [--path <output-dir>]
```

**Direct approach:**
- Create directory structure manually following skill conventions
- Write SKILL.md with proper frontmatter (name, description)
- Add optional resources (scripts/, references/, assets/)

**When to use:**
- Script: Standard skill creation with template
- Direct: Custom skill structure or partial creation

## Viewing Skill Details

**Script approach:**
```bash
python skill-manager/scripts/view_skill.py <skill-name> [skills-dir]
```

**Direct approach:**
- Read `<skill-name>/SKILL.md` for content
- Use `ls` or `glob` to show file structure
- Read reference files for additional context

**When to use:**
- Script: Formatted display of skill information
- Direct: Need to read specific files or navigate structure

## Deleting Skills

**Script approach:**
```bash
python skill-manager/scripts/delete_skill.py <skill-name> [skills-dir]
```

**Direct approach:**
```bash
rm -rf <skill-name>
```

**Warning:** Deletion is irreversible. Always confirm with user first.

**When to use:**
- Script: Safe deletion with confirmation
- Direct: Simple removal without safety checks

## Packaging Skills

**Script approach:**
```bash
python skill-manager/scripts/package_skill.py <skill-path> [output-dir]
```

**Direct approach:**
```bash
python skill-creator/scripts/package_skill.py <skill-path> [output-dir]
```

**Validation:** Script automatically checks:
- YAML frontmatter format
- Required fields (name, description)
- Directory structure
- File organization

**When to use:**
- Script: Validation + packaging in one step
- Direct: Need to customize packaging or access validation separately

## Searching Skills

**Script approach:**
```bash
python skill-manager/scripts/search_skills.py <query> [skills-dir]
```

**Direct approach:**
- Use `grep` tool to search SKILL.md files for keywords
- Search in frontmatter (name, description) or body content

**When to use:**
- Script: Formatted search results with highlights
- Direct: Programmatic filtering or custom search patterns

## Skill Structure

Every skill contains:

```
skill-name/
├── SKILL.md (required)
│   ├── YAML frontmatter: name, description
│   └── Markdown body: instructions
├── scripts/ (optional) - Executable code
├── references/ (optional) - Documentation
└── assets/ (optional) - Templates, resources
```

See `references/skill_structure.md` for detailed conventions and examples.

## Best Practices

1. **Always confirm destructive actions** (delete, overwrite)
2. **Validate before packaging** to ensure skill integrity
3. **Use scripts for common operations** to avoid errors
4. **Check skill exists** before operations (view, delete, package)
5. **Backup skills** before bulk operations

## Error Handling

Scripts handle common errors:
- Invalid skill names or paths
- Missing SKILL.md files
- Malformed YAML frontmatter
- File permission issues

For custom error handling or edge cases, use direct file operations with try-except blocks.