AGENT SKILL

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.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 3
Forks
3

01 前言 Front Matter

name
ship-coding-agent-integration
description
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.

02 资源文件 1

03 SKILL.md 正文

Ship a coding-agent integration

Require verification evidence from test-coding-agent-integration. Do not publish, tag, or mutate a live distribution unless the user explicitly requests that release action.

Prepare the distribution

  • Integrate the agent with the repository's build, validation, and publishing system using its supported marketplace or package format.
  • Validate manifests, entrypoints, generated artifacts, package allowlists, platform binaries, dependency compatibility, and installability.
  • Ensure distributed hooks and plugins remain thin daemon forwarders without direct Braintrust credential or ingest logic.
  • Add versioning, tags, release notes, provenance, and release automation suited to the distribution channel, including a safe dry-run path.
  • Document prerequisites, setup, run, import or attach, disablement, troubleshooting, fidelity limitations, privacy behavior, and release steps.
  • Configure only the narrowly required publishing and optional smoke-test secrets.

Prove release readiness

Install the built artifact through the user-facing distribution path. Verify setup, one live traced session, managed run, import or attach when supported, status or permalink output, and disablement without damaging unrelated agent configuration. Add a post-deploy smoke test where the channel permits it.

04 同仓库更多 Skills

braintrustdata
braintrustdata/braintrust-coding-agent-plugins

troubleshoot-braintrust-mcp

Diagnose Braintrust MCP connection issues.

★ 3
braintrustdata
braintrustdata/braintrust-coding-agent-plugins

braintrust

Use Braintrust for LLM evaluation, logging, and observability.

★ 3
braintrustdata
braintrustdata/braintrust-coding-agent-plugins

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.

★ 3
braintrustdata
braintrustdata/braintrust-coding-agent-plugins

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".

★ 3
braintrustdata
braintrustdata/braintrust-coding-agent-plugins

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.

★ 3
braintrustdata
braintrustdata/braintrust-coding-agent-plugins

add-coding-agent-setup

Add or review persistent setup for a coding-agent tracing integration, including public CLI exposure, plugin or hook installation, non-secret route configuration, idempotent updates, disablement, and isolated setup tests. Use when implementing or fixing the setup, install, enable, disable, or uninstall experience for an agent.

★ 3