agentic-design-patterns skills

61 tagged agentic-design-patterns, measured the same way as everything else here.

Browse within: agentic-workflow 71agentic-development 70ai-developer-tools 70ai-first 70claude-code-plugin 70gemini-cli 56CrewAI 28antigravity 28extensions 28gemini-cli-extension 28gemini-cli-extensions 28agentic-ai 5

weather-skill

01

simranjeet97/Awsome_AI_Agents

Skill Claude CodeCodex

Fetches real-time weather conditions for any city or location worldwide. Use this skill when the user asks about weather, temperature, rain, forecast, or climate conditions for a specific place.

not rated 229 6mo ago A 41 tokens original Apache-2.0

a2a

02

hajekim/agentic-design-patterns-skills

Skill Claude CodeCodex

This skill should be used when the user wants to "agent-to-agent communication", "A2A protocol", "inter-agent messaging", "agent network", "agent federation", "cross-agent calls", "distributed agent systems", "agent discovery", "agent cards", "standardized agent communication", "remote agent invocation", "multi-agent…

not rated 4 6mo ago A 435 tokens original MIT

agentify

03

avnath13/agentify

Skill Claude CodeCodex

Design production-grade agentic AI systems from a natural-language use case. Runs a clarification loop, walks grounded decision trees (workflow vs agent, RAG vs fine-tuning, single vs multi-agent, autonomy tiers), and emits a detailed enterprise system design document with embedded interactive architecture, sequence…

not rated 2 3mo ago A 179 tokens original MIT

a2a

04

hajekim/agentic-design-patterns-extension

Skill Claude CodeCodex

This skill should be used when the user wants to "agent-to-agent communication", "A2A protocol", "inter-agent messaging", "agent network", "agent federation", "cross-agent calls", "distributed agent systems", "agent discovery", "agent cards", "standardized agent communication", "remote agent invocation", "multi-agent…

not rated 1 6mo ago A 435 tokens copy · 100% MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: