πŸͺ

aaronkendell/skills-marketplace

πŸͺMarketplace

aaronkendell/skills-marketplace

Add this Marketplace

Add marketplace in Claude Code:
$/plugin marketplace add aaronkendell/skills-marketplace
31Plugins
0
Last UpdatedAug 29, 2026

Plugins in this Marketplace

πŸ”Œ

app-store-connect

App Store Connect automation β€” build lifecycle, TestFlight orchestration, release flow, signing, metadata and localisation, screenshots, pricing, crash triage and submission health. Apple publishes no agent skills, so this fills the gap for golf and keepings.

0
πŸ”Œ

apple-dev

Apple platform development β€” SwiftUI, SwiftData, iOS, macOS, watchOS, visionOS, Core ML, Apple Intelligence, MapKit, testing, performance and release review. Broader than App Store Connect: this is writing the app, that is shipping it.

0
πŸ”Œ

auth-skills

Better Auth agent skills: create-auth scaffolding + best practices. Better Auth is a stack non-negotiable.

0
πŸ”Œ

cloudflare

Cloudflare's own skills for Workers, KV, R2, D1, Durable Objects and the rest of the platform. The mcp-gateway itself is a Worker, so these cover the thing that hosts everything else. Preferred over the Cloudflare MCP connector, which reaches ~2,500 API endpoints and carries the schema on every request.

0
πŸ”Œ

dev

Full SDLC: research β†’ plan β†’ build β†’ ship. Linear integration, TDD, automated testing, code review. Includes the workspace, design, and copy (voice/microcopy) skills.

0
πŸ”Œ

expo

Expo skills: app design, deployment/EAS, upgrades, router, native UI. Upstream exposes expo-app-design / expo-deployment / upgrading-expo as aliases of this one plugin.

0
πŸ”Œ

fly

Fly.io's own skills repo. Only `sprites` today β€” no flyctl ops skill upstream, which is why the local `fly-ops` skill in the skills plugin covers deploys, machines, logs and token scoping. Watch this for an official one.

0
πŸ”Œ

grafana

Official Grafana Labs skills for Grafana, Prometheus, Loki, Tempo and the wider LGTM stack. Upstream is itself a marketplace of several plugins rather than one, so each skill directory is listed explicitly and strict makes this list authoritative.

0
πŸ”Œ

huashu-design

θŠ±ε”Design β€” HTML-native high-fidelity prototypes, slides, animation, data viz and expert review (23k stars). Single-skill repo: SKILL.md sits at the root rather than under skills/, so the skill path is the repo root. Was loose in ~/.claude/skills, meaning one laptop had it and no worktree or cloud agent did.

0
πŸ”Œ

impeccable

Design finishing workflow: direction contract -> approved comp -> build -> finish review, with asset-producer/documenter/reviewer sub-agents. Required by dev:design.

0
πŸ”Œ

infisical

Infisical's own skills β€” setup, API, app connections, secret syncs, dynamic secrets, rotation, access control, SSO, PKI, KMS and the Kubernetes operator. Every credential in this workspace comes from Infisical, so this is the one vendor whose skills touch every task.

0
πŸ”Œ

inngest

Inngest's official Claude Code plugin β€” setup, events, durable functions, steps, flow control, middleware, realtime, plus a brownfield audit and the v3β†’v4 migration. It also wires MCP for the LOCAL dev server at 127.0.0.1:8288, which only resolves while `inngest dev` is running in the same sandbox; in a cloud agent start the dev server first or the connection simply fails, harmlessly.

0
πŸ”Œ

langfuse

