Review an AI team's work against its acceptance criteria using collected evidence. Match requirements to task results or artifacts, distinguish verified facts from agent claims, and identify uncertainty or missing work before recommending completion.
Checks an AI team run against its acceptance criteria using the evidence bundle. Use when the user asks whether the work is done or correct, or before completing a run. Separates verified evidence from agent claims.
Run score Not tested
See how to installReviews an AI team's work against its acceptance criteria and collected evidence. For each criterion, it identifies a concrete task result or artifact reference that supports it. The report separates verified facts, agent claims, uncertainty, and remaining work so you can see the basis for a completion decision. It also reports the recorded budget without treating that figure as an enforced limit or an amount billed.
Use it when you want to check whether work assigned to an AI team is finished and whether its deliverables meet the agreed conditions. Before ending a run, it can check whether the supporting material backs up a claim of completion. Matching conditions to results also helps identify evidence that is still missing from the decision.
Uses the RuFlo AI Team connector, ruflo-ai-team, to retrieve information through team_get, task_list, memory_search, and evidence_export. It recommends completion only when every required criterion has evidence. You decide whether to complete the run.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Uses the RuFlo AI Team connector (server name ruflo-ai-team): the tools team_get, task_list, memory_search and evidence_export.
Retrieve the evidence bundle and compare each acceptance criterion with a concrete task result or artifact reference. Separate verified facts, agent assertions, uncertainty, and missing work. Report the recorded budget without presenting it as enforced or billed. Recommend completion only when every required criterion has evidence; the user decides whether to complete the run.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.