All authors
Claude Skills by boshu2
github.com/boshu265 skills0 installs92 views
- RefactorRestructure or clean up code with no behavior change, proved by before-and-after checks. Use when: asked to clean up, extract, dedupe or simplify, even one function.Votes: 0GitHub stars: 446
- Reverse EngineerTear down a competitor''s repo or product into a feature inventory and adoption choices. Use when: comparing us to another tool or asking what to steal.Votes: 0GitHub stars: 446
- RpiDrive one accepted change through implementation and checks to done, with one fresh review only where a mistake is costly. Use when: selected by name.Votes: 0GitHub stars: 446
- SecurityReview code for security problems; scan for vulnerabilities, secrets, dependency and prompt risks. Use when: asked whether code is safe to ship, even one small handler.Votes: 0GitHub stars: 446
- Skill BuilderCreate, repair, audit or consolidate agent skills (SKILL.md packages). Use when: writing or fixing a skill, its description or structure. Not for one-off lessons; use Memory.Votes: 0GitHub stars: 446
- Skill EvalMeasure whether a skill helps by comparing runs with and without it. Use when: reading skill A/B results or deciding to keep, revise or remove one.Votes: 0GitHub stars: 446
- TestWrite or assess tests that prove behavior and would fail without the fix. Use when: writing tests, TDD, or asked whether a green test is enough.Votes: 0GitHub stars: 446
- Using GcOperate Gas City through its own doors: Mayor, doctor and native run state. Use when: Gas City is selected or a gc run looks stuck.Votes: 0GitHub stars: 446
- ValidateFreshly judge whether a finished change and its claims meet original acceptance: PASS, FAIL or NOT_PROVEN. Use when: asked for a go/no-go, sign-off or independent verdict.Votes: 0GitHub stars: 446
- MemoryWrite, find or curate lessons and agent rules with stated evidence and limits. Use when: asked to remember something or write a rule into agent instructions.Votes: 0GitHub stars: 446
- OrchestrateCoordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.Votes: 0GitHub stars: 446
- ReviewGive advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.Votes: 0GitHub stars: 446
- InterviewInterview you one question at a time, each with a recommendation, to settle a big outcome before agents work alone. Use when: selected by name.Votes: 0GitHub stars: 446
- NavigatePick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.Votes: 0GitHub stars: 446
- Claude ExecRun one prompt through headless Claude with scoped permissions and a time bound. Use when: scripting or automating a `claude -p` call, even a simple one.Votes: 0GitHub stars: 446