Search
By Neeeophytee
Skills
Sort:BestMost starsTrending todayTrending this weekTrending this monthNewestRecently updatedName
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. | Neeeophytee/ | 343 | — | ~650 | Automated safety check: Pass | MIT | 11 days ago |
| 2 | Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. | Neeeophytee/ | 343 | — | ~631 | Automated safety check: Pass | MIT | 11 days ago |
| 3 | Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills. | Neeeophytee/ | 343 | — | ~482 | Automated safety check: Pass | MIT | 11 days ago |
| 4 | Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. | Neeeophytee/ | 343 | — | ~492 | Automated safety check: Pass | MIT | 11 days ago |
| 5 | After a working session, produce a report on what changed plus a quiz the user must pass before merging. | Neeeophytee/ | 343 | — | ~532 | Automated safety check: Pass | MIT | 11 days ago |
| 6 | Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. | Neeeophytee/ | 343 | — | ~779 | Automated safety check: Pass | MIT | 11 days ago |
| 7 | Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. | Neeeophytee/ | 343 | — | ~474 | Automated safety check: Pass | MIT | 11 days ago |
| 8 | Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. | Neeeophytee/ | 343 | — | ~503 | Automated safety check: Pass | MIT | 11 days ago |
| 9 | Interview the user one question at a time to resolve remaining ambiguity before implementation. | Neeeophytee/ | 343 | — | ~447 | Automated safety check: Pass | MIT | 11 days ago |
| 10 | Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. | Neeeophytee/ | 343 | — | ~493 | Automated safety check: Pass | MIT | 11 days ago |
| 11 | Use existing source code as the specification when the user can't describe what they want in words. | Neeeophytee/ | 343 | — | ~476 | Automated safety check: Pass | MIT | 11 days ago |
| 12 | Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. | Neeeophytee/ | 343 | — | ~790 | Automated safety check: Pass | MIT | 11 days ago |
| 13 | Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. | Neeeophytee/ | 343 | — | ~676 | Automated safety check: Pass | MIT | 11 days ago |
| 14 | Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed. | Neeeophytee/ | 343 | — | ~660 | Automated safety check: Pass | MIT | 11 days ago |