Official Langfuse skills β€” tracing, prompt management, datasets and evaluation for the LLM work in golf/hive/portfolio. Pairs with the langfuse/* routes on mcp.bokendell.com, which are the only way Claude can reach Langfuse's MCP server at all (it takes HTTP Basic, and claude.ai connectors accept OAuth only).

0
πŸ”Œ

mcp-pack

Bundle of MCP servers (Neon, Grafana, Mapbox docs+DevKit, Proxyman) that follow you across every repo and superset worktree when enabled at user scope. Secrets via shell env vars.

0
πŸ”Œ

motion

Design taste and motion craft β€” animation vocabulary, Apple interface/motion principles, Emil Kowalski's polish philosophy, and the animation audit/review pair. Previously loose in ~/.claude/skills, so present on one laptop and nowhere else.

0
πŸ”Œ

neon

Neon's own skills β€” Postgres, branching workflows, the egress optimizer, plus Functions, Object Storage and AI Gateway. Supersedes the local skills:neon-postgres for anything Neon-specific.

0
πŸ”Œ

openrouter

OpenRouter's own skills β€” models, generations, analytics, OAuth, the TypeScript SDK, and speech/image/video endpoints. Credentials at /infrastructure/openrouter.

0
πŸ”Œ

ponytail

External overengineering/debt pressure skill. Use as a signal for skill-watch and review; bokendell DDD/API/mobile/design standards remain owned by the local dev and skill-watch plugins.

0
πŸ”Œ

posthog

PostHog's own skills. Marked under construction upstream, so treat it as a moving target; golf and portfolio both use PostHog and its credentials sit at /infrastructure/posthog.

0
πŸ”Œ

proxyman

Proxyman's official skills β€” install and setup, app settings, certificate lifecycle and recovery, HTTPS capture across devices and runtimes, the debugging tools (breakpoints, map local/remote, scripting, reverse proxy), licensing, and proxyman-cli. Note that unlike most vendors here the CLI does NOT replace the MCP: it covers proxy config, rules, certificates and logs, while live traffic inspection stays an MCP surface, which is why mcp-pack keeps the Proxyman server.

0
πŸ”Œ

resend

Resend's own skills: the API skill, resend-cli, react-email (which is what we send with), email-best-practices, and the agent email inbox. Preferred over the Resend MCP connector, which is 99 tools and ~33k tokens of schema on every request whether or not an email is sent.

0
πŸ”Œ

revenuecat

RevenueCat's own AI toolkit: subscription setup, SDK integration, paywalls, purchase and restore flows, entitlement gating, testing, troubleshooting, charts and experiment analysis. NOTE β€” this plugin also ships a .mcp.json pointing at https://mcp.revenuecat.ai/mcp; the skills are the reason to install it, and the connector can be left disabled.

0
πŸ”Œ

revenuecat-play-billing

RevenueCat's Google Play billing skills β€” subscription lifecycle, plan and price changes, payment recovery, webhooks and security. Only relevant to the Android side of golf and keepings.

0
πŸ”Œ

rive-interactive

Rive interactive animation skill. Rive is in golf's real asset pipeline (assets:plates, the rive MCP) β€” the other four motion plugins were dropped 2026-08-27.

0
πŸ”Œ

sentry

Sentry's own engineering skills β€” code review, find-bugs, commit and branch helpers, Django perf/access review. Not Sentry-product-specific, so it is useful beyond the sentry/* gateway routes; strict keeps this list authoritative against upstream churn.

0
πŸ”Œ

session-bridge

Inspect, resume, and hand off agent sessions across Codex CLI and Claude Code. `session-bridge` CLI reads both session stores; resume-session (read) + handoff-session (switch tools) skills.

0
πŸ”Œ

skill-watch

Claude Code + Codex hook loop for skill activation, standards drift, swarm/arch-check review signals, and reviewable auto-rewrites into this marketplace working tree.

0
πŸ”Œ

skills

Cross-cutting skill bundle: framework references, AI tooling, GitHub helpers, code/docs review, Expo helpers.

0
πŸ”Œ

taste

Premium frontend design taste β€” sourced live from Leonxlnx/taste-skill. strict:true because upstream's plugin.json also declares components; with strict, this entry's `skills` list is authoritative and the two stop conflicting. `skills` must list each skill DIRECTORY (one containing a SKILL.md) β€” pointing at the bare ./skills container registers ZERO skills. taste-skill-v1 is deliberately excluded: upstream keeps it only for projects pinned to its exact old behaviour, and carrying both means two skills competing to answer the same request.

0
πŸ”Œ

ui-ux-pro-max

UI/UX reference database: styles, palettes, font pairings, product types, UX guidelines, chart types across 22 stacks. Required by dev:design as the heuristics layer.

0
πŸ”Œ

upstash

Upstash's own skills β€” Redis, QStash, Workflow, Vector, Search and the CLI. Every product here uses Upstash; credentials are at /infrastructure/upstash in each Infisical project.

0