I will add an answer check to your claude or ai workflow and test it

I
ilya_shk
I
ilya_shk
Ilya S.

About this gig

An AI workflow that runs is not the same as one that is right. A figure can come from the wrong rows, a caveat can go missing, and the answer still looks finished.


I add a checking step to your workflow: after your AI writes an answer, a reviewer model and, where there are figures, scripts read it before anyone relies on it. A wrong answer is sent back or flagged.


Then I show the step works on your own answers: I take answers you consider correct, plant one mistake per copy (a wrong figure, the wrong rows counted, a lost caveat, a claim no figure supports) and record which check stops each.


In my own workflow: 24 mistakes of 7 kinds. The figure check stopped 6, the coverage check 5, and a reviewer model named all of the other 13 in 3 runs each. Stopped by nothing: 0.


Built and tested in Claude workflows (Claude Code, skills). For an app on another model I hand over the check as a script with setup notes, and you add your own API key.


You get the checks, the planted set, the results and what is still not covered. All in writing, no calls.

Get to know Ilya S.

Ilya S.

I test and fix what AI built: apps, Claude skills, AI answers

  • FromUkraine
  • Member sinceSep 2026
  • Languages

    Russian, Ukrainian, English
I work where AI output has to hold up. Apps built with AI (Lovable, Bolt, Replit, Claude): I find the bugs that change money or leak data, write a failing test for each, fix them and check the fixes again. Claude skills and plugins: built or fixed, with tests run before and after. AI answers: a checking step added to your workflow and tested with mistakes planted on purpose. In my own test, 24 planted, 0 missed. Month-end numbers from Claude, counted your way. All in writing, no calls. You send code or files, never passwords.

My Portfolio