Search notes and jump to a post. Press ⌘K (Mac) or Ctrl+K (Windows) to open anytime.
Skills for coding agents
Practical workflows I hand to coding agents. They handle the checklist. I keep the judgment calls.
Pick the skills you want. The installer adds editable files to your project.
npx skills add jcottam/agent-resources
npx skills updateskills.sh ↗Single skill
npx skills add jcottam/agent-resources/skills/engineering/ship
Install the complete set as a managed plugin. Claude Code keeps it updated.
/plugin marketplace add jcottam/agent-resources /plugin install agent-resources
Think through the work. Then build and ship it.
Frame the problem, challenge assumptions, and make the work clear.
Activate rigorous, no-nonsense advisory mode for deep analysis, research, critical review, or honest assessment.
Rigorous advisory mode. When this skill is active, you operate as a direct, intellectually honest analyst. Your job is to be right, not agreeable. Accuracy is your success metric, not approval.
Opinionated rubber duck.
Restate my idea in your own words so I can hear it fresh, then flag anything that sounds fuzzy, contradictory, or underspecified. After that, give your concrete opinion or suggestion on what I should do.
Compact a chat session or task into a curated markdown handoff file under ~/.agents/handoffs/ for continuation in a new agent turn or chat.
Editorially compress session context into a small markdown checkpoint an agent can load in a new turn. Raw transcripts live under Cursor project folders; handoffs are curated, short, and decision-dense.
Move a tested personal agent skill into a shared skills repository, check for overlap, normalize metadata, update the catalog and release files, validate the package, and publish it through a reviewable branch.
Promote a tested personal skill into a shared repository without creating duplicate skills or losing its working version.
Orient, build, review, release, and publish.
Orient a developer to an unfamiliar codebase by systematically exploring its structure, purpose, features, conventions, and workflows.
Systematically explore a codebase and produce a structured orientation that tells a developer everything they need to start working productively. Depth scales with project size — small projects get a tight summary, large projects get a layered map.
Draft a content wireframe for a website or page before any design or code.
Write every word a page needs — in order, with intent annotations — before touching layout, color, or code. The wireframe is the blueprint; design follows.
Upload files to Cloudflare R2 and return a shareable public URL.
Upload any file to Cloudflare R2 and get back a shareable public URL.
Review commits in a branch, date range, or recent history; group related work into a clean linear history; and verify that the final tree is unchanged.
Turn noisy Git history into a small, reviewable commit stack without changing the final code.
Summarize a logical grouping of git commits into plain-language release notes for non-technical readers.
Turn a logical grouping of commits into clear summaries for teammates, stakeholders, or changelogs — not developer jargon.
Validate a branch, run quality gates, update documentation and changelog, and open a pull request.
Pre-flight checklist that validates the branch, runs quality gates, updates documentation and changelog, and opens a pull request.
Forensic, stage-aware pull request review.
Forensic, stage-aware pull request review. Reconstructs the commit narrative, tests the PR's architectural premises against project reality, and produces a review comment the user can post directly.
11 skills · MIT · GitHub
I use these often. Thanks to the people who made them.