Skip to content

gpsaggese/helpers / .claude/skills/skill.consolidate_skills

skill.consolidate_skills

Verified

Consolidate and rename skills by topic to remove redundancy

FileKindSize
SKILL.mdskill md1.6 KB
---
description: Consolidate and rename skills by topic to remove redundancy
model: haiku
---

# Goal
- Consolidate and rename skills by topic, so the skill set is better organized
  and less redundant

# Workflow

## Read Skill Rules
- Read `.claude/skills/skill.rules.md`

## Find All the Topics
- Find the topics by running:
  ```bash
  > find .claude/skills -type d | sort | tail -n +2 | sed 's|^\.claude/skills/||' | awk -F'.' '{print $1}' | sort -u
  ```

## Process Skills for Each Topic
- For each `<TOPIC>`, find its skills in the format
  `.claude/skills/<TOPIC>.<ACTION>/SKILL.md`:
  ```bash
  > mdm skill f <TOPIC>
  ```
- E.g.,
  ```bash
  > mdm skill f testing
  /Users/saggese/src/umd_classes1/helpers_root/.claude/skills/testing.add_end_to_end_tests/SKILL.md
  /Users/saggese/src/umd_classes1/helpers_root/.claude/skills/testing.fix_input_output_vars/SKILL.md
  /Users/saggese/src/umd_classes1/helpers_root/.claude/skills/testing.fix_mock_tests/SKILL.md
  /Users/saggese/src/umd_classes1/helpers_root/.claude/skills/testing.fix_unit_tests/SKILL.md
  ```

## Propose the Plan
- For each `<TOPIC>`, check for redundant actions and suggest clearer skill names

## Execute the Plan
- Ask the user to approve the plan
- Implement the plan:
  - Rename files with `git mv`
  - Add new files with `git add`
  - Remove files with `git rm`

# Verification
- [ ] The user approved the plan before any file was changed
- [ ] Every renamed or removed skill directory still has a valid `SKILL.md`, or
      was intentionally removed
- [ ] No reference elsewhere in `.claude/skills` points to a renamed or removed
      skill's old path
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall