CtrlK
BlogDocsLog inGet started
Tessl Logo

crewai

You are an expert in designing collaborative AI agent teams with CrewAI. You think in terms of roles, responsibilities, and delegation. You design clear agent personas with specific expertise, create well-defined tasks with expected outputs, and orchestrate crews for optimal collaboration.

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/crewai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides a reasonable overview of CrewAI patterns with useful anti-patterns, but suffers from truncated/incomplete code examples that undermine actionability. It explains some concepts Claude would already know and lacks validation/error-handling guidance for multi-agent workflows. The structure is adequate but could benefit from splitting lengthy YAML examples into separate files and adding verification steps.

Suggestions

Fix the truncated Basic Crew code example and ensure all code blocks are complete and executable, including necessary imports (e.g., ChatOpenAI).

Add validation/error-handling steps: how to verify agent outputs, handle LLM failures, and debug crew execution issues.

Trim the agent backstory examples and capabilities list — Claude knows what researchers and writers do; focus on CrewAI-specific configuration patterns.

Move the lengthy YAML config example into a separate reference file and keep only a minimal inline example in SKILL.md.

DimensionReasoningScore

Conciseness

The skill includes some unnecessary explanations Claude would already know (e.g., explaining what a researcher or writer does in backstories, the 'Capabilities' and 'Requirements' sections are somewhat redundant). The YAML config example is quite long and could be tightened. The role description at the top repeats the frontmatter description. However, it's not egregiously verbose.

3 / 5

Actionability

The code examples are partially executable but have notable gaps: the Basic Crew example is truncated mid-line (`config=self.tasks_config['research_task'])` cuts off), missing imports (ChatOpenAI not imported), and the hierarchical example references undefined task variables (research_task, analysis_task, writing_task). The anti-patterns section provides good guidance but the expected_output example is not in a proper code block context.

3 / 5

Workflow Clarity

The skill shows sequential and hierarchical process types and mentions planning, but lacks explicit validation checkpoints. There's no guidance on error handling, debugging failed agent runs, or verifying outputs between steps. The planning feature section hints at structure but doesn't show how to validate or recover from failures.

3 / 5

Progressive Disclosure

The content is reasonably structured with clear sections (Patterns, Anti-Patterns, Limitations), but everything is inlined in a single file with no references to supporting documents. The YAML config examples are lengthy and could be split out. The 'Related Skills' section mentions other skills but doesn't link to them. No bundle files exist to offload detailed content.

3 / 5

Total

12

/

20

Passed

Description

45%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description reads more like a system prompt persona definition ('You are an expert...') than a skill description, using second person voice throughout. While it identifies the CrewAI domain clearly, it lacks an explicit 'when to use' clause and misses natural trigger terms users would employ. The capabilities listed are moderately specific but could be more concrete about outputs and technical actions.

Suggestions

Rewrite in third person voice (e.g., 'Designs collaborative AI agent teams using CrewAI framework') and remove the system-prompt style 'You are/You think' phrasing.

Add an explicit 'Use when...' clause with trigger terms like 'CrewAI', 'multi-agent', 'agent crew', 'agentic workflow', 'crew.ai', or when users ask about building teams of AI agents.

Include more concrete actions and outputs such as 'generates CrewAI Python code', 'defines Agent and Task classes', 'configures crew processes (sequential/hierarchical)' to improve specificity.

DimensionReasoningScore

Specificity

Names the domain (CrewAI agent teams) and mentions a few concrete actions like 'design agent personas', 'create well-defined tasks', and 'orchestrate crews', but these are somewhat high-level and not comprehensive in describing what the skill actually produces or does technically.

3 / 5

Completeness

Provides a 'what' (designing collaborative AI agent teams with CrewAI) but has no explicit 'when' clause or trigger guidance. The description is written in second person ('You are an expert...', 'You think in terms of...'), which is a system prompt style rather than a skill description. The missing 'Use when...' clause caps this at 3, and the lack of any implicit trigger guidance brings it to 2.

2 / 5

Trigger Term Quality

Includes 'CrewAI' as a key trigger term, plus related terms like 'agent teams', 'roles', 'delegation', and 'crews'. However, it misses natural user phrases like 'multi-agent', 'agentic workflow', 'crew.ai', or specific file/config references users might mention.

3 / 5

Distinctiveness Conflict Risk

The mention of 'CrewAI' specifically makes this fairly distinct from generic coding or AI skills. However, it could overlap with general multi-agent framework skills (e.g., LangGraph, AutoGen) since many of the described capabilities (roles, tasks, delegation) are common across agent frameworks.

4 / 5

Total

12

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.