add-coding-agent-integration
Orchestrate a complete Braintrust coding-agent integration by delegating feasibility, daemon translation, event capture, setup, managed run, transcript import, verification, and shipping to the specialized repo-local skills. Use for end-to-end support for a new agent or a completeness audit of an existing integration; use the component skills directly for focused work.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 3
- Forks
- 3
01 前言 Front Matter
- name
- add-coding-agent-integration
- description
- Orchestrate a complete Braintrust coding-agent integration by delegating feasibility, daemon translation, event capture, setup, managed run, transcript import, verification, and shipping to the specialized repo-local skills. Use for end-to-end support for a new agent or a completeness audit of an existing integration; use the component skills directly for focused work.
02 资源文件 1
- 参考文档agents/openai.yaml234 B
03 SKILL.md 正文
Orchestrate a coding-agent integration
Coordinate the integration; do not implement component details from this skill. Inspect current source, keep a requirement-to-evidence inventory, and invoke the specialized skill for every applicable workstream.
Delegate the work
- Use
audit-agent-tracing-supportto establish whether hooks, an in-process plugin API, transcripts, or a combination can provide sufficient data. - Use
add-coding-agent-translatorto establish the canonical source identity and production daemon translator first. - Use
add-coding-agent-captureto forward live native events through command hooks or an in-process plugin. - Once the translator exists, delegate independently:
- persistent installation and configuration to
add-coding-agent-setup; - invocation-local launching to
add-coding-agent-run; - historical import and live transcript following to
add-coding-agent-import, when a viable transcript exists.
- persistent installation and configuration to
- Use
test-coding-agent-integrationto verify every implemented surface and the combined end-to-end path. - Use
ship-coding-agent-integrationonly after verification evidence exists.
Add every applicable skill to the working plan and follow that skill when its workstream begins. Do not copy its instructions into the plan or preload skills for workstreams that are out of scope.
Maintain the shared contract
Keep one stable source identity across the translator, capture adapter, setup, run, import, status, tests, and documentation. Keep plugins and hooks thin, fail-open, credential-free forwarders; the daemon owns correlation, trace construction, recovery, routing, and delivery.
Treat a missing capability as blocked or explicitly not applicable with
evidence, never as silently complete. Do not call the integration complete
until each applicable component skill has produced implementation and test
evidence and the shipping skill has confirmed a releasable distribution path.
Hand off
Report a compact matrix with one row per delegated skill: status, source evidence, test evidence, blockers or fidelity loss, and remaining release work.
04 同仓库更多 Skills
troubleshoot-braintrust-mcp
Diagnose Braintrust MCP connection issues.
braintrust
Use Braintrust for LLM evaluation, logging, and observability.
test-coding-agent-integration
Test or audit a coding-agent tracing integration across translator fixtures, capture adapters, setup, managed run, transcript import, daemon recovery, real-agent execution, package installation, and CI. Use when adding verification, reviewing integration completeness, diagnosing coverage gaps, or proving that emitted events become correct Braintrust traces.
ship-coding-agent-integration
Package and release a coding-agent tracing integration through its marketplace, package registry, or distribution repository, including manifests, builds, validation, versioning, CI, documentation, publishing automation, and installed-artifact smoke tests. Use when preparing an integration for release or auditing whether it has a complete distribution path.
audit-agent-tracing-support
Assess whether a coding agent's hooks/plugin API can support tracing (per docs/trace-coding-agents-with-hooks.md), or whether a reliable fallback like session transcripts exists. Use when evaluating a new or existing coding agent (Claude Code, Codex, Cursor, Gemini CLI, Aider, etc.) for a Braintrust tracing plugin, or when someone asks "can we trace agent X" / "is agent X's hook API good enough".
add-coding-agent-translator
Implement or review a coding agent's daemon translator, including source registration, native event correlation, trace shape, deterministic recovery, routing metadata, and translator tests. Use when adding a new agent translator or changing how an existing agent's hooks or transcripts become Braintrust spans.