saas-agent-toolkit
Design agent-usable SaaS tool systems using six reusable tool shapes (Search, Summarize, Draft, Update, Notify, Approve) plus connectors and policy guardrails. Use when turning SaaS features into reliable agent actions with clear contracts, permissions, audit trails, and approval gates.
What this skill does
# SaaS Agent Toolkit ## Overview Use this skill when a user asks how to make a SaaS product "agent-usable" rather than only human-usable. This skill reframes product capabilities into a stable execution model: 1. Connectors layer: auth and event plumbing 2. Tools layer: six reusable tool shapes 3. Policy layer: permissions, approvals, and reliability guardrails ## Workflow 1. Scope target SaaS domain and entities. 2. Define the 3-layer architecture. 3. Map capabilities into the six tool shapes. 4. Add guardrails (auth, allowlists, idempotency, audit). 5. Produce a concrete rollout plan and KPI set. ## Step 1: Scope Domain Capture: - Product/system (for example Zendesk, Salesforce, Jira, Notion) - Core entities (ticket, contact, issue, page, deal, order) - High-risk actions (payment, delete, external publish, permission change) - Success outcome (speed, quality, cost, reliability) ## Step 2: Build 3-Layer Architecture Design these layers explicitly: 1. `Connectors`: OAuth/API key, webhook ingestion, identity mapping, optional SCIM. 2. `Tools`: Search, Summarize, Draft, Update, Notify, Approve. 3. `Policy & Guardrails`: RBAC, budgets, rate limits, PII controls, logging, retries. Design principle: Prefer predictable, auditable, rollback-safe operations over "smart but opaque" behavior. ## Step 3: Define Tool Contracts Use six stable tool contracts: 1. `Search`: locate entities and relationships. 2. `Summarize`: produce structured, citation-backed takeaways. 3. `Draft`: generate submit-ready drafts without auto-sending. 4. `Update`: write bounded, idempotent changes back to systems. 5. `Notify`: close loops with owners/watchers/approvers. 6. `Approve`: enforce human gating for high-risk operations. Read `references/tool-contracts.md` for function templates and I/O expectations. ## Step 4: Add Mandatory Guardrails Apply all of the following: - Explicit error taxonomy (`401`, `403`, `404`, `empty`, `conflict`, `timeout`) - Idempotency key for mutating actions - Field allowlist for `Update` (no unrestricted patch) - Citation requirement for `Summarize` - Dry-run and draft-only defaults for user-facing output - Approval gates for high-risk categories - Full audit trail: who requested, who approved, what changed, when, result Read `references/approval-and-audit.md` for standard approval and audit schema. ## Step 5: Produce Deliverables Return output in this structure: 1. Domain scope and entities 2. 3-layer architecture 3. Tool contract table (six tools) 4. Guardrail design 5. Example end-to-end workflow 6. Rollout plan (`0-30`, `31-90`, `90+` days) 7. KPI table 8. Top unresolved risk KPI minimums: - task completion rate - first-call success - API success rate - p95 latency - integration lead time - unit outcome cost ## Example Workflow Patterns Use `references/workflow-patterns.md` for ready-to-adapt flows: - customer support triage and response - sales follow-up automation - incident assistant with approval-gated external updates
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.