wicked-garden-agentic-frameworks
Skill9 starsChanged 7 months agoMITView on GitHub
Use when selecting or comparing agentic frameworks (LangChain, LangGraph, CrewAI, AutoGen, etc.) — curated comparison by use case, language, and maturity. Gets latest context via Context7 when available. NOT for reviewing existing agentic code (use review-methodology) or architecture patterns (use agentic-patterns).
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-dataSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 66
Custom Tools: All frameworks support custom tools
- Distinctive: line 78
Third-Party Integration: All support OpenTelemetry, most support LangFuse, Arize
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agentic Frameworks
Comprehensive guide to agentic frameworks, their strengths, and how to choose the right one.
Quick Comparison Table
| Framework | Language | Best For | Maturity | Learning Curve |
| Anthropic ADK | TypeScript | Claude-specific, production | High | Low |
| LangGraph | Python | Complex workflows, state | High | Medium |
| CrewAI | Python | Role-based teams | Medium | Low |
| AutoGen | Python | Multi-agent conversations | Medium | Medium |
| Pydantic AI | Python | Type-safe agents | Medium | Low |
| OpenAI Agents SDK | Python | OpenAI-specific | Low | Low |
| LlamaIndex Agents | Python | RAG-heavy applications | High | Medium |
| Haystack | Python | Production pipelines | High | Medium |
| Semantic Kernel | C#/Python | Microsoft ecosystem | Medium | Medium |
| LangChain | Python | Rapid prototyping | High | Medium-High |
| Agency Swarm | Python | OpenAI Assistants API | Low | Low |
| Dify | Low-code | No-code workflows | Medium | Very Low |
Selection Criteria
1. Orchestration Capabilities
Simple Sequential:
- LangChain (chains)
- Haystack (pipelines)
- Pydantic AI
Complex Workflows:
- LangGraph (state machines)
- ADK (delegated workflows)
- AutoGen (conversation patterns)
Team-Based:
- CrewAI (role-based)
- Agency Swarm (org structure)
2. State Management
No Built-in State: LangChain, Pydantic AI
Checkpointed State: LangGraph (built-in), ADK (context preservation)
Distributed State: Custom implementation needed for all
3. Tool Integration
Extensive Tool Libraries: LangChain (largest ecosystem), LlamaIndex (RAG-focused), Haystack (production tools)
Easy Tool Definition: Pydantic AI (type-safe), ADK (TypeScript decorators), OpenAI Agents SDK (function calling)
Custom Tools: All frameworks support custom tools
4. Error Handling
Built-in Retry/Fallback: ADK (comprehensive), LangGraph (error handling nodes), Haystack (pipeline error handling)
Manual Error Handling: CrewAI, AutoGen, Pydantic AI
5. Observability
Native Tracing: LangSmith (for LangChain/LangGraph), Braintrust (for ADK)
Third-Party Integration: All support OpenTelemetry, most support LangFuse, Arize
Framework Profiles
See refs/framework-profiles-1.md (ADK, LangGraph, CrewAI) and refs/framework-profiles-2.md (AutoGen, Pydantic AI, LlamaIndex) for detailed profiles.
Anthropic Agent Developer Kit (ADK)
Best for: Production Claude applications Strengths: TypeScript with type safety, built-in context management, comprehensive error handling, delegated workflows Weaknesses: Claude-only, TypeScript/Node only, smaller community When to choose: Building on Claude exclusively, TypeScript/Node stack, need production-ready patterns
LangGraph
Best for: Complex stateful workflows Strengths: State machine abstraction, built-in checkpointing, human-in-the-loop support, time-travel debugging Weaknesses: Steeper learning curve, can be overkill, more boilerplate When to choose: Complex workflows with branches/loops, need state persistence, want human approval gates
CrewAI
Best for: Role-based agent teams Strengths: Intuitive role/task abstraction, simple API, good for hierarchical teams Weaknesses: Less mature, limited state management, fewer production features When to choose: Team-based workflows, quick prototyping, straightforward delegation
AutoGen
Best for: Multi-agent conversations Strengths: Flexible conversation patterns, group chat capabilities, human-in-the-loop Weaknesses: Can be verbose, conversation management complexity When to choose: Agents need to debate/collaborate, conversational workflows
Pydantic AI
Best for: Type-safe Python agents Strengths: Type safety via Pydantic, simple clean API, dependency injection, multi-provider Weaknesses: New/less mature, smaller ecosystem, limited orchestration patterns When to choose: Want type safety, simple agent use cases, already using Pydantic
LlamaIndex Agents
Best for: RAG-heavy applications Strengths: Excellent retrieval capabilities, query planning, tool use with data Weaknesses: Best for RAG use cases, heavier framework When to choose: Heavy RAG requirements, complex data retrieval, query planning needs
Decision Tree
Start: What's your primary use case?
├─ Complex stateful workflow with branches/loops
│ └─ Use: LangGraph
├─ Role-based team of agents
│ └─ Use: CrewAI or ADK
├─ RAG-heavy application
│ └─ Use: LlamaIndex Agents
├─ Multi-agent conversations/debates
│ └─ Use: AutoGen
├─ Simple sequential workflow
│ ├─ TypeScript?
│ │ └─ Use: ADK
│ └─ Python?
│ └─ Use: Pydantic AI or LangChain
├─ Production pipeline
│ └─ Use: Haystack or ADK
└─ Maximum flexibility
└─ Build from scratch or use LangGraphLanguage Considerations
Python Frameworks: LangChain, LangGraph, CrewAI, AutoGen, Pydantic AI, LlamaIndex
- Largest ecosystem, most tutorials/examples, best for data science/ML integration
TypeScript Frameworks: Anthropic ADK
- Better type safety, Node.js ecosystem, good for web applications
C# Frameworks: Semantic Kernel
- Microsoft ecosystem, .NET integration
Multi-Provider vs Single-Provider
Multi-Provider (LLM-agnostic): LangChain, LangGraph, CrewAI, AutoGen, Pydantic AI
- Can switch between OpenAI, Anthropic, etc.
- More flexibility but may not leverage provider-specific features
Single-Provider (Optimized): ADK (Claude), OpenAI Agents SDK (OpenAI)
- Better integration with specific provider
- Access to provider-specific features but less flexibility
Production Readiness
Most Production-Ready: Anthropic ADK, LangGraph, Haystack, LlamaIndex
Good for Production: CrewAI, LangChain, AutoGen
Early/Experimental: Pydantic AI, OpenAI Agents SDK, Agency Swarm
When NOT to Use a Framework
Build from scratch if: very simple use case, specific requirements unmet, want maximum control, or learning exercise. Framework overhead not worth it for single LLM calls, static prompts, or no agent behavior.
Quick Recommendations
Just getting started: CrewAI or Pydantic AI | State management: LangGraph | TypeScript: ADK | RAG: LlamaIndex | Team-based: CrewAI or ADK | Max flexibility: LangGraph | Production Claude: ADK
References
refs/framework-profiles-1.md- ADK, LangGraph, CrewAI detailed profilesrefs/framework-profiles-2.md- AutoGen, Pydantic AI, LlamaIndex profiles + comparison matrixrefs/migration-patterns-paths.md- Common migration paths between frameworksrefs/migration-patterns-testing.md- Migration testing, rollback, and effort estimates
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

