Why skills?

• You know things the agent doesn't — skills let you teach it your expertise
• Doing it manually works once. A skill makes it repeatable and shareable with your whole team
• A skill is a folder — a SKILL.md that the agent discovers, plus code, tests, and demo data
• Write it once, run it on any agent — Claude Code, Codex, Gemini CLI, Cursor, and many more

ClawBio skills follow the open Agent Skills specification (agentskills.io), originally developed by Anthropic

Working with your coding agent

You need a coding agent: Claude Code, Codex, Gemini CLI, or similar. They all read the project instructions.

• You will press Enter a lot. Read what you're approving. The agent runs commands and edits files on your behalf — you are responsible.
• The agent will agree with you a lot. Push back — it often changes its mind and finds a better answer when challenged.
• /plan — planning before coding saves tokens, saves time, and catches bad ideas early.
• /compact — long conversations cause context rot: the agent forgets earlier details. Compacting summarises the history so it can keep going.

Get set up

docs.clawbio.ai/tutorials/setup

docs.clawbio.ai/tutorials/build-a-skill

# 1. You need a GitHub account (github.com/join)
#    So you can push code and open a pull request
# 2. Fork ClawBio/ClawBio on GitHub and clone your fork
#    Your agent works locally on your copy of the repo

Your agent can help with all of this — forking, cloning, pushing code, opening PRs.

Plan as a team — at least 15 minutes

The most important thing today isn't the AI — it's everyone in this room. Share your domain expertise.

Before you write any code, discuss with the people around you:

1. What problem does your skill solve? One sentence. One thing done really well.
2. What goes in? What comes out? Use open file formats. Output something another ClawBio skill can take as input.
3. What could go wrong? Think about edge cases. Be defensive — add guardrails.

Aim for an MVP. A plan prevents scope creep. If you can't explain it in one sentence, it's too big.

Do this before you touch any code.

Not sure what to build?

You don't have to write a new skill from scratch. Pick any of these:

• Look at GitHub issues for wanted skills
• Audit or red-team an existing skill
• Test a skill with real, publicly-available data
• Translate a skill to another language

Go build

# 1. Open an issue for your skill
"Open an issue on ClawBio/ClawBio using the new skill proposal template"

# 2. Start building
"I want to build a new ClawBio skill that <solves your problem>.
 Ask me any clarifying questions."

Respect original works. Cite research properly — LLMs hallucinate references. Never assume scientific correctness — validate against the original.

See rewrites.bio by Seqera  ·  Stuck? Raise your hand — helpers are here.

Supercharge your agent (optional — try later)

Agent skills teach your coding agent how to work. Install them with npx skills add.

• Superpowers (obra/superpowers) — brainstorming, TDD, planning, debugging. A full dev workflow.
• Grilling (mattpocock/skills@grilling) — the agent interviews you about every aspect of your plan, one question at a time, until the design is solid.

Use skills to help write your own skills more effectively — Superpowers enforces TDD and planning, Grilling sharpens your spec before you start.

Browse more at skills.sh — or npx skills find <query>

Open a PR
before you leave.

Unfinished is fine. Unpushed is lost.

github.com/ClawBio/ClawBio  ·  clawbio.ai