leek/agent-skills / skills/setup
setup
VerifiedConfigure this repo for the engineering skills: the markdown tracker layout, triage status vocabulary, and domain doc layout.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
| agents/openai.yaml | config | 226 B |
| domain.md | markdown | 2.2 KB |
| issue-tracker.md | markdown | 12.1 KB |
| scripts/test-ticket.shexecutable | script | 33.8 KB |
| scripts/ticket.shexecutable | script | 35.9 KB |
| triage-labels.md | markdown | 1.5 KB |
triage-labels.md
View on GitHub# Triage Status Roles
The skills speak in terms of five canonical triage roles. This file maps those roles to the status strings written into markdown request files under `.scratch/`.
| Role in this skills collection | Status string in our files | Meaning |
| -------------------------- | -------------------- | ---------------------------------------- |
| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this request |
| `needs-info` | `needs-info` | Waiting on reporter for more information |
| `ready-for-agent` | `ready-for-agent` | Fully specified, ready for an AFK agent |
| `ready-for-human` | `ready-for-human` | Requires human implementation |
| `wontfix` | `wontfix` | Will not be actioned |
When a skill mentions a role (e.g. "set the AFK-ready status"), write the corresponding string as the file's status. **How** it's stored depends on the file: wayfinder-pipeline files (`map.md`, `spec.md`, `decisions/`, `tickets/`) carry it in YAML frontmatter as `status:` (see `issue-tracker.md`); triage request files carry it as a `**Status:** <string>` line near the top.
Beyond these five triage roles, the pipeline adds two **build lifecycle** values, always legal on a spec or build ticket: `in-progress` (a session has claimed it) and `closed` (resolved).
Edit the right-hand column to match whatever vocabulary you actually use.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |