eagerworks
OrganizationA collection of portable agent skills by Eagerworks — install via the skills.sh CLI for Claude Code, Cursor, Copilot, Codex, Amp, and more.
Categories
Indexed Skills (9)
commit
Commits everything modified or new in the working tree by default, grouped into a series of coherent Conventional Commits — one commit per logical change, staged by path, with the type/scope vocabulary inferred from the repo's own git history — instead of sweeping everything into a single commit. Configurable per repo to ask before including new files. Use when asked to "commit this", "commit my changes", "commit everything", "make a commit", "split this into commits", or to write a commit message for work already staged.
create-pr
Opens (or updates) a pull request with a conventional title, an evidence-backed description, and a real verification checklist — resolving the base branch from evidence, attaching screenshots via the GitHub CLI when the change is visible in the UI, and asking rather than guessing at every genuine judgment call. Use when asked to "open a PR", "create a pull request", "push this and make a PR", "ship this branch", or to fix up an existing PR's title, description, or checklist.
pr-review
Reviews a branch, PR, staged, or working-tree diff for correctness, security, repo-convention, test-coverage, and documentation gaps, returning severity-rated findings without editing code. Use when asked to "review my branch/PR", "is this ready to merge", "check this diff before I push", "does this need an ADR", or to apply fixes for findings from a previous review round. When the target is a GitHub PR, the same report is also posted to the PR — as inline comments on each finding's line plus a summary, by default — so the whole team can read it.
kamal
Sets up, runs, and troubleshoots Kamal deployments (v1 and v2) — zero-downtime Docker deploys to VPS or bare-metal servers. Use when the user mentions Kamal, kamal-proxy, or Traefik, edits config/deploy.yml or .kamal/secrets, or asks to deploy an app to their own server, roll back, add accessories like Postgres or Redis, fix a failed deploy or healthcheck, or upgrade from Kamal 1 to 2.
rest-api-design
Designs and reviews REST APIs: resource naming, HTTP methods and status codes, payload and error formats, pagination, versioning, auth, rate limiting, and OpenAPI specs. Use when adding or renaming an endpoint, asked "is this endpoint RESTful", "what status code should I return", "design the API for X", or to audit an existing API for consistency or security (IDOR, mass assignment).
loop-engineering-audit
Audits a repository for loop-engineering readiness — whether an AI coding agent can pick up a task, implement it, verify it with local checks, and hand off a PR in an unattended loop — and returns a graded report plus the ordered list of work needed to get there. Use when asked "can agents work on this repo autonomously", "audit this project for Claude Code / Cursor / Codex", "what's missing for AI agents to work here", "prepare this repo for loop engineering / agentic development", "is this codebase agent-ready", or to re-check a project after readiness work was done. The report is printed in chat and saved to docs/loop-engineering-audit.md in the audited project.
decision-record
Write or update a decision record (ADR) in docs/decision-records/ for this repo — eagerworks/skills. Use when a change makes a real judgment call with a defensible alternative that the code alone won't explain (a skill's output contract, where it writes, a naming/config convention, a workflow it deliberately deviates from a precedent on), when the user asks to "record this decision" or "write an ADR", or when landing a non-obvious choice in this collection. Repo-internal tooling — not shipped to skills.sh users.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
mobile-store-review
Audits a mobile app codebase — Expo/React Native (managed or bare) or native iOS/Android, standalone or inside a Turborepo/monorepo — and reports whether it would pass Apple App Review and Google Play review. Use this skill whenever the user: asks if their app will pass, fail, or get rejected by Apple or Google review; is preparing an App Store or Play Store submission; got a rejection email or resolution center message citing a guideline or policy; is filling out the App Privacy questionnaire or Play Data safety form; is auditing permissions, usage descriptions, a privacy manifest, or account-deletion flow; mentions App Review Guidelines, Play Developer Program Policies, TestFlight, `eas submit`, App Store Connect, or Play Console; or is doing a pre-submission or release-readiness check on a mobile app. Also use when the user says things like "will this get rejected?", "audit my app before I ship it", or "review my app for the stores" — even if they don't name a specific guideline.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.