Agent skills for engineering, writing and design work, in one repo that installs on omp, Claude Code, Codex, Cursor and pi. It holds:
- Matt Pocock's skills, vendored unchanged.
- Lauren Tan's pstack and Cursor's cursor-team-kit skills, rewritten so they run outside Cursor.
- Corey Haines' marketing skills, Vercel's agent skills, Effect's Effect skills, supermemory's svg-animations, 0xpili's simplified-technical-english, Boris Tane's logging-best-practices, Emil Kowalski's design, motion and Swift skills, Ayoub Ghriss' i-have-adhd and Dan McAteer's be-ambitious, vendored unchanged.
- Our own skills, distilled from day-to-day work.
A weekly job pulls upstream changes into a pull request, so vendored skills stay current.
Every skill:
npx skills@latest add anis-dr/skillsOne skill:
npx skills@latest add anis-dr/skills --skill <name>Add -g to install into your user folder instead of the current project. Not sure which skill fits? Run /ask-anis: it maps every skill here and how they connect.
User-invoked
- architect: Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
- arena: Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
- ask-anis: Find the right skill or workflow
- automate-me: Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works.
- blast-radius: Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up.
- correct: Find the mistakes agents keep repeating in this repo and make each one impossible.
- create-formal-verification-skill: Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits.
- create-verification-skill: Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
- effect-v3-to-v4: Use this skill when migrating a codebase from Effect v3 to Effect v4, upgrading
effector any@effect/*package across the v3/v4 boundary. - eval: Blind test a skill or prompt change across models
- grill-with-docs: Grill a design and write its docs
- implement: Build work from a spec or tickets
- implement-spec: Implement the result of /to-spec and /to-tickets in code.
- improve-codebase-architecture: Find and grill architecture improvements
- interrogate: Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
- maintain-formal-verification-skill: Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code.
- maintain-verification-skill: Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections.
- no-comments: Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
- recall: Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief.
- reflect: Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill.
- retro: Conduct a retrospective on a coding session.
- setup-matt-pocock-skills: Configure a repo for the skills
- sharpen: Make a task deeper, not bigger, then rewrite the prompt.
- statechart: Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart.
- swarm: Fan out N parallel workers, drain them, and return one report.
- to-spec: Turn a conversation into a spec
- to-tickets: Split a plan into tracer-bullet tickets
- triage: Move issues through triage roles
- wayfinder: Map a large effort as decision tickets
Model-invoked
- agent-sources: Read a dependency's source at the installed version
- anti-slop-migration: Fix anti-slop lint findings without type laundering
- autonomous-run: Drive a long task to a checkable exit predicate
- avoid-feature-creep: Keep scope tight: MVPs, backlogs, one-more-feature
- babysit: Drive a GitHub PR or stack to merge-ready
- benchmark-checklist: Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it.
- bun-monorepo: Bun catalogs, patches and Changesets publishing
- code-review: Review a diff on standards and spec
- codebase-design: Vocabulary for deep-module design
- control-cli: Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services.
- control-ui: Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.
- dependabot-backlog: Merge a Dependabot backlog into one verified PR
- deploy-to-vercel: Deploy applications and websites to Vercel.
- deslop: Remove AI-generated code slop and clean up code style
- diagnosing-bugs: Diagnose hard bugs and regressions
- domain-modeling: Build and sharpen a domain model
- drizzle-postgres: Drizzle bulk params, migration merges, baselines
- effect-ts: Use this skill when setting up a repository that uses the Effect Typescript library.
- estimate: Ranged, calibrated estimates for agent runs, tickets and quotes
- file-structure: Place, name and tidy files so the tree explains the code
- git-split-amended-followup: Split an amended fix into its own follow-up commit
- how: Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer").
- likec4-postcss-isolation: Stop root PostCSS config breaking likec4 serve
- logging-best-practices: Logging best practices focused on wide events (canonical log lines) for powerful debugging and analytics
- make-pr-easy-to-review: Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
- modern-web-guidance: Search tool for modern web development best practices.
- omp-session-retro: Retro over many sessions and harnesses
- orca: Verify UI and hand off tickets inside Orca
- parallel-branches: Parallel subagents in one worktree to a gh stack
- pause-resume: Pause work safely or pick up a prior session
- performance: Trace, fix and hillclimb against a measured baseline
- pr: Write a PR body that's fast to review
- pr-size-breakdown: Honest LOC breakdown for a large GitHub PR
- pragmatic-effect: Keep Effect code simple and practical
- principles: Engineering principles, one per decision
- prototype: Prototype to answer a design question
- query-timeout-diagnosis: Query timeouts while the database is healthy
- rds-snapshot-dump: Portable pg_dump from an RDS Postgres snapshot
- research: Research from high-trust sources
- setup-effect-toolchain: Set up tsgo, Oxlint and oxfmt for Effect repos
- show-me-your-work: Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).
- spec-port-diverged-branch: Port a commit across diverged branches as a spec
- stacked-prs: Create, verify and unblock GitHub stacked PRs
- tanstack-start-middleware: Server-only imports in TanStack Start middleware
- tdd: Test-driven red-green-refactor
- to-plan: Executor-ready plans as flows, not pasted code
- transcripts: Find session transcripts per harness
- typescript-best-practices: TypeScript best practices.
- typescript-library: Library APIs that infer end to end and reject misuse
- vercel-cli-with-tokens: Deploy and manage projects on Vercel using token-based authentication.
- vercel-composition-patterns: React composition patterns that scale.
- vercel-optimize: Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps.
- vercel-react-best-practices: React and Next.js performance optimization guidelines from Vercel Engineering.
- vercel-react-native-skills: React Native and Expo best practices for building performant mobile apps.
- vercel-react-view-transitions: Guide for implementing smooth, native-feeling animations using React's View Transition API (
<ViewTransition>component,addTransitionType, and CSS view transition pseudo-elements). - verify-api-shape: Check live API responses before trusting fixtures
- verify-this: Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
- wayfinder-reversal: Handle wayfinder reversals and close the map
- why: Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
- wizard: Generate an interactive setup wizard
- write-swift: How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors, task groups), protocols and generics (some vs any), API design, performance and ARC, Swift Testing, macros, and the modern language features agents don't know about yet.
User-invoked
- grill-me: Sharpen a plan through interview
- handoff: Compact a conversation into a handoff
- i-have-adhd: Action-first output for ADHD readers
- ketchup: Catch the user up on what changed in this chat since their last message, in plain words and small visuals.
- ketchup-video: Catch the user up like /ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it.
- teach: Learn a concept in a guided workspace
- to-questionnaire: Front-load questions into a doc for someone to answer
- wait-what: Re-pitch that: simpler, with the context I'm missing
Model-invoked
- be-ambitious: Turn a task or prompt into a deeper version of itself, not a bigger one.
- checkbox-picker: Bulk keep/delete choices in a local picker
- diagram-rules: Judgement for any diagram, before the tool
- grilling: Stress-test thinking a round of questions at a time
- humanizer: Make AI-written text sound like the writer
- macos-uninstall: Remove a macOS app and all its leftovers
- scratchpad: Where files go; temp files you can read and edit
- show-me: Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
- simplified-technical-english: Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation.
- technical-html: Markdown docs built into styled HTML pages
- technical-pdf: Typst technical PDFs with verified layout
- technical-writing: Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax.
- trademark-search: Search trademark registers through TMview
- unslop: Cut AI tells from any writing.
- vscode-theme-to-zed: Port a VS Code color theme to Zed
- writing-for-agents: Write documents agents consume
- writing-guidelines: Review docs/prose for Writing Guidelines compliance.
User-invoked
- learn-taste: Turn a session's design corrections into rules, with their why, in DESIGN.md, a project skill, or a lint check.
- pick-ui-library: Pick the library for a frontend task from a curated list — primitives, toasts, drawers, command menus, OTP, numbers, charts, virtualization, drag and drop, state, styling.
- review-animations: Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy.
Model-invoked
- animate: Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits.
- animate-expo: Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades.
- animation-performance: Keep web animations inside the frame budget — animate composite-only properties, keep motion off the main thread when the page is busy, and find the cause when an animation drops frames.
- animation-vocabulary: Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding).
- app-ux: App screen rules for click cost, states and generated-UI tells
- apple-design: Apple's approach to interface design and fluid, physical motion, translated for the web.
- ask-sonner: Guide to Sonner, the React toast library — install and wire up the Toaster, pick the right toast() call, promise and loading toasts, updating, dismissing and persisting toasts, styling, theming and icons, positioning and multiple toasters.
- break-ui: Try to break a piece of UI by feeding it worst-case data — long names, unbreakable emails, one-letter names, missing fields, huge counts, zero items, long labels, non-Latin text, emoji, extreme numbers — then render it behind a "Demo data / Worst case" toggle and report everything that broke, with the fix for each.
- choreograph: Coordinate several elements that animate together — decide what moves, in what order, how much they overlap, and what stays still — so a group reads as one intentional motion instead of a pile of separate animations.
- design-references: Mobbin references as a catalog to pick from
- emil-design-eng: Emil Kowalski's design-engineering philosophy for UI polish, component design, animation decisions, and the invisible details that make software feel great.
- find-animation-opportunities: Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't.
- gestures: Build drag, swipe, and sheet interactions that track the finger 1:1 and stay interruptible.
- improve-animations: Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute.
- logo-surface-board: Judge logo marks on favicon, tile and nav
- measure-ui: Prove UI fidelity and states by measuring
- mobile-native: Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed.
- pen-dev: Design, gate and migrate tokens in pen.dev files
- redesign-inventory: Redesign a UI without dropping any control
- refactoring-ui: Refactoring UI rules, scales and review checklist
- remove-animations: Find the animations an interface doesn't need and remove them — motion on keyboard actions, high-frequency surfaces, functional data, and decoration with no purpose — then clean up what they leave behind.
- svg-animations: Create beautiful, performant SVG animations and illustrations.
- web-design-guidelines: Review UI code for Web Interface Guidelines compliance.
User-invoked
- loop-me: Spec the workflows you want to build
- setup-ts-deep-modules: Enforce deep TypeScript modules
- software-factory: Shared language for designing a software factory: the tasks it runs and the services it plugs into.
- writing-beats: Assemble raw material into beats
- writing-fragments: Mine raw writing fragments
- writing-shape: Shape raw material into an article
Model-invoked
- youtube-video-to-skill: Turn a video tutorial into a skill with frames
Model-invoked
- ab-testing: When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
- ad-creative: When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
- ads: When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms.
- ai-seo: When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.
- analytics: When the user wants to set up, improve, or audit analytics tracking and measurement.
- aso: When the user wants to audit or optimize an App Store or Google Play listing.
- attribution: When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools.
- churn-prevention: When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.
- co-marketing: When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
- cold-email: Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.
- community-marketing: Build and leverage online communities to drive product growth and brand loyalty.
- competitor-profiling: When the user wants to research, profile, or analyze competitors from their URLs.
- competitors: When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use.
- content-strategy: When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover.
- copy-editing: When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content.
- copywriting: When the user wants to write, rewrite, or improve marketing copy for any page, including homepage, landing pages, pricing pages, feature pages, about pages, or product pages.
- cro: When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.
- customer-research: When the user wants to conduct, analyze, or synthesize customer research.
- directory-submissions: When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.
- emails: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
- events: When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.
- free-tools: When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness.
- image: When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets.
- influencer-marketing: When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI.
- launch: When the user wants to plan a product launch, feature announcement, or release strategy.
- lead-magnets: When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation.
- marketing-council: When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more).
- marketing-ideas: When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.
- marketing-loops: When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task.
- marketing-plan: When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
- marketing-psychology: When the user wants to apply psychological principles, mental models, or behavioral science to marketing.
- offers: When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure.
- onboarding: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.
- paywalls: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
- popups: When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes.
- pricing: When the user wants help with pricing decisions, packaging, or monetization strategy.
- product-marketing: When the user wants to create or update their product marketing context document.
- programmatic-seo: When the user wants to create SEO-driven pages at scale using templates and data.
- prospecting: When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
- public-relations: When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests).
- referrals: When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
- reverse-engineer-marketing: When the user wants to reverse engineer how another company grew and copy what worked.
- revops: When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.
- sales-enablement: When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts.
- schema: When the user wants to add, fix, or optimize schema markup and structured data on their site.
- seo-audit: When the user wants to audit, review, or diagnose SEO issues on their site.
- signup: When the user wants to optimize signup, registration, account creation, or trial activation flows.
- site-architecture: When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
- sms: When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS.
- social: When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
- video: When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks.
Model-invoked
- git-guardrails-claude-code: Block dangerous git commands
- migrate-to-shoehorn: Replace test assertions with shoehorn
- scaffold-exercises: Scaffold lint-ready course exercises
- setup-pre-commit: Add pre-commit quality checks
bun install, then:
| Command | What it does |
|---|---|
bun run skills sync |
Rebuilds every vendored skill from its pinned upstream commit, then applies the agent-neutral rules and patches. |
bun run skills sync --report |
Writes upstream/DRIFT.md: upstream commits since each pin, and upstream skills and subagents nothing tracks. |
bun run skills sync --update |
Moves vendored skills to upstream HEAD and writes the report. |
bun run skills patch <name> |
Saves hand edits to a vendored skill or agent as its patch. |
bun run skills check |
Checks frontmatter, invocation, skill calls, banned terms, the router and this README. |
bun run skills readme |
Regenerates the skill list above. |
Subagent definitions vendored from upstream live in agents/<name>.md. An entry with "mode": "agent" in upstream/sources.json names the upstream Markdown file, and sync builds it like a vendored skill: the agent-neutral rules, then upstream/patches/<name>.patch. The drift report lists every upstream skill and subagent that no entry tracks; to leave one out on purpose, add it to upstream/ignored.json with a reason.
CONVENTIONS.md says how a skill here is written. Upstream sources and licenses are in NOTICE.md.