Agent skill

flyio-webhooks-events

Implement Fly.io machine events, health check monitoring, and log-based event processing for deployment automation and alerting. '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flyio-webhooks-events --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 3 KB
Bundled scripts: none
Version: 1.6.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(fly:*)Bash(curl:*)
Requires: Designed for Claude Code
Path: plugins/saas-packs/flyio-pack/skills/flyio-webhooks-events/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Fly.io Events & Monitoring ## Overview Fly.io does not have traditional webhooks. Instead, monitor machine state changes via the Machines API, process structured logs via `fly logs`, and use health check endpoints for automated responses. ## Instructions ### Step 1: Poll Machine State Changes ```typescript // Monitor machine state transitions via Machines API async function watchMachines(appName: string, callback: (event: MachineEvent) => void) { const client = new FlyClient(appName, process.env.FLY_API_TOKEN!); const stateCache = new Map<string, string>(); setInterval(async () => { const machines = await client.listMachines(); for (const m of machines) { const prev = stateCache.get(m.id); if (prev && prev !== m.state) { callback({ machineId: m.id, region: m.region, previousState: prev, currentState: m.state, timestamp: new Date(), }); } stateCache.set(m.id, m.state); } }, 10_000); // Check every 10 seconds } interface MachineEvent { machineId: string; region: string; previousState: string; currentState: string; timestamp: Date; } ``` ### Step 2: Health Check Event Handler ```typescript // Implement health check that reports machine health // Fly.io uses this to auto-restart unhe

What's inside
Steps it walks through
  1. Overview
  2. Instructions
  3. Step 1: Poll Machine State Changes
  4. Step 2: Health Check Event Handler
  5. Step 3: Structured Log Processing
  6. Step 4: Deployment Event Notifications
  7. Resources
  8. Next Steps
Commands it runs
Stream logs and process with jq
fly logs -a my-app --json | jq -c 'select(.level == "error")' | while read -r line; do
echo "$line" >> errors.jsonl
done
Search recent logs for specific patterns
fly logs -a my-app --no-tail | grep -i "error\|crash\|oom"
Post-deploy notification in CI
fly deploy -a my-app && \
curl -X POST "$SLACK_WEBHOOK_URL" \
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the flyio-webhooks-events skill do?

Implement Fly.io machine events, health check monitoring, and log-based event processing for deployment automation and alerting. '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill flyio-webhooks-events --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going