Agent skills
Skills that grew out of my daily work with AI agents. Each one exists because I needed it.
Install all
npx skills add 50BytesOfJohn/skillsREADME
50BytesOfJohn Skills
Hey, John here. This is a small collection of agent skills I'm working on for AI coding tools that support the Agent Skills standard.
Feel free to use them, contribute improvements, or share feedback if something could be clearer or more useful.
Install
Install all skills:
npx skills add 50BytesOfJohn/skills
Or pick a specific skill:
npx skills add 50BytesOfJohn/skills --skill aaa-unit-tests
npx skills add 50BytesOfJohn/skills --skill no-waffle
npx skills add 50BytesOfJohn/skills --skill opencode
npx skills add 50BytesOfJohn/skills --skill update-dependencies
Browse on skills.sh.
Skills
| Skill | Description |
|---|---|
aaa-unit-tests |
Write clear, maintainable unit tests using the Arrange-Act-Assert pattern. |
no-waffle |
Cut walls of text. Shorter answers, less jargon, no filler. |
opencode |
Use the opencode CLI to consult another model for a second opinion, blind review, or multi-turn design discussion. |
update-dependencies |
Update dependencies to their latest versions and validate the upgrade against real changelogs. |
aaa-unit-tests
Write clear, maintainable unit tests using Arrange-Act-Assert. TypeScript/JavaScript first; the rules apply broadly.
Use when: creating or refactoring unit tests.
no-waffle
Cut walls of text. Write shorter, drop the jargon, skip the filler.
Use when: something is too long, too corporate, or full of bullshit. Also whenever the agent is writing something you will actually read.
opencode
Run the opencode CLI correctly when asking another model for a second opinion, blind review, or multi-turn design discussion. Covers the non-obvious CLI mechanics that cause silent failures (prompt ordering, file attachments, long runs, sessions).
Use when: consulting another model/agent, running something by a named model, or getting multiple models to review something.
Requires: opencode CLI installed and authenticated.
update-dependencies
Update every dependency to its latest version, then validate the upgrade: real changelogs over training data, hold back what the framework pins, fix the easy breaks, and report what needs a decision.
Use when: updating, upgrading, or bumping dependencies, checking for outdated packages, or asking what's new in your deps.