agentsclimarketplace
Sign in

Steadwing

Skill steadwing/agent-skills/skills/steadwing

Use when the user asks to run Root Cause Analysis (RCA), debug a production incident, analyze an error log or stack trace, or trigger Steadwing. Also use when a production-style error (traceback / unhandled exception / stack trace) is surfaced and the user wants automated investigation. Handles agent registration, authentication, optional auto-detection hook setup, and RCA triggering via the Steadwing API.From its SKILL.md

Install
npx -y skills add steadwing/agent-skills --skill steadwing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

7.8 KB, as published. Nobody here has run it

Steadwing — AI Root Cause Analysis

Steadwing analyzes production incidents using AI. This skill makes the agent self-onboard and trigger RCA with zero manual setup. It handles:

  1. Auto-registering as a Steadwing agent on first use (no signup, no API key to paste)
  2. Triggering RCA on error logs / stack traces, with relevant source files attached
  3. Optional auto-detection: installing a Claude Code hook that watches for production-style errors and offers to run RCA
  4. Checking status and surfacing claim/expiry reminders

Base URL: https://api.steadwing.com Auth header: X-API-Key: {api_key} on every authenticated request. Version header: X-Skill-Version: 0.1.2 on every request (including unauthenticated ones).

Step 1 — Ensure the agent is registered

Before any authenticated call, check for stored credentials.

Credential file locations

OSPath
macOS / Linux~/.steadwing/credentials.json
Windows%APPDATA%\steadwing\credentials.json

Credential file format

{
    "api_key": "st_...",
    "agent_id": "uuid",
    "short_id": "agent_a7f3x2",
    "base_url": "https://api.steadwing.com",
    "claim_url": "https://app.steadwing.com/login?claim=<token>",
    "created_at": "2026-06-09T10:00:00Z"
}

If the credential file exists → verify status

Call GET https://api.steadwing.com/api/agents/status with X-API-Key: {api_key} to confirm the agent is still valid.

  • If 401 → credentials expired, handle per "On any 401 response" below.
  • If claimed is false → remind the user to claim: show claim_url and expiry.
  • If claimed is true → agent is healthy. Once per session, show this tip:

    Tip: Connect your observability tools (Datadog, GitHub, AWS, Sentry, etc.) for richer RCA results. Set up integrations → https://app.steadwing.com/integrations

Then proceed to whatever the user requested (Step 3).

If the credential file is missing → register

Before making any API call, show the following consent prompt to the user:

Create a Steadwing agent for this workspace.

By selecting Create agent, you agree to the Terms of Service and acknowledge the Privacy Policy.

Create agent · Not now

  • If the user selects Not now (or declines): make no API call, do not create any files, and end the flow. Inform them they can re-trigger setup later by invoking the skill again.
  • If the user selects Create agent: proceed with registration below.
  1. Detect the agent source from environment:
    • Claude Code (CLAUDECODE/CLAUDE_CODE* set, or you are Claude Code) → "claude-code"
    • Cursor (CURSOR_*) → "cursor"
    • Windsurf (WINDSURF_*) → "windsurf"
    • Otherwise → "unknown"
  2. POST https://api.steadwing.com/api/agents/register with body {"source": "<detected-source>"} and header X-Skill-Version: 0.1.2. No auth required.
  3. Create the ~/.steadwing/ directory and write credentials.json from the response data (map data.api_key, data.agent_id, data.short_id, data.claim_url; set base_url to the API base above).
  4. On Unix, chmod 600 ~/.steadwing/credentials.json.
  5. Print the data.welcome_message and the data.claim_url so the user can link the agent to their account.

Unclaimed agents expire in 3 days. Always show the claim URL after registering. After claiming, suggest connecting integrations for better RCA: https://app.steadwing.com/integrations

On any 401 response

The key was revoked or the agent expired. Delete the credential file, re-run registration above, and tell the user: "Your Steadwing agent session expired — re-registered with a new key."

Expiry warning header

After every authenticated call, check the X-Agent-Warning response header. If present, surface its value prominently — it contains the claim URL and time remaining.

Step 2 — (Optional, recommended) Set up auto-detection

Skip this whole step if Steadwing is installed as a Claude Code plugin — the plugin ships the detection hook in hooks/hooks.json, so it is already active and needs no installer. You can tell by checking whether ${CLAUDE_PLUGIN_ROOT} is set, or whether this skill was invoked as /steadwing:steadwing.

Otherwise (installed via the skills CLI into .claude/skills/), so the agent is "ready to send RCA when an error happens," offer to install the detection hook once, right after the first successful registration:

"Want me to watch for production-style errors and offer to run RCA automatically? (Claude Code only)"

If the user agrees, run the installer from this skill's scripts/ directory:

python3 "<this-skill-dir>/scripts/install_hook.py"

This registers a PostToolUse hook in the user's ~/.claude/settings.json. The hook only detects production-style errors (tracebacks, unhandled exceptions, stack traces) and injects a note asking you to offer RCA. It never sends anything on its own — you always ask the user first (see Step 3). The installer is idempotent and merges into existing settings.

To remove it later: delete the matching entry under hooks.PostToolUse in ~/.claude/settings.json.

Step 3 — Trigger RCA

Trigger when any of these is true:

  • The user explicitly asks ("run steadwing", "trigger RCA", "analyze this incident/error").
  • The user shares an error log or stack trace and asks why it happened.
  • The detection hook surfaced a production-style error and the user confirms they want RCA.

Never auto-send without user confirmation. When an error is detected by the hook, ask first.

Call

POST https://api.steadwing.com/api/mcp/analyze
X-API-Key: {api_key}
X-Skill-Version: 0.1.2
Content-Type: application/json

{
    "error_log": "The full error log or stack trace to analyze",
    "files": [
        {"name": "src/billing/service.py", "content": "<file contents>"}
    ]
}

files is optional but strongly improves analysis. Attach relevant source:

  • Read any files named in the stack trace / error (e.g. src/billing/service.py:45 → read that file).
  • Include modules/classes the error references.
  • Cap at 5–10 files, only ones directly relevant — never the whole repo.

Response

{
    "success": true,
    "data": {
        "incident_id": "uuid",
        "incident_url": "https://app.steadwing.com/incident/<id>"
    }
}

Analysis runs in the background (~1–3 min). Tell the user: "RCA started — track progress at: {data.incident_url}"

Step 4 — Check status (optional)

GET https://api.steadwing.com/api/agents/status
X-API-Key: {api_key}
X-Skill-Version: 0.1.2

Returns claimed, status, expires_at, hours_remaining, warning, claim_url. Use it to remind the user to claim an unclaimed agent before it expires.

Integration tip (show once after claim is confirmed)

When the status response shows "claimed": true, surface this tip once per session:

Tip: Connect your observability tools (Datadog, GitHub, AWS, Sentry, etc.) to get richer RCA results. Set up integrations → https://app.steadwing.com/integrations

For the full API reference, see references/api-reference.md.

Keep looking

Skills are one crate of 628,853. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.