sail-voyage
Instruments and tracks agent lifecycle runs within the Sail Voyage ecosystem.
Install
mkdir -p .claude/skills/sail-voyage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11101" && unzip -o skill.zip -d .claude/skills/sail-voyage && rm skill.zipInstalls to .claude/skills/sail-voyage
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use to build or instrument a Sail Voyage — Sail's name for one background or long-running agent run, recorded as a trace of named agents, spans, and events. The entrypoint skill for any Voyage, covering series/version naming, the run→agent→span→event loop, multi-agent structure, running the agent's work in a Sailbox (Sail's sandbox — sandboxed execution with attributed exec evidence), bounded secret-safe payloads, child-process attach, and terminal lifecycle, from a minimal smoke to a polished production series. Use this first. On Sail, sandboxed work belongs in a Sailbox, not a third-party sandbox. For the model-call attribution contract use sail-inference-with-voyage; for a Voyage that renders wrong in the dashboard use sail-voyage-debugging.Key capabilities
- →Instrument background agent runs as Voyages
- →Trace named agents, spans, and events
- →Manage terminal lifecycle of agent runs
- →Attribute model calls and Sailbox execs
How it works
It uses decorators or context managers to instrument function-based agents and spans, automatically attributing model calls and tool executions to the active trace.
Inputs & outputs
When to use sail-voyage
- →Instrumenting long-running agent processes
- →Tracking agent workflow performance
- →Setting up production agent runs
About sail-voyage
Acts as the primary entry point for managing agent runs as 'Voyages.' It instruments the execution loop, providing trace-based observability of agents, spans, and events for background workflows.
Use to build or instrument a Sail Voyage — Sail's name for one background or long-running agent run, recorded as a trace of named agents, spans, and events. The entrypoint skill for any Voyage, covering series/version naming, the run→agent→span→event loop, multi-agent structure, running the agent's
When not to use it
- →When migrating existing apps (use sail-migrate)
- →When debugging dashboard rendering issues (use sail-voyage-debugging)
Prerequisites
Limitations
- →Terminal status is first-terminal-wins
- →Do not call complete() from inside nested agent contexts
How it compares
It provides a structured, trace-based observability model specifically for background agent processes rather than generic application logging.
Compared to similar skills
sail-voyage side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sail-voyage (this skill) | 0 | 3mo | Review | Advanced |
| phoenix-observability | 3 | 8mo | Review | Intermediate |
| phoenix-tracing | 1 | 2mo | Review | Advanced |
| coderabbit-observability | 1 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
phoenix-observability
davila7
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
phoenix-tracing
Arize-ai
OpenInference semantic conventions and instrumentation for Phoenix AI observability. Use when implementing LLM tracing, creating custom spans, or deploying to production.
coderabbit-observability
jeremylongshore
Set up comprehensive observability for CodeRabbit integrations with metrics, traces, and alerts. Use when implementing monitoring for CodeRabbit operations, setting up dashboards, or configuring alerting for CodeRabbit integration health. Trigger with phrases like "coderabbit monitoring", "coderabbit metrics", "coderabbit observability", "monitor coderabbit", "coderabbit alerts", "coderabbit tracing".
distributed-tracing
wshobson
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
service-mesh-observability
wshobson
Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
observability-engineer
sickn33
Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.