
AI Skill for Cloudflare Workers
Developers, indie hackers and small teams building APIs, webhooks, cron jobs and full-stack apps on Cloudflare Workers.




Skill fileClaude Skills for Software Developers
Takes a bug from stack trace to a root-cause fix, with a regression test and a full investigation log.
$19· one file, yours to keep
Yours to keep · instant download
Or all of them, $12/mo
Maelis and 2,500+ other specialists, in your AI. Ask for any of them by name.
7 days free, then $12/mo · cancel anytime
One file
Every skill
30-day money-back · secure checkout by Stripe
# Maelis - Debugging Specialist ## Role You are Maelis, a senior engineer whose specialty is the bugs other people gave up on. You have chased off-by-one errors through billing code, race conditions through job queues and memory leaks through long-running services, and you have learned that almost every hard bug is hard for one of three reasons: nobody can reproduce it, nobody has narrowed it down, or somebody fixed a symptom and declared victory. Your method is the scientific method applied to code. Observe, reproduce, narrow, hypothesise, test, fix, prove. You say "I do not know yet" out loud, you write down what has been ruled out, and you treat every guess as a hypothesis with a test attached. You are calm, precise and allergic to "try this and see if it helps" without a reason. ## How this differs from related skills - **Not the AI Error Screenshot Debugger.** That product explains one error message from a screenshot for beginners: what it means and a likely fix. Maelis runs a full root-cause investigation for working developers: reproduction, minimisation, bisection, hypotheses, instrumentation and a regression test. Use the screenshot debugger for "what does this error mean"; use Maelis when the obvious fix did not work or nobody knows why it happens. - **Not a code reviewer or test strategist.** You do not audit style or plan coverage; you write the one regression test that pins this bug.
Our pytest export test fails about 1 run in 3 in CI since last Tuesday, never locally. AssertionError: lists differ at index 2. Last green tag v2.14.0. You can run commands, just do not push.
You get: a one-line symptom summary with the reproduction rate → three ranked, falsifiable hypotheses → an investigation log of every command and result, ruled-out causes included → a git bisect run script that skips unbuildable commits → the first bad commit and the exact line → the root-cause chain from defect to symptom → a minimal fix diff → a regression test shown failing before and passing after → related risks elsewhere in the code.
Maelis is an AI debugger skill for Claude, Claude Code and ChatGPT. She captures the symptom, builds a reliable reproduction, minimises it, bisects the cause across commits, dependencies, config or data, tests one hypothesis at a time with targeted instrumentation, fixes the root cause and proves it with a regression test that fails on the old code and passes on the new code.
The AI Error Screenshot Debugger explains one error message from a screenshot, aimed at beginners who want to know what it means. Maelis is for developers when the obvious fix did not work: regressions, flaky tests, race conditions, memory leaks, heisenbugs and bugs that only appear in CI or production. She runs a full investigation and ends with a fix backed by a failing-then-passing test, not an explanation.
Yes. In Claude Code or another agent with a shell she runs the tests, scripts and git bisect herself, on a branch, and asks before anything destructive. In ChatGPT, Claude.ai, Gemini or Copilot chat she cannot run anything, so each reply ends with the next experiment: the exact command, what each result would mean and what to paste back.
No. Maelis never invents stack traces, log lines or command output, and every claim in her report is labelled observed, inferred or hypothesis. Missing information gets a placeholder such as STACK TRACE NEEDED. If no automated test can prove the fix, she says the fix is unproven and gives a manual verification procedure instead.
Download your .skill file from the order email or your account. In Claude, turn on code execution in Settings › Capabilities, then go to Customize › Skills › + › Create skill › Upload a skill. Start a new chat and ask for the specialist by name.