Check Crewai API
Current crewai 1.15.x API versus the 0.x API that coding assistants remember: imports, Agent/Task/Crew parameters and defaults, kickoff variants, CrewOutput fields, LLM model strings and provider extras, structured output (output_pydantic, response_model, response_format), guardrails, unified Memory, knowledge embedders, the `crewai create crew` wizard vs --classic, reset-memories flags, and removed features. Use when writing, reviewing, or debugging any crewai code, before trusting remembered crewai syntax, or when a user pastes errors like `cannot import name 'BaseTool' from 'crewai_tools'`,
Install
/plugin marketplace add crewAIInc/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add crewAIInc/skills --skill check-crewai-apigit clone --depth 1 https://github.com/crewAIInc/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/check-crewai-api ~/.claude/skills/check-crewai-apiPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Check CrewAI API
Load this before writing or reviewing crewai code: it maps what you probably remember to what crewai 1.15.x actually accepts.
Verified against crewai 1.15.22 and 1.15.23 on 2026-10-01.
Live-tested with real LLMs on 2026-10-01.
Run `crewai version` first; if the major/minor differs from 1.15, re-verify version-sensitive rows with the `ask-docs` skill before trusting them.
---
## 1. Three rules before you write anything
1. **Unknown keyword arguments are silently ignored.** `Agent`, `Task` and `Crew` accept and drop parameters that do not exist. `Crew(memory_config={...})` and `Task(response_format=Model)` construct fine and do nothing. A stale parameter name never raises, so check it exists:
```python
from crewai import Agent, Crew, Task
assert "response_model" in Task.model_fields # real field
assert "response_format" not in Task.model_fields # silently dropped if passed
assert "memory_config" not in Crew.model_fields # silently dropped if passed
print(sorted(Agent.model_fields)[:5])
```
2. **The installed source wins over any doc, tutorial, or memory.** That includes the `AGENTS.md` that `crewai create` writes into new projects. When a row below matters, check the installed signature (see [verify-installed-api.md](references/verify-installed-api.md)).
3. **Assert on structured output at the boundary.** Several mistakes below fail quietly with `out.pydantic is None` while the run reports success.
---
## 2. ImportsDetails
- Skill name
check-crewai-api- Repository
- crewAIInc/skills
- Path
skills/check-crewai-api/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Check Crewai API skill do?
Current crewai 1.15.x API versus the 0.x API that coding assistants remember: imports, Agent/Task/Crew parameters and defaults, kickoff variants, CrewOutput fields, LLM model strings and provider extras, structured output (output_pydantic, response_model, response_format), guardrails, unified Memory, knowledge embedders, the `crewai create crew` wizard vs --classic, reset-memories flags, and removed features. Use when writing, reviewing, or debugging any crewai code, before trusting remembered crewai syntax, or when a user pastes errors like `cannot import name 'BaseTool' from 'crewai_tools'`,
How do I install the Check Crewai API skill?
Claude Code plugin: /plugin marketplace add crewAIInc/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Check Crewai API popular?
It lives in crewAIInc/skills, which has 49 GitHub stars and 24 forks.
Related skills
Ask Docs
49crewAIInc/skills
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.
Build Flow
49crewAIInc/skills
Building CrewAI Flows on crewai 1.15.x: structured (Pydantic) vs dict state and state.id, @start/@listen/@router wiring, or_/and_ semantics, router labels vs method names, @persist (correct import, where it stores state, restore_from_state_id), checkpointing with CheckpointConfig, @human_feedback and HumanFeedbackResult.feedback, plot(), calling crews and agents from flow methods, kickoff inputs, and the `crewai create flow` scaffold. Use when writing or debugging a Flow subclass or main.py with `from crewai.flow import ...`, when a listener never fires or fires twice, or when you see errors l
Call Deployed Crew
49crewAIInc/skills
Calling a crew or flow deployed on CrewAI AMP over HTTP: the bearer token and deployment URL, GET /inputs, POST /kickoff with the {"inputs": {...}} body, which input keys are required ({placeholder} tokens), polling GET /status/{kickoff_id} with a deadline and backoff, terminal states and where the result lives, webhooks, POST /resume, slow first calls, and writing crews that stay correct when they are kicked off repeatedly or concurrently. Use when writing a client, script, backend or frontend that calls a deployed crew, when a kickoff returns 422 "Missing inputs: ...", when a status poll nev
Sankhya API Java
43andressaolivi/sankhya-skills
Conhecimento sobre os pontos de extensão Java do ERP Sankhya — interfaces oficiais de customização e padrões de uso da camada de persistência. Use quando o usuário perguntar sobre customização Java do Sankhya: AcaoRotinaJava, EventoProgramavelJava, RegraNegocioJava, TarefaJava, AcaoReguaCobranca, DynamicVO, JapeSession, EntityFacade, JdbcWrapper, ServiceContext, ServiceBroker; action buttons, eventos programáveis, regras de negócio, workflow Java, régua de cobrança, manipulação de VOs, persistência JAPE, SQL nativo com macros do Sankhya. NÃO use para configuração funcional do ERP (use sankhya-
AI Memory System Architecture
44hyxnj666-creator/ai-memory
System architecture facts: components, data flow, integration boundaries. Load when implementing cross-component features, debugging integration issues, or onboarding to the codebase. Topics: Event sourcing for the billing audit log.
Spec Goal Development
44hanshuang1008-del/spec-goal-development
面向跨项目 Codex 编码智能体的默认开发编排 Skill。对自然语言提出的新增、修改、调试、重构、集成或发布请求,自动判断是否属于复杂或意图不明确的开发任务;必要时用普通语言澄清真实目标,显性展示 SPEC 创建与用户授权,建立并展示 Goal,分片实施、持续调试、分层验证并完成交付闭环。非开发任务和简单、低风险、局部且可逆的开发任务走轻量路径。
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.