agent integration

AI Community

Skill notes

Parameters

Collect these before starting (ask the user if not provided): Parameter · Description · How to derive AGENT_NAME · Human-readable name (e.g., "Gemini CLI") · User provides AGENT_PACKAGE · Go package dir name — no hyphens · Lowercase, remove hyphens/spaces AGENT_KEY · Registry key for agent.Register() and entire enable · Check existing patterns in cmd/entire/cli/agent/registry.go

Architecture References

These documents define the agent integration contract: Implementation guide: docs/architecture/agent-guide.md — Step-by-step code templates, event mapping, testing patterns Integration checklist: docs/architecture/agent-integration-checklist.md — Design principles and validation criteria

Scope

This skill targets hook-capable agents — those that support lifecycle hooks (implementing HookSupport from agent.go). Agents that use file-based detection (implementing FileWatcher) require a different integration approach not covered here. Check agent.go for the current interface definitions.

Core Rule: E2E-First TDD

This skill enforces strict E2E-first test-driven development. The rules: E2E tests are the spec. The existing ForEachAgent test scenarios define what "working" means. The agent runner makes those tests runnable for the new agent. Run E2E tests at every step. Each implementation tier starts by running the E2E test and watching it fail. You implement until it passes. No exceptions. Unit tests are written last. After all E2E tiers pass (Step 14), you write unit tests using real data collected from E2E runs as golden fixtures.

Pipeline

Run these three phases in order. Each phase builds on the previous phase's output.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@entireio · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Research

Discover the agent's hook mechanism, transcript format, and configuration through binary probing and documentation research. Produces an implementation one-pager at `cmd/entire/cli/agent/$AGENT_PACKAGE/AGENT.md` that the other phases use as their single source of agent-specific information. Read and follow the research procedure from `.claude/skills/agent-integration/researcher.md`. Expected output: Implementation one-pager at `cmd/entire/cli/agent/$AGENT_PACKAGE/AGENT.md` and a test script at `scripts/test-$AGENT_SLUG-agent-integration.sh`.

02
Phase 2: Write E2E Runner

Create the E2E agent runner so existing test scenarios can exercise the new agent. No unit tests are written in this phase — no new test scenarios either (existing `ForEachAgent` tests are the spec). Read and follow the procedure from `.claude/skills/agent-integration/test-writer.md`. Expected output: E2E agent runner at `e2e/agents/$AGENT_SLUG.go` that compiles and registers with the test framework.

03
Phase 3: Implement (E2E-First, Unit Tests Last)

Build the Go agent package using strict E2E-first TDD. E2E tests drive development at every step — run each tier, watch it fail, implement the minimum fix, repeat. Unit tests are written only after all E2E tiers pass, using real data from E2E runs as golden fixtures. Read and follow the implement procedure from `.claude/skills/agent-integration/implementer.md`. Expected output: Complete agent package at `cmd/entire/cli/agent/$AGENT_PACKAGE/` with all E2E tiers passing and unit tests locking in behavior.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.