Library
Claude Code skills, in folders you can copy.
A public, MIT-licensed library of skills, schedules, and project instructions. Each one is a folder with a markdown file inside. Copy it, edit it, run it.
The shape
What a skill looks like
A folder, a markdown file, frontmatter on top, instructions below. Claude Code reads the description to decide when to invoke; the body is what it follows. Here's the skeleton every skill in this library starts from.
---
name: meeting-prep
description: Reads the relevant client folder, calendar, and recent
email before a meeting, then drafts a focused one-page brief.
---
# meeting-prep
Use when a meeting is coming up and a brief is needed that's specific
to who you're meeting and what's happened since you last spoke.
## When to use this
- The user has a meeting in the next 24 hours
- They reference the client by name or slug
- They say "prep me for", "what do I need to know about", or similar
## What it does
1. Reads `clients/<slug>/README.md` for engagement context
2. Pulls the calendar invite via Google Calendar MCP
3. Searches Gmail for the last two weeks of messages with this client
4. Writes a one-page brief to `clients/<slug>/meetings/<date>.md`
## Output
A markdown brief with: meeting context, recent decisions, three things
to raise, and any open action items from the previous meeting.
Schedules and instructions follow the same shape: one folder, one markdown file. The starter version of each lives in _template/ inside its bucket.
What's in it
Inventory
Four buckets: skills, schedules, instructions, essays. Each row links to a folder or file on GitHub. The list grows as artifacts get promoted from personal use, redacted, and published here.
Skills
/skills
Folders Claude Code picks up from ~/.claude/skills/. Each one bundles a description, triggers, and the steps Claude follows when invoked.
- _template The starter SKILL.md. Copy this folder, rename it, fill in the frontmatter and steps.
- end-of-day-review A ten-minute weekday close. Confirm what mattered, surface what's still owed, choose tomorrow's three.
- weekly-self-reflection A Sunday reflection that also logs decisions and proposes knowledge-base updates from one evidence pass.
- decision-log Capture significant decisions with the why, then audit them quarterly so they stop getting re-litigated.
- doc-triage Run a doc through a four-check rubric before it goes up the chain: clarity, evidence, owner and next step, LLM-tell.
- meeting-prep Pull live context from notes, chat, tickets, and the knowledge base into a tight brief for any named meeting.
Schedules
/schedules
Recurring prompts that run via Claude Code's /loop command. Weekly reviews, inbox sweeps, status checks. Each one shows the cadence and what the output looks like.
- _template The starter schedule. Cadence on top, prompt body below, sample output at the bottom.
- first schedules coming soon Sunday review, midweek inbox sweep, daily standup draft. Promoted as they prove themselves.
Instructions
/instructions
Fragments for a project's CLAUDE.md. Guardrails for privacy boundaries, conventions for shared tools, voice and tone rules. Drop them into the repo where Claude Code is going to work.
- _template The starter instructions block. Scope, conventions, banned patterns, escalation rules.
- first instruction sets coming soon Privacy boundary block, voice and tone block, docs-hygiene block. Each as a copyable fragment.
Essays
/essaysThe design layer: why the patterns behind the skills are shaped the way they are. You read these rather than install them. Start with the Monday Cascade, it maps the rest.
- The Monday Cascade Parallel gather, then sequential synthesis, then briefing. One orchestrator replaces six cron jobs.
- The Canonical-Home Rule Every fact has exactly one home; everything else points at it or writes with attribution.
- Synthesis Discipline The output contract for high-stakes synthesis: readability gate, reader-not-producer prose, inline source tags.
- The A9 Enforcement Gate Skill-authoring rules enforced by another skill. A ledger of failure modes, each earned the second time it bit.
- Source-and-Date Tags Every numeric claim carries its source and pull date. Trust-by-default through tagged provenance.
- The Personal Skill Index Route-table, not hardcoded. Adding the Nth skill does not mean editing the first N-1.
Get it
Two ways to install
No Git needed
Download and copy
- Download the repo as a .zip.
- Unzip it anywhere on your machine.
- Open the
skills/folder inside. - Copy any skill folder into
~/.claude/skills/.
Same shape works for schedules/ and instructions/.
With Git
Clone and copy
git clone https://github.com/maxeskell/aiotr-library.git \
~/code/aiotr-library
cp -r ~/code/aiotr-library/skills/<skill-name>/ \
~/.claude/skills/Pull updates later with git pull in ~/code/aiotr-library, then re-copy.
Either way, open a new Claude Code session and the skill is live. Restart isn't strictly required; a fresh session is enough.