add-agent

Guide creating or updating agent adapters in the Exgentic repository.

68|22|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Exgentic/exgentic --skill add-agent-exgentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-agent
Source: https://github.com/Exgentic/exgentic/tree/main/misc/skills/add-agent
Command: npx skills add https://github.com/Exgentic/exgentic --skill add-agent-exgentic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

add-agent provides a structured, best-practice workflow for creating or updating agent adapters in the Exgentic repository, ensuring consistent integration and safer extension points.

Core Features & Use Cases

  • Guides on implementing light-weight adapters with lazy imports and isolating heavy dependencies behind module boundaries.
  • Covers the Agent and AgentInstance patterns, registry registration, and validation against benchmark contracts.
  • Helps maintainability through standard tests, documentation, and safety checks for end-to-end workflow across benchmarks.

Quick Start

Follow the workflow to implement a new or updated agent adapter in a smoke-tested, reproducible manner.

Frequently Asked Questions about add-agent

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

FAQPage Schema
How do I add a new agent adapter to a software engineering repository?

To add a new agent adapter, follow a guided workflow to implement lightweight Agent and AgentInstance classes with lazy imports, register them in the repository registry, and validate them against benchmark contracts.

What is the best way to update existing agent adapters while isolating heavy dependencies?

Updating agent adapters involves separating heavy dependencies behind module boundaries using lazy imports, ensuring importability, verifying correct constructor usage, and running end-to-end smoke tests for safe cleanup.

Why do my agent adapters fail end-to-end validation against benchmark contracts?

Agent adapters fail validation when they lack proper registry registration, use incorrect constructors, or import heavy dependencies eagerly, violating the reproducible workflow rules required for benchmark contracts.

Can I use lazy imports to keep agent adapter classes lightweight during registry registration?

Yes, you can and should use lazy imports when creating Agent and AgentInstance classes, which isolates heavy dependencies behind module boundaries and ensures safe, lightweight registry registration.

When do I need to validate agent adapters against benchmark contracts?

You need to validate agent adapters against benchmark contracts during end-to-end testing to enforce importability, confirm correct constructor usage, and ensure safe cleanup after standard tests run.

Does the add-agent workflow support smoke tests for reproducible adapter integration?

Yes, the add-agent workflow supports smoke tests to implement new or updated agent adapters in a reproducible manner, maintaining safety checks and standard tests across benchmarks.