Works with the AI Agents you already use
batman
Evidence-driven engineering: investigate, design, challenge, review, and execute.
Free
batman
Example session with this skill installed
Investigate why the payment webhook is returning 500 errors in the staging environment. Use standard depth.
- Read your context and instructions
- Compiled the batman
I have investigated the payment webhook failure by tracing the request through api/webhooks/payments.ts and the associated staging logs.
Investigation Report: Payment Webhook 500 Error
| Category | Details |
|---|---|
| Observed Failure | HTTP 500 Internal Server Error during Stripe signature verification. |
| Causal Mechanism | The STRIPE_WEBHOOK_SECRET in the staging environment does not match the signing secret used by the Stripe CLI forwarder. |
| Evidence | logs/staging-api.log shows SignatureVerificationError at line 42. Local check confirms process.env.STRIPE_WEBHOOK_SECRET is undefined in the container environment. |
| Affected Path | POST /api/webhooks/payments -> stripe.webhooks.constructEvent(). |
| Status | Confirmed. The failure is consistent across all 12 recorded attempts in the last hour. |
Next steps
- Inject the correct
STRIPE_WEBHOOK_SECRETinto the staging environment variables. - Trigger a redelivery of the failed webhooks from the Stripe Dashboard to verify the fix.
- Add a startup check to the API to log a warning if webhook secrets are missing.
Connects securely to your tools. The creator never sees your data.
About this skill
Stop shipping code based on guesses or bloated proposals. This skill provides an evidence-driven engineering framework to investigate bugs, challenge complex plans, design minimal solutions, and execute verified changes.
What it does
- Investigate failures by tracing requests through code and logs to find causal mechanisms instead of symptoms.
- Challenge proposals by identifying hidden assumptions and comparing plans against simpler alternatives or existing code reuse.
- Design solutions that prioritize the smallest complete change with explicit failure handling and recovery paths.
- Execute implementation using minimal code that updates affected callers, tests, and settings while preserving unrelated work.
- Review changes by tracing required behavior through callers and dependencies to find missing work or broken paths.
How it works
- Choose a mode based on your current phase: investigate, challenge, design, review, or execute.
- Define depth as quick for narrow checks, standard for typical flows, or deep for broad risk analysis.
- Analyze evidence from source code, logs, and actual state to verify claims before suggesting any action.
- Follow protocols to separate facts from hypotheses and ensure every objection or plan is grounded in observable code.
Frameworks & tools
This skill is language-agnostic and works with any repository. It relies on access to source files, logs, and test suites to verify its conclusions.
Why this beats prompting it yourself
Generic prompts often lead to over-engineered solutions and hallucinated bug causes. This skill enforces a strict evidence-first protocol that requires every claim to be backed by source code or log traces, preventing speculative fixes and "just in case" abstractions.
Use cases
- Debugging intermittent production failures by reconstructing causal chains from logs.
- Refactoring a complex proposal to find a smaller, lower-risk implementation path.
- Reviewing high-stakes pull requests for edge-case failures and caller regressions.
- Implementing features that must integrate correctly with existing helper functions.
Known limitations
This skill remains read-only for investigation, design, and review tasks unless you explicitly authorize code changes. It requires clear access to repository context to provide evidence.
Stays read-only for investigation and review unless edits are explicitly requested. Requires access to logs or source to verify claims.
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 this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 day ago
- Free with an Agensi account
Requires