dual-agent

Enforce feature parity and shared architecture between LangChain and PydanticAI agents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-demo --skill dual-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dual-agent
Source: https://github.com/curtismu7/AI-demo/tree/main/.claude/skills/dual-agent
Command: npx skills add https://github.com/curtismu7/AI-demo --skill dual-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that both the LangChain and PydanticAI agents have identical capabilities, maintaining feature parity and shared architecture.

Core Features & Use Cases

  • Feature Parity Enforcement: Ensures every user-visible capability in one agent exists in the other.
  • Shared Architecture Decisions: Consistent implementation of wire protocol contracts, run.sh registration, and architecture patterns.
  • LLM Provider Parity: Supports the same LLM providers in both agents.
  • Use Case: Before making changes to either agent, this Skill provides guidelines and a checklist to maintain parity between the two.

Quick Start

Review the dual-agent skill before making changes to either the LangChain or PydanticAI agent to ensure feature parity.

Frequently Asked Questions about dual-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain feature parity between LangChain and PydanticAI agents?

To maintain feature parity between LangChain and PydanticAI agents, apply a checklist enforcing identical user-visible capabilities, wire protocol agreements, and shared architecture patterns before modifying either agent.

What is the best way to enforce shared architecture across multiple AI agents?

Enforcing shared architecture across multiple AI agents requires consistent implementation of wire protocol contracts and run.sh registration, ensuring both LangChain and PydanticAI agents apply identical structural patterns.

Do I need a parity checklist to update LLM provider support in dual agents?

Yes, a parity checklist is needed to update LLM provider support, ensuring that any provider added or modified in the LangChain agent is equally supported and configured in the PydanticAI agent.

When should I use a dual-agent parity workflow for software engineering?

Use a dual-agent parity workflow whenever modifying either the LangChain or PydanticAI agent, specifically when tasks involve changing capabilities that must remain identical across both implementations to prevent architectural drift.

Can I use this approach to sync wire protocol contracts between different agent frameworks?

Yes, you can use this approach to sync wire protocol contracts between different agent frameworks by applying predefined guidelines that enforce matching communication protocols and shared architectural decisions across LangChain and PydanticAI.

Why does my PydanticAI agent have capabilities missing from the LangChain implementation?

Capabilities are missing because feature parity was not enforced during development; applying a dual-agent checklist ensures every user-visible capability in one agent exists in the other before changes are merged.