Agent Plugins Marketplace

Recently added

Plugins grouped by the day they were added to the directory, newest first.

Sep 15, 2026

  1. Grok Bot delegation SOP for Chief of Staff — on every Matthew ask: match or create purpose-built expert bots (via grok-bot-creation), port or upstream RavenClaude skills, SendToAgent with a tight brief, then coordinate; escalate to Matthew only for decisions, auth, or irreversible actions. Also carries the fleet token-spend playbook: condensed returns, an effort ladder before spawn, routine hygiene, connectors over browser, CPCT measurement. Distinct from ravenclaude-core Team Lead orchestration (Claude Code) and ai-agent-engineering (building agentic products). Requires ravenclaude-core@>=0.7.0.

    Claude Code
  2. Grok Bot creation specialist — design token-efficient, mostly autonomous Grok Bot personas (CreateAgent / UpdateAgent) with statistically insignificant quality loss: create checklist, gold description template, safe token hygiene, and the recipe for upstreaming net-new skills into RavenClaude via GitHub Sage. Distinct from ai-agent-engineering (building production agentic systems / frameworks) and ravenclaude-core (Claude Code orchestration). Requires ravenclaude-core@>=0.7.0.

    Claude Code
  3. GraphQL-engineering team — agents (graphql-schema-architect, graphql-server-engineer, graphql-security-governance-engineer) for the three engines of a GraphQL surface: schema design & evolution (client-driven type modeling, nullability, Relay pagination, mutation/error shape, schema-first vs code-first, federation vs stitching, non-breaking evolution), server & resolvers (N+1/DataLoader batching + per-request caching, selection-set-aware fetching, subscriptions, APQ/response caching), and security & governance (query cost/depth budgets, field-level authz, persisted operations, introspection hardening, rate/batch limits, error hygiene). Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Engineering judgment, not a security certification; library/federation/spec-feature specifics are volatile — every version carries a retrieval date + [verify-at-use]; no PII. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  4. Graph-engineering team — agents (graph-data-modeler, graph-query-engineer) for property-graph and RDF craft: when a graph beats relational, LPG vs RDF, labeled/typed modeling, supernodes, Cypher/ISO GQL/openCypher/Gremlin/SPARQL traversals, and GraphRAG construction (skill + command, not a dedicated agent). skills, commands, knowledge files (graph-vs-relational tree, LPG catalog, dated 2026 language/engine map, GraphRAG construction), best-practices, templates, scenarios, an advisory hook, a stdlib shape linter. Advisory only — snippets the user runs; no live graph runtime. Seams: when NOT a graph → database-engineering; vector/hybrid RAG → ai-rag-engineering; whether a memory graph beats BM25 → memory-engineering; GraphQL → graphql-engineering; Microsoft Graph API → microsoft-graph; Fabric Graph SKU → microsoft-fabric. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  5. Grantee-side grants-management team — agents (grants-strategy-lead, grants-compliance-and-reporting-specialist) for the full grant lifecycle: pre-award PIPELINE & STRATEGY (prospect research + funder fit 'fit-before-effort', go/no-go, logic model, needs statement, SMART objectives, evaluation plan, budget narrative, LOI→full-proposal assembly) and post-award COMPLIANCE & REPORTING (2 CFR 200 cost principles, indirect rates / NICRA / de minimis, time & effort, procurement, SF-425 FFR + RPPR, subrecipient-vs-contractor determination & monitoring, Single Audit, closeout). Fluent in federal mechanics (SAM.gov, Grants.gov, SF-424 family, UEI) and grants systems (Fluxx, Submittable, Instrumentl). skills, a knowledge bank + templates. NOT individual/major-donor fundraising (nonprofit-fundraising), NOT grantmaking policy design (public-sector-govtech), NOT general bookkeeping (accounting-bookkeeping). Not legal/accounting advice. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  6. Geospatial / GIS engineering team — agents. The geospatial-data-engineer owns spatial data modeling and storage (PostGIS, GiST/SP-GiST indexes, SRID/projection hygiene — EPSG:4326 vs 3857, geometry vs geography), spatial SQL and analysis (ST_ functions, joins, nearest-neighbor, buffers), spatial data quality (validity, validate-at-load), and pipelines (GDAL/OGR, geocoding, routing like OSRM/Valhalla). The mapping-visualization-engineer owns serving and visualization (vector tiles/MVT, pg_tileserv/Martin/Tegola, MapLibre/Mapbox GL styling, the GeoJSON-vs-vector-tile tradeoff). skills, projection + storage/serving decision trees, a dated 2026 stack reference, templates, best-practices, an advisory hook (checks). Seams: warehouse/ELT → data-platform; OLTP → database-engineering; map UI → frontend-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  7. AI multimedia for brand & winery sites: a creative brief -> on-brand, web-optimized, license-clean images/video/3D/audio behind a mandatory human curation gate. agents (generation-strategist, web-asset-pipeline-engineer, asset-provenance-guardian, brand-and-accessibility-reviewer) route a brief to the right generator (provider-neutral, Grok-lean for images where competitive; inpaint/outpaint/bg-removal/upscale first-class), turn raw output into AVIF/WebP responsive <picture> markup with LCP/CLS-safe embeds, pin commercial-use licenses (flags the FLUX-dev non-commercial trap; C2PA + a provenance ledger; EU AI Act Art.50 disclosure), and gate every asset on brand-hex/style conformance + WCAG alt text before ship. skills, knowledge docs (Mermaid decision trees; all prices [unverified]), best-practices, commands, templates, scripts. The shared foundation the brand-identity-studio plugin consumes. Declarative fal MCP binding (set FAL_KEY). Requires ravenclaude-core@>=0.7.0.

    Claude Code6 skills1 MCP server
  8. gcp-cloud7stars

    Google Cloud (GCP) infrastructure & platform team — agents (gcp-architect, gcp-iam-engineer, gcp-network-engineer, gcp-data-and-compute-engineer) for the GCP layer of a stack: the resource hierarchy (organization/folders/projects) and org policy constraints, least-privilege IAM (predefined over primitive roles, service accounts + Workload Identity Federation, no key files), VPC networking (Shared VPC, firewall rules, Private Service Connect, Cloud NAT), compute selection (Cloud Run / GKE / Cloud Functions / GCE), and the data services (BigQuery, Pub/Sub, Cloud SQL) at a selection level. skills, a decision-tree knowledge bank (compute-selection + project-hierarchy trees + a dated 2026 capability map), best-practices, templates, commands, an advisory hook. Multi-cloud seam to aws-cloud/azure-cloud; IaC -> terraform-iac; BigQuery analytics -> data-platform; security verdicts -> ravenclaude-core/security-reviewer. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  9. Game Development specialist team — agents (gamedev-producer, game-designer, gameplay-engineer, live-ops-analyst), skills, templates, commands, an advisory hook, best-practice rules, a research-grounded knowledge bank with Mermaid decision trees (production/design/live-ops + runtime-performance frame/GC/draw-call/memory budgets + engine-selection/ECS-vs-OOP/networking-model), a scenarios bank (frame-time GC hitch, draw-call batching, netcode rollback, save-system migration), a stdlib frame/CPU-GPU/memory budget calculator (scripts/gamedev_budget.py), and a bundled C# (Roslyn, stdio) LSP config. Scopes to a vertical slice, designs core loops and economies that retain, runs production on milestones and risk burn-down, reads live-ops on retention/monetization, and diagnoses frame-budget/draw-call/netcode/save-migration problems. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  10. Funeral-home & deathcare operations team — grief-aware agents for a funeral director, owner, or manager. `funeral-operations-lead` runs the business: case flow (first call → removal → arrangement → preparation → services → billing → aftercare), staffing & on-call, capacity, pre-need, aftercare, and margins. `funeral-arrangement-and-compliance-specialist` owns the arrangement conference and the FTC Funeral Rule: General/Casket/Outer-Burial-Container price lists, itemization, telephone-price and embalming-not-required disclosures, cremation authorization & chain-of-custody, vital records, and permits across burial, cremation, aquamation, and green burial. skills, a knowledge bank (Mermaid compliance decision tree + 2026 operations patterns), templates. Not cemetery interment (out of scope), not clinical grief therapy (behavioral-health-practice), not bookkeeping (accounting-bookkeeping). Requires ravenclaude-core@>=0.7.0. Not legal advice — deathcare law varies by state/country.

    Claude Code3 skills
  11. Frontend-engineering team — agents (frontend-architect, react-implementation-engineer, frontend-state-and-data-engineer, frontend-performance-engineer) for building app-grade frontends (React/Next, TypeScript): component architecture and composition, the rendering-strategy choice (CSR/SSR/SSG/ISR/React Server Components), client state vs server-cache (TanStack Query/RSC) and form/validation, bundle/performance discipline (code-splitting, Core Web Vitals, hydration cost), and accessibility-in-code (semantic HTML, ARIA, keyboard, focus). TypeScript-first. skills, a decision-tree knowledge bank (rendering-strategy + state-location trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Distinct from web-design (brand/UX/marketing sites). Seams: design/brand/WCAG-audit -> web-design, auth UX -> auth-identity, API consumption -> api-engineering, native -> mobile-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  12. International freight-forwarding sales team — specialist agents (freight-rate-quoter, rfq-tender-strategist, key-account-manager, pipeline-forecast-coach, prospecting-outreach-strategist, trade-lane-compliance-advisor) for the day-to-day of a global-forwarding sales / business-development manager: building accurate all-in ocean + air quotes (chargeable weight, BAF/CAF/THC/LSS surcharges, margin), responding to RFQs/RFPs/tenders, running QBRs and account plans, keeping the CRM pipeline and forecast honest, prospecting shippers multi-channel, and getting Incoterms 2020 + customs basics right. skills, slash commands, a knowledge bank with Mermaid decision trees (mode, quote-vs-qualify, Incoterms, spot-vs-contract, rate-objection, account-risk, prospect-pursuit, quote-delivery, LCL-vs-FCL, deadline mode-shift), a scenarios bank, and a runnable chargeable-weight / quote-margin calculator. Carrier-neutral — any forwarder or 3PL. Inherits ravenclaude-core protocols.

    Claude Code6 skills
  13. Franchise operations team — agents (franchise-operations-strategist, multi-unit-performance-manager) across the two halves of a franchise business: the system economics & relationship (reading the FDD and Item-19 FPR for what it does/doesn't say, royalty + ad-fund + fee flows, the royalty-loaded unit-economics model, the new-unit / expand go/no-go, the franchisor<->franchisee contract) and running the units (multi-unit P&L, prime-cost control, brand-standard audits, manager scorecards, unit-variance ranking). skills, a decision-tree knowledge bank (a new-unit go/no-go Mermaid tree + a dated 2026 franchise-economics reference), best-practices. Business decision-support, NOT legal/financial/investment advice; binding FDD/agreement review -> legal-ops-clm; fees + Item-19 figures are per-FDD-edition, jurisdictional + volatile — retrieval-dated + verify-at-use. Seams: restaurant-operations, retail-store-operations, field-service-management, finance. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  14. Forms engineering — the seam between how a form is built, how the request stream behind it is run, and where its trust boundary sits. Owns what no other plugin does: intake taxonomy and triage routing that make a request stream deterministic; the form measurement contract (which events, which denominator, what counts as a defect) and its hand-off to statistical process control; the server half of a submission that web-design routes out by rule (client/server validation parity, honeypot design and its assistive-tech exemption, double-submit and submission idempotency, webhook signature verification, PII minimisation); and form-platform selection on durable axes rather than a feature matrix. Client-side form construction and form accessibility stay with web-design. Upload hardening and challenge-widget mechanics stay with ravenclaude-core, which this plugin cites rather than restates, and every binding security verdict routes to ravenclaude-core/security-reviewer. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  15. Fleet & Logistics specialist team — agents (fleet-engagement-lead, dispatch-routing-specialist, fleet-maintenance-specialist, logistics-cost-analyst), skills, templates, commands, an advisory hook, best-practice rules, a research-grounded knowledge bank with Mermaid decision trees (lane-thin, replacement-timing, spot-vs-contract, lease-vs-buy-vs-rent, private-fleet-vs-3PL), a scenarios bank, and a stdlib calculator (cost-per-mile, deadhead, replace-vs-repair, driver-turnover). A fleet-operations team for a carrier, private fleet, or last-mile operator — it reads cost-per-mile against the ~$2.26 industry all-in (and the ~$1.78 non-fuel marginal), manages the operating ratio in a market that turned negative-margin in 2024, routes to deadhead and utilization, and treats driver turnover (often 90%+ at large truckload carriers) as a unit-economics problem. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  16. Gym / boutique-fitness-studio operations team — agents (fitness-studio-operations-lead, membership-retention-manager, class-schedule-coach-ops) for the three engines of a fitness business: the membership P&L (growth, churn/retention, member LTV, utilization, ancillary revenue from PT, retail, and café), the retention machine (onboarding, attendance triggers, churn prediction and saves, win-back, referral, pricing/tiers), and the class grid (scheduling on demand, instructor utilization and pay, capacity/fill, waitlist, no-show, sub coverage). ADVISORY operations knowledge, not legal/financial/medical advice; volatile specifics (churn norms, LTV math, class-fill and instructor-pay benchmarks) carry a retrieval date + verify-at-use; no member PII. Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Seams to retail-store-operations, restaurant-operations, and people-operations-hr. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  17. Fintech & payments-engineering team — agents (payments-architect, payments-integration-engineer, billing-subscriptions-engineer, payments-pci-compliance-advisor) for building payment + billing systems that don't lose or duplicate money: payment-flow architecture (PSP choice, money-as-integer, the double-entry ledger, reconciliation), payment integration (Stripe-style intents, idempotency keys, webhook verification + idempotent handling, 3DS/SCA, retries/dunning), subscription & usage billing (plans, proration, metering, invoicing, revenue events), and PCI-DSS scope minimization (tokenization, never touch raw PAN, SAQ-A posture). The ENGINEERING — accounting/GL routes to finance, financial regulation to regulatory-compliance, security verdicts to ravenclaude-core. skills, a decision-tree knowledge bank (charge-flow + PCI-scope trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  18. FinOps & Cloud Cost specialist team — agents (finops-lead, cost-allocation-analyst, commitment-planning-specialist, unit-economics-strategist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A FinOps team for a cost lead or eng-finance partner accountable for cloud spend and unit economics — it allocates spend before optimizing it, reads unit economics over the total bill, treats commitments as a portfolio decision made after rightsizing, and kills waste first. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  19. finance7stars

    Corporate finance & FP&A specialist team — FP&A analyst, financial modeler, controller, treasury analyst, valuation analyst, audit-prep specialist, and board-pack composer. Ships skills including the controller-autopilot: a governed close-to-report cycle (GAAP statements, COA mapping, reconciliation auto-match, review→approve→lock workflow, ELT staging, consolidation, per-entity dashboard, close schedules) plus its live-integration tier (multi-currency remeasurement + CTA, OAuth GL connectors + drill-through lineage, warehouse/RLS dashboard, IdP-backed segregation of duties) and a gold-standard NetSuite close (OAuth2 M2M + SuiteQL BS/IS trial balance, COA-draft, tie-out doctor, changed-after-sign-off drift, layperson runbook). templates, a knowledge bank, and advisory hooks (anti-patterns + secrets/PII scan). Inherits ravenclaude-core protocols (Grounding, Structured Output, Cited-Adjudicator).

    Claude Code23 skills
  20. Film & Video Production specialist team — agents (production-lead, line-producer, post-production-supervisor, production-finance-analyst), skills, templates, commands, an advisory hook, best-practice rules, a research-grounded knowledge bank with Mermaid decision trees, a scenarios bank, and a stdlib production-economics calculator (shoot-day cost, contingency burn, overtime burden). A production-management team for a producer, production company, or post house — it budgets to a defensible top-sheet, schedules to the shoot day rather than the calendar, runs the post pipeline as a dependency chain, and reads production economics the way a line producer who answers for every dollar on the day must. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  21. Field-service management & dispatch operations specialist team — agents covering the service operating model (SLAs, contracts, dispatch-to-cash), dispatch & scheduling (skill/SLA/geo optimization, emergency vs planned), technician productivity (utilization, first-time-fix, MTTR, callbacks), and parts & inventory (truck stock, service-level tradeoffs, returns). Ships skills (dispatch-and-scheduling, technician-productivity-and-first-time-fix, truck-stock-and-parts), commands, templates, best-practices, a decision-tree knowledge bank, and an advisory hook flagging FSM anti-patterns. Domain: HVAC, plumbing, elevator, medical-device service. Inherits ravenclaude-core protocols.

    Claude Code3 skills
  22. Experimentation & growth-engineering team — agents (experimentation-architect, feature-flag-engineer, product-analytics-instrumentation-engineer) for the APPARATUS that lets a team learn fast and ship safely: feature flags + progressive delivery (kill switches, targeting, flag lifecycle/debt), A/B-test plumbing (assignment, exposure logging, SRM checks, sequential-peeking guards, the results read), and trustworthy event instrumentation (a tracking plan, a consistent event schema, identity stitching, a CDP). The engineering of experimentation — statistical VALIDITY (power/MDE, significance) is applied-statistics'. skills, a decision-tree knowledge bank (flag-vs-config + ship-decision trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: significance -> applied-statistics, hypothesis/outcome -> product-management, rollout -> devops-cicd, pipelines -> data-platform. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  23. Event-management team — agents (event-strategist, event-operations-lead, event-marketing-revenue) for planning and running conferences, webinars, and field/community events across in-person, virtual, and hybrid formats: goals/KPIs and the go/no-go gate, format and audience and budget/break-even model, sponsorship strategy and fulfilled-promise delivery, minute-by-minute run-of-show and show-flow, venue/vendor/AV logistics, registration funnel and attendee ops, contingency and single-point-of-failure plan-Bs, promotion and ticketing funnel, and post-event ROI measured against the goal you set. This is the event craft, distinct from generic delivery — schedule/RAID/stakeholder management lives in project-management. skills, a decision-tree knowledge bank (format + break-even + sponsorship-tier + go/no-go trees, plus a dated 2026 tooling/benchmark map), best-practices, templates, commands, an advisory hook. Seams: schedule/RAID -> project-management. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  24. Corporate ESG & sustainability-disclosure team — agents (esg-reporting-architect, ghg-accounting-analyst, disclosure-and-assurance-lead) for the reporting layer that turns sustainability obligations into a defensible, assurable disclosure: framework selection & scoping (CSRD/ESRS, ISSB IFRS S1/S2, GRI, SEC climate rule), double vs financial materiality, the reporting boundary & governance, the disclosure roadmap; GHG Protocol Scopes 1/2/3 (the 15 Scope-3 categories), emission factors, location- vs market-based Scope 2, base year, data quality; and disclosure drafting, evidence trail, limited vs reasonable assurance readiness, gap assessment. Knowledge bank (trees), best-practices, skills, commands, templates, a hook, a stdlib GHG calculator (scope2/inventory/intensity), scenarios. Seams: financial reporting -> finance; data lineage -> data-governance-privacy; filing -> regulatory-compliance. NOT a legal or financial-audit opinion. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  25. Engineering Management specialist team — agents (engineering-manager-lead, people-and-growth-manager, delivery-and-execution-manager, technical-health-manager), skills, commands, templates, an advisory hook, best-practice rules, and a research-grounded knowledge bank. The craft of leading engineers: structured 1:1s, growth frameworks and calibrated performance reviews, hiring loops, team-health signals, and tech-debt-vs-roadmap trade-offs — with DORA used as a health signal, never a stack-rank weapon. Domain-neutral; deepens (does not replace) people-operations-hr and project-management. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  26. Embedded & IoT Engineering specialist team — agents (embedded-systems-lead, firmware-rtos-specialist, power-budget-analyst, connectivity-protocol-specialist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. An embedded team for a firmware lead or hardware founder accountable for a fielded device — it treats the power budget as the spec, holds real-time deadlines as hard constraints, budgets flash/RAM like money, favors determinism over throughput, and requires OTA + rollback before fielding. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  27. Email-engineering team — agents (email-deliverability-architect, email-sending-engineer) for getting legitimate mail to the inbox: domain authentication (SPF, DKIM, DMARC alignment + a staged p=none -> quarantine -> reject rollout, BIMI), transport security (MTA-STS RFC 8461 + TLS-RPT RFC 8460), deliverability (subdomain stream separation, domain/IP warm-up, reputation, Gmail/Yahoo bulk-sender rules), inbox categorization (Gmail tabs, Outlook Focused Inbox, Apple Mail), ESP integration (SES/SendGrid/Postmark/Resend) with idempotent sends + verified webhook handling, MJML templates, and the feedback loop (bounce/complaint classification, ARF, suppression lists, one-click unsubscribe per RFC 8058). skills, a knowledge bank, best-practices, templates, commands, a scenarios bank, a stdlib auth-record linter, and an advisory hook. Seams: strategy -> marketing-operations, infra -> backend-engineering, DNS -> cloud plugins, security -> security-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  28. EdTech-flavored Partner Success Manager team — specialist agents anchored on the PSM lane, with skills, templates, an advisory hook, a knowledge bank with Mermaid decision trees, a engagement bank, and a stdlib psm_calc.py calculator (seat-utilization / renewal-NRR-forecast / time-to-value). Covers QBRs, success plans, health scores, a self-contained Power-BI-style partner-health report, onboarding, touchpoint logs, adoption sequencing, 90-day implementation arcs, train-the-trainer curricula, advocacy/reference pipelines, renewal decision memos, and the integration contract for a centralized CS dashboard (Planhat + Salesforce + Snowflake + Zapier + Granola). Team growth ships as skills + knowledge + templates, not parallel agents. Primary-source citations with retrieval dates. Vertical-explicit but segment-agnostic — fits K-12, higher-ed, corporate L&D, or mixed EdTech books. Inherits ravenclaude-core protocols including the alternate-methods Capability Grounding Protocol.

    Claude Code17 skills
  29. E-commerce & DTC specialist team — agents (ecommerce-lead, merchandising-specialist, performance-marketing-strategist, retention-analytics-analyst), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A growth-and-unit-economics team for a DTC brand operator — it protects the LTV:CAC ratio (the 3:1 line below which a brand bleeds), reads conversion against the 1.4–1.8% average, attacks the retention gap (the average brand keeps just ~28% for a second purchase), and reads contribution margin after the real cost of acquisition and returns. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  30. Digital-twin engineering team — agents (digital-twin-architect, twin-integration-engineer) for the layer answering 'what should this twin MODEL, at what FIDELITY, and does it MATCH the real asset?': twin taxonomy (asset vs process vs system-of-systems; descriptive/predictive/prescriptive; digital-shadow vs true bidirectional), only-as-much-fidelity-as-the-decision-needs, modeling approach (physics vs data-driven/surrogate/reduced-order vs hybrid), telemetry ingestion (MQTT/OPC-UA/Kafka, edge vs cloud), state sync/drift/calibration, simulation & what-if, and fidelity validation. Fluent in DTDL + Azure Digital Twins, ISO 23247, AAS, Eclipse Ditto, NVIDIA Omniverse, Unity/Unreal, Bentley/Siemens. skills, a knowledge bank (decision tree + 2026 patterns), and templates. Distinct from embedded-iot-engineering (device firmware), robotics-autonomous-systems-engineering (robot control/autonomy), and data-platform (BI/warehouse). Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  31. DevOps & CI/CD delivery-pipeline team — agents (pipeline-engineer, release-engineer, gitops-engineer, build-and-artifact-engineer) for the path from commit to production: CI design (stages, caching, matrix, fail-fast, required checks), progressive delivery (blue-green, canary, feature-flagged rollouts, automated rollback), GitOps continuous delivery (Argo CD / Flux, desired-state in Git, drift detection), and build/artifact integrity (reproducible builds, semantic versioning, SBOM, provenance/SLSA, registry hygiene). skills, a decision-tree knowledge bank (deploy-strategy + CI-vs-CD-boundary trees + a dated 2026 tooling map), best-practices, templates, commands, an advisory hook. Seams: IaC -> terraform-iac, clusters -> cloud-native-kubernetes, telemetry/SLOs -> observability-sre, supply-chain verdicts -> ravenclaude-core/security-reviewer. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  32. Developer-tooling team — the BUILD-TOOLING layer for monorepo & build-systems engineering. agents (build-systems-architect, monorepo-engineer) covering monorepo tooling (Nx, Turborepo, Bazel/Buck2, Moon, pnpm/yarn/npm workspaces, Lerna), build performance & remote/content-addressable caching, task graphs and affected/since-only builds, dependency & package management (version policy, lockfile hygiene, renovate/dependabot, supply-chain hygiene: SBOM/provenance/pinning), and code-generation/scaffolding. skills (choose-monorepo-tooling, optimize-build-and-cache, manage-dependencies), Mermaid-backed knowledge docs (monorepo-tooling decision tree, build-caching & performance), and runbook templates. Seams: CI/CD pipelines → devops-cicd; service code → backend/frontend-engineering; containers/IaC → the cloud plugins. House line: measure before you migrate; cache correctness before cache speed. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  33. Developer-relations / DevRel team — agents (developer-advocate, devrel-content-engineer, developer-community-manager) for the developer experience of a product with an API/SDK: time-to-first-success (getting-started) audits, sample-app and SDK-quickstart design, a DX content strategy, conference talks + CFP abstracts, community health, DX metrics (activation funnel), and the product-feedback loop that fixes the product instead of writing around it. skills, a knowledge bank with Mermaid decision trees (advocate-vs-docs-vs-community, fix-the-product-or-document-it, content-format choice), best-practices, templates, commands, and an advisory anti-pattern hook. Distinct from technical-writing-docs (reference docs), marketing-operations (demand gen), and product-management (what to build). Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  34. Desktop-app-engineering team — agents (desktop-architect, electron-engineer, tauri-engineer, desktop-platform-engineer) for cross-platform desktop apps: the Electron-vs-Tauri-vs-native-vs-PWA decision, a hardened process/security model (Electron contextIsolation + IPC allow-lists; Tauri capabilities/permissions + Rust commands), reproducible packaging, code-signing + notarization on Windows and macOS, safe auto-update, and native OS integration (tray, menus, notifications, file associations, deep links, secure on-device storage). skills, a decision-tree knowledge bank (framework-choice + IPC-security trees + a dated 2026 capability map), best-practices, templates, commands, an advisory hook. Seams: renderer UI -> frontend-engineering, the backend/API -> api-engineering/backend-engineering, tokens/OAuth -> auth-identity, signing/notarization in CI -> devops-cicd, the mobile sibling -> mobile-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  35. Design-systems engineering team — agents (design-systems-architect, design-tokens-and-component-engineer) answering 'what is the shared system every product surface builds from, and how is it versioned and adopted?': design-token architecture (primitive → semantic → component tiers, theming/dark-mode/multi-brand), component-library API design (composition vs configuration, controlled/uncontrolled, a11y baked in), Storybook/docs, Figma→code token pipeline (Style Dictionary), and versioning/adoption (semver, changesets, codemod-backed breaking changes, deprecation, governance, adoption metrics). skills, a knowledge bank (a Mermaid decision tree + a dated 2026 tooling reference). Distinct from frontend-engineering (builds apps that CONSUME the system), accessibility-engineering (WCAG compliance), and web-design (site visual design) — this team owns the SYSTEM those build from. Tooling specifics volatile: retrieval-dated + verify-at-use. Needs ravenclaude-core.

    Claude Code3 skills
  36. Dental Practice specialist team — agents (dental-practice-lead, clinical-treatment-planner, dental-rcm-specialist, dental-operations-analyst), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A treatment-planning-and-revenue-cycle team for a dental practice owner — it controls overhead against the ~62% median, holds collections above 98%, builds case acceptance on the treatment plan rather than the discount, and reads doctor/hygiene production per hour the way a practice that runs on the schedule does. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  37. Databricks lakehouse engineering team — agents (lakehouse-architect, databricks-platform-engineer) answering 'how do we build this on Databricks correctly and affordably?': medallion (bronze/silver/gold) architecture, Delta Lake table design (partitioning, liquid clustering, OPTIMIZE/Z-ORDER, VACUUM), Unity Catalog governance (catalogs/schemas/grants, lineage), Spark & PySpark job design and the shuffle/skew/spill failure modes, Structured Streaming & Auto Loader, DLT pipelines, Photon, Jobs/Workflows orchestration, and cluster/SQL-warehouse sizing & cost control (DBUs, autoscaling, spot, serverless). Engineering judgment, not a benchmark; DBR/runtime/pricing specifics are volatile — every version carries a retrieval date + [verify-at-use]. Distinct from microsoft-fabric (Fabric/OneLake), data-platform (generic ETL), data-orchestration (Airflow/Dagster), analytics-engineering (dbt/semantic layer), and ml-engineering (classical MLOps). Needs ravenclaude-core.

    Claude Code2 skills
  38. Database Reliability Engineering (DBRE) team — agents (dbre-architect, database-operations-engineer, database-incident-responder) that own the PRODUCTION database as a reliability surface, the layer database-engineering (schema/query design) doesn't: HA topology & failover from RPO/RTO, backup & point-in-time recovery with restore verification, disaster recovery, capacity planning, connection pooling; zero-downtime expand-contract migrations, backfills, replication management & failover drills, upgrades; and DB on-call (replication lag, lock contention, connection storms, runaway queries, disk-full), DB SLOs, blameless postmortems. skills, a knowledge bank with Mermaid decision trees + a dated 2026 reference, best-practices, templates. Seams: schema/query → database-engineering; service SRE → observability-sre; provisioning → terraform-iac / cloud; pipelines → data-orchestration; access → security-engineering / auth-identity. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills
  39. Database-engineering team — agents (schema-architect, query-performance-engineer, migration-engineer, db-reliability-engineer) for the OPERATIONAL/transactional data layer (OLTP): relational schema design and normalization (and when to denormalize), indexing strategy and query/EXPLAIN-plan tuning, safe zero-downtime schema migrations (expand/contract), and connection-pooling, transactions/isolation, replication, and backup/restore reliability. Postgres-leaning, principles portable to MySQL/SQL Server; NoSQL access-pattern guidance where it fits. skills, a decision-tree knowledge bank (index-choice + migration-safety trees + a dated 2026 capability map), best-practices, templates, commands, an advisory hook. Distinct from data-platform (analytics/ELT/warehouse) and analytics-engineering (dbt). Seams: ELT/warehouse -> data-platform, ORM/app data-access -> backend-engineering, managed DB infra -> cloud plugins. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  40. Data-streaming-engineering team — agents (streaming-architect, kafka-pipeline-engineer, stream-processing-engineer) for REAL-TIME data: streaming-vs-batch decision and topology, event streaming + CDC (Kafka/Pulsar/Kinesis, topics/partitioning, schema registry + evolution, the outbox/Debezium CDC pattern), delivery semantics (at-least-once vs exactly-once, idempotency, transactional outbox), and stream processing (Flink/Kafka-Streams: event-time vs processing-time, windowing, watermarks, state, joins, backpressure). skills, a decision-tree knowledge bank (streaming-vs-batch + delivery-semantics trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Distinct from data-platform (batch ELT) and microsoft-fabric (RTI/Eventstream). Seams: batch ELT -> data-platform, AsyncAPI contracts -> api-engineering, Fabric RTI -> microsoft-fabric, app-side messaging -> backend-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code7 skills
  41. Exploratory data science & reproducible research team — agents (exploratory-data-scientist, feature-and-modeling-engineer, research-reproducibility-engineer) for the analysis layer between raw data and a defensible result: data profiling/cleaning, EDA, hypothesis generation, communicating findings with uncertainty; feature engineering, classical modeling (regression, trees, boosting), model selection, evaluation (cross-validation, metrics) and leakage avoidance; and the reproducibility spine — notebook hygiene, pinned environments, experiment tracking, data/version control, seeds, and reproducible pipelines. best-practices, decision-tree knowledge bank, skills, commands, templates, a hook, scenarios bank, and stdlib-only ds_calc.py (classification/regression metrics, split-check). Seams: is-the-result-statistically-real -> applied-statistics; productionize/serve/monitor -> ml-engineering; data pipelines/warehouse -> data-platform. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  42. Data-quality & observability team — agents (data-quality-architect, data-quality-engineer) for the layer answering 'is this data CORRECT, FRESH, COMPLETE, and can we TRUST it?': producer-boundary contracts, validation tests (not-null/unique/accepted-values/referential/distribution), freshness/volume/schema-drift/distribution monitors, threshold vs statistical anomaly detection, data-quality SLAs/SLIs, and data-incident response (triage, quarantine/circuit-breaker, root-cause, backfill). Fluent in dbt tests + dbt-expectations, Great Expectations, Soda, Elementary, managed observability (Monte Carlo, Bigeye, Metaplane), and warehouse-native checks. skills, a knowledge bank (tooling decision tree + 2026 patterns reference), and templates. Distinct from data-platform (ELT/warehouse/BI), analytics-engineering (dbt transforms), data-orchestration (schedules the runs), and data-governance-privacy (policy/PII/lineage) — this is the trust/quality layer over all of them. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  43. Data-platform team — agents (database-setup-guide, etl-pipeline-engineer, dashboard-builder, connector-developer) for cloud DBs, ELT (Airbyte / Fivetran / n8n) with connectors for QuickBooks / Stripe / Salesforce / HubSpot / GA4 / Shopify / HRIS / Planhat / Intercom / Slack-as-source plus 8-vendor support-tool integration coverage (Zendesk, Freshdesk, Intercom Conv+Tkt, SFDC Service Cloud, JSM, HubSpot Service, Help Scout, Front + 2026 Fivetran connector-MAR build-vs-buy math), and embedded dashboards (Evidence.dev / Superset / Metabase / Cube + Tremor). skills (incl. support-ticket-normalization — conformed fct_ticket / fct_conversation_event over 8 vendors; cross-system-identity-resolution — the Salesforce↔Planhat↔Intercom↔Slack account spine), templates, a knowledge bank, best-practices. Opinionated against per-viewer-priced BI for greenfield SMB. Requires ravenclaude-core@>=0.7.0.

    Claude Code15 skills
  44. Data-orchestration team — agents (orchestration-architect, pipeline-orchestration-engineer) for the layer that RUNS and SCHEDULES data pipelines: orchestrator selection (Airflow, Dagster, Prefect, Mage, Temporal-for-data; cloud-native MWAA/Step Functions, Azure Data Factory, Cloud Composer/Workflows), DAG and software-defined-asset design, scheduling/triggers (cron, sensor, data-aware), backfills and catchup, idempotency and retries with exponential backoff, partitioning, freshness SLAs and alerting, and lineage. skills (choose-orchestrator, design-dag-and-dependencies, handle-backfills-and-retries), a knowledge bank (a Mermaid selection tree + a 2026 patterns reference), and templates. Distinct from data-platform (ELT/warehouse/BI), analytics-engineering (dbt), and data-streaming-engineering (real-time) — this is the scheduling/run layer they plug into. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  45. Data governance & privacy team — agents (data-governance-architect, privacy-compliance-engineer, data-catalog-lineage-engineer) for making data discoverable, trustworthy, and lawfully used: the governance operating model (ownership/stewardship, policies, classification scheme), privacy mechanics (GDPR/CCPA/-style data-subject rights — access/erasure/portability, consent + lawful basis, data minimization, retention, pseudonymization vs anonymization), and a data catalog with lineage + sensitive-data/PII discovery + access governance/DLP. The ENGINEERING of governance, not legal advice. skills, a decision-tree knowledge bank (classification + DSR-handling trees + a dated 2026 map), best-practices, templates, commands, an advisory hook. Seams: financial-regulatory -> regulatory-compliance, warehouse RLS -> data-platform, Purview-in-Fabric -> microsoft-fabric, security verdicts -> security-engineering. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  46. Cybersecurity governance, risk & compliance (GRC) team — agents (grc-architect, control-and-evidence-engineer, audit-and-third-party-risk-lead) for the security-compliance program layer: framework selection & scoping (SOC 2 TSC, ISO 27001 + Annex A, NIST CSF 2.0, NIST 800-53), the ISMS, control crosswalk across frameworks, the Statement of Applicability; control implementation & operating effectiveness, policy authoring, evidence collection & continuous control monitoring, Type I vs Type II readiness; audit readiness, gap assessments, and vendor/third-party risk (TPRM tiering, SIG/CAIQ, shared-responsibility, monitoring). Decision-tree bank (Mermaid trees), best-practices, skills, commands, templates, a hook, a grc_calc.py risk/coverage/readiness calculator, scenarios. Seams: AppSec -> security-engineering; financial-regulator -> regulatory-compliance; privacy mechanics -> data-governance-privacy; cloud config -> aws/azure/gcp-cloud. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  47. Customer Support & CX Operations specialist team — agents (support-ops-lead, ticket-deflection-analyst, queue-staffing-specialist, csat-quality-strategist), skills, templates, commands, an advisory hook, best-practice rules, and a research-grounded knowledge bank. A support-ops team for a head of support, CX manager, or founder accountable for cost-to-serve and SLA attainment — it deflects before hiring, staffs to forecast and occupancy, reads CSAT segmented, and treats backlog as arrivals-against-capacity flow. Inherits ravenclaude-core protocols.

    Claude Code5 skills
  48. Customer-Success analytics team — specialist agents (cs-analytics-architect, churn-signal-analyst) that own the DOMAIN layer of a CS-health analytics build: the conformed account / health-snapshot / renewal data model, which signals compose the health view, and the transparent rule-based Green/Yellow/Red risk tier (every Red shows why) — no black-box ML in phase one. Domain-neutral: it sits on top of data-platform's pipeline/warehouse/connector layer (which it routes all plumbing to) rather than duplicating it. skills, best-practice rules, a knowledge bank (CS-health/churn signals, renewal lifecycle, NRR/GRR retention metrics, consolidated + risk-tier-escalation Mermaid decision trees), a scenarios bank (field notes), a stdlib cs_calc.py (NRR-GRR + weighted health-score + renewal-risk), and data-model + tier-design templates whose identity spine points at data-platform. Pairs with data-platform; seams to salesforce / tableau / edtech-partner-success. Requires ravenclaude-core@>=0.7.0.

    Claude Code5 skills
  49. Creator-economy business operations team — agents (creator-business-strategist, content-and-audience-manager) for running a creator/media business: the monetization mix (ads, sponsorships, memberships & subscriptions, products/courses, affiliate, services), the platform portfolio (owned vs rented, platform-risk diversification, repurposing), audience funnel & LTV, sponsorship valuation & rate cards, content ops, community & retention, and the creator P&L/MRR. skills (choose-monetization-mix, price-a-brand-deal, plan-content-and-audience-growth), a knowledge bank (a Mermaid monetization-mix tree + a dated 2026 platform/payout/rate reference), best-practices. ADVISORY operations knowledge, not legal/tax/financial advice; payout rules, rate norms, and FTC/ASA disclosure specifics are volatile + jurisdictional, retrieval-dated + verify-at-use; no audience PII. Distinct from marketing-operations, developer-relations, and ecommerce-dtc. Requires ravenclaude-core@>=0.7.0.

    Claude Code3 skills
  50. Craft-beverage (winery / brewery / distillery) operations team — agents (craft-beverage-operations-lead, tasting-room-and-club-manager, beverage-distribution-compliance-advisor) across the three engines of a producer: production & cost (batch/yield planning, COGS per unit, tank/barrel/time capacity, packaging, channel margin mix), the tasting room & club (throughput and conversion, club/membership revenue and churn, DTC, events), and distribution & compliance (three-tier vs self-distribution economics, distributor relationships, TTB / state licensing and excise). Operations and financial decision-support, not legal, tax, or regulatory advice; no licensing/excise determinations and no PII; benchmarks carry a retrieval date + verify-at-use; three-tier / TTB / licensing / excise rules are jurisdiction-specific and flagged for a professional. Ships skills, a decision-tree knowledge bank (Mermaid trees + a dated 2026 reference), best-practices, templates, commands. Requires ravenclaude-core@>=0.7.0.

    Claude Code4 skills