If your AI workflow still makes you repeat the same instructions in every single chat, that's a tax you don't need to pay. I built Ink and Agency to fix that friction point. It’s a practical skills pack designed to integrate right into Claude—and can be adapted for other agents, giving reusable prompts for writing, planning, triage, architecture design, and just general day-to-day work.
I wanted better outputs with less effort and more consistency across tasks. So I turned repeatable playbooks into discrete skills, each with clear boundaries and predictable behavior.
Why I Built It
Most agent failures don't happen because the model is bad. They happen because the prompt quality falls apart.
You ask for something broad, get a broad response. Then you spend time correcting it—steering it back on track. That’s fine if you do it once in a while. But when that becomes your daily job, it grinds you down.
Ink and Agency packages task-specific behavior into reusable units. Now, you can route work by intent instead of rewriting the entire process every time.
What's In The Pack
The repository is structured like a catalog: one folder per skill with a SKILL.md entry point. It gives you practical coverage across areas that teams actually deal with:
- Writing: Drafting, shaping, humanizing, and structuring long-form content.
- Analysis: Codebase explanation, issue triage, and message breakdown.
- Planning: Sprint planning, review reporting, standup prep, and daily briefings.
- Collaboration: Structured critique modes or multi-persona consultation (a "council").
- Workspace: Operations for Obsidian notes, markdown files, canvases, and general vault work.
Quick Start for Claude Users:
git clone git@github.com:risadams/skills.git "$HOME/.claude/skills"
After that, the skills are ready—no extra launcher needed.
The Real Value in Day-to-Day Work
A good skills pack isn't just a bag of clever prompts. It’s a reliability layer. Here is what changes after you start using one:
- Better handoffs: Tasks are framed consistently, so the output quality doesn't feel random.
- Less context thrash: You stop re-explaining your process in every single chat thread.
- Faster execution: Known task types map directly to known skill patterns.
- Easier team adoption: Every skill has a stable surface area and clear purpose—it’s predictable.
If you work in DevOps, delivery, or product engineering, this pattern hits home quickly. You're already used to turning repeated work into scripts, templates, and automation. Skills are just that move for prompt-driven work.
A Few Quick Examples of Use
You don't have to write long instructions; you can just ask for the outcome:
Use break-it-down on this email to explain what it is really saying.Run codebase-explain for this module.Triage PROJ-1234.Run a clarity-council on this design tradeoff.
That's the whole point. You ask for outcomes, not rituals.
