Skip to content

PierceS1/PS1 / .claude/skills/repo-skills

repo-skills

Verified

After cloning a repository, scan for skill definitions and load them on demand. Always use this after cloning any repo.

FileKindSize
SKILL.mdskill md1.2 KB
---
name: repo-skills
description: After cloning a repository, scan for skill definitions and load them on demand. Always use this after cloning any repo.
---

# Repo Skill Discovery

After cloning any repository, scan for skill definitions. Replace `<repo-root>` below with the absolute path of the cloned repository:

```bash
find <repo-root>/.claude/skills -name "SKILL.md" 2>/dev/null
find <repo-root>/.codex/agents \( -name "*.md" -o -name "*.toml" \) 2>/dev/null
find <repo-root>/.skills -name "SKILL.md" 2>/dev/null
```

If no skill files are found, skip the index output and proceed with the task.

For each skill file found, read only the metadata (YAML frontmatter for .md files, top-level fields for .toml files) to extract the name and description. Output a compact index:

<repo-skills repo="org/repo-name" path="/absolute/path/to/repo">
- skill-name: one-line description
- skill-name: one-line description
</repo-skills>

When a discovered skill is relevant to your current task, read its full file and follow its instructions.

If the `<repo-skills>` index is missing from your conversation history (e.g. after context compaction), re-scan the repo using the path from `git rev-parse --show-toplevel` in the repo's working directory to rebuild it.
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 CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall