ask-docs
Query the official CrewAI documentation for answers. Use when the user has a CrewAI question that isn't fully covered by the getting-started, design-agent, design-task skills — e.g., specific API details, configuration options, advanced features, troubleshooting errors, enterprise features, tool references, or anything where the latest docs are the best source of truth.
What this skill does
# Ask CrewAI Docs Answer CrewAI questions by looking up the official documentation at `docs.crewai.com`. --- ## When to Use This Skill Use this skill when: - The user asks about a CrewAI feature, parameter, or behavior not covered in detail by the other skills - You need to verify current API syntax, method signatures, or configuration options - The user hits an error and needs troubleshooting guidance from official docs - The question is about a newer or less common CrewAI feature (e.g., telemetry, testing, CLI commands, deployment, enterprise features) - You're unsure whether your knowledge is current — the docs reflect the latest published state **Do NOT use this skill** when the question is clearly answered by one of the other skills (getting-started, design-agent, design-task). Those skills contain curated, opinionated guidance. This skill is for filling gaps and verifying details. --- ## How to Query the Docs ### Step 1: Fetch the docs index The CrewAI docs site publishes an `llms.txt` file — a structured index of every documentation page with descriptions. Fetch it first to find the right page: ``` WebFetch: https://docs.crewai.com/llms.txt ``` This returns a categorized list of all doc pages in the format: ``` - [Page Title](https://docs.crewai.com/path/to/page): "Description of what the page covers" ``` Categories include: - **API Reference** — REST endpoints (kickoff, status, resume, inputs) - **Concepts** — agents, crews, tasks, tools, flows, memory, knowledge, LLMs, processes, training, testing - **Enterprise** — RBAC, SSO, automations, traces, deployment, triggers, integrations - **Tools Library** — 40+ tools organized by category (AI/ML, automation, cloud, database, files, search, web scraping) - **MCP Integration** — MCP server setup, transports, DSL, security - **Examples & Cookbooks** — practical implementations - **Learning Paths** — tutorials and advanced topics - **Observability** — monitoring integrations ### Step 2: Fetch the relevant page Once you identify the right page from the index, fetch its content: ``` WebFetch: https://docs.crewai.com/<path-from-index> ``` ### Step 3: Synthesize and cite Combine what you find from the docs with context from the other skills to give a clear, actionable response. Always include the docs URL so the user can read further. --- ## Workflow Summary 1. **Understand the user's question** — what specific CrewAI concept, API, or behavior are they asking about? 2. **Fetch `llms.txt`** — scan the index to find the most relevant page(s) 3. **Fetch the page(s)** — retrieve the actual documentation content 4. **Synthesize the answer** — combine docs content with context from other skills 5. **Cite the source** — include the docs URL in your response --- ## For an Even Better Experience Users who frequently query CrewAI docs can configure the CrewAI docs MCP server in their coding agent for richer, structured search: ``` https://docs.crewai.com/mcp ``` This is optional — the `llms.txt` workflow above works without any setup. --- ## Examples of Good Use Cases | User Question | Why This Skill | |---|---| | "What parameters does `Crew()` accept?" | Specific API reference — docs are authoritative | | "How do I set up telemetry in CrewAI?" | Niche feature not covered in other skills | | "What's the difference between `Process.sequential` and `Process.hierarchical`?" | Detailed comparison best sourced from docs | | "I'm getting `ValidationError` when using `output_pydantic`" | Troubleshooting — docs may have known issues or caveats | | "How do I deploy a CrewAI flow to production?" | Deployment guidance lives in docs, not in design skills | | "What CLI commands does `crewai` support?" | CLI reference is a docs concern | | "How do I configure memory for a crew?" | Detailed config options beyond what design-agent covers | | "What tools are available for web scraping?" | Tools library reference | | "How do I set up SSO for CrewAI enterprise?" | Enterprise features live in docs | --- ## Related Skills - **getting-started** — project scaffolding, choosing abstractions, Flow architecture - **design-agent** — agent Role-Goal-Backstory, parameter tuning, tools, memory & knowledge - **design-task** — task descriptions, expected_output, guardrails, structured output, dependencies
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.