Incident and delivery toolkit
Three local, read-only tools for the hours after a failed build or an incident: find the first real cause of a failed CI run, merge logs from several systems into one timeline, and turn an npm or pip audit into an ordered fix plan. Each one runs on your machine, reads only the files you name and changes nothing. Needs Python 3.9+.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 3 skills unlock instantly in your library.
What's included
3 skillsCI failure triage for GitHub Actions, GitLab and Docker builds: finds the first real cause in a failed build log. Local and read-only.
Turns npm audit or pip-audit JSON into an ordered fix plan, from fix now to no fix available. Local and read-only.
Incident postmortem timeline: merges app, web, deploy and database logs into one timeline for your outage review. Local and read-only.
See it in action
Failed CI Run Triage
Example session with this skill installed
/ci-failure-triage ci-log.txt
- Read your context and instructions
- Compiled the failed ci run
Illustrative. Both logs are invented (not from a real project); the reports below are what the script prints.
Log 1: a container build that ran out of memory
CI FAILURE TRIAGE (12 lines read)
Failing step: [build 4/6] RUN npm run build
Most likely first cause: Out of memory (line 5, 1 matching line(s))
evidence: #9 45.11 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
next: Look at the memory the job had. Re-run once; if it repeats, raise the runner memory or lower parallelism.
All findings, in the order they appear:
- line 5 Out of memory x1 [[build 4/6] RUN npm run build]
#9 45.11 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
- line 11 Container build x1 [[build 4/6] RUN npm run build]
ERROR: failed to solve: process "/bin/sh -c npm run build" did not complete successfully: exit code: 134
Later findings (Container build) come after the first one and may be side effects of it. Fix the first, then re-run.
Lines that only say the step failed:
- line 12: ##[error]Process completed with exit code 1.
Limits: pattern matching on text. It cannot see what is missing from a truncated log, and a flaky failure and a real one can look the same. Credentials found in lines are masked.
Log 2: a test run that failed on a network error
CI FAILURE TRIAGE (10 lines read)
Failing step: Run npm test
Most likely first cause: Network or external service (line 7, 1 matching line(s))
evidence: FetchError: request to api.example.test/v1/profile failed, reason: read ECONNRESET
next: Check the status page of the service named in the line, then re-run once. Repeated failures point to a blocked host or a missing proxy setting.
All findings, in the order they appear:
- line 5 Test failure x2 [Run npm test]
FAIL src/api.test.js
- line 7 Network or external service x1 [Run npm test]
FetchError: request to api.example.test/v1/profile failed, reason: read ECONNRESET
A test failure is also present. If the cause above is an outside condition (network, timeout, memory), the test may have failed because of it: re-run once before changing code.
Lines that only say the step failed:
- line 9: npm ERR! code ELIFECYCLE
- line 10: ##[error]Process completed with exit code 1.
Limits: pattern matching on text. It cannot see what is missing from a truncated log, and a flaky failure and a real one can look the same. Credentials found in lines are masked.
Next steps
- Read the first finding, not the last line: the red exit code is only the symptom.
- Re-run once when the first cause is an outside condition (network, timeout, memory) before changing code.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads these skills and uses them on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.