Results for “verification”

Organizes email triage, drafting, sending, and verification workflows with evidence-first reporting for mailbox operations.

Loads an implementation plan, executes tasks in batches with verification, and reports progress for review between batches.

Enforces evidence-based debugging, safety gates, and verification before every change to keep AI work correct and honest.

Load a written implementation plan, execute each task with verification checkpoints, and complete development using a structured workflow.

Automate Mailcheck email verification tasks through Composio's Mailcheck toolkit via Rube MCP, with tool discovery and connection management.

Executes approved Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence.

Provides a safe strategy for writing and editing large files to avoid truncation, including size thresholds, verification steps, and fallback recovery methods.

Comprehensive verification workflow before merging changes to production.

Self-referential loop until task completion with architect verification

Governs unattended automation workflows with mandatory budgets, dry-run defaults, and a separate verification gate before any side effect.

Guides the creation, editing, and verification of agent skills using a test-driven development approach, with structured documentation and quality gates.

Self-referential loop until task completion with configurable verification reviewer

Enforces safety gates, evidence-based debugging, anti-slack detection, and verification hooks when AI modifies files, configs, or deployments.

Create detailed phase plan (PLAN.md) with verification loop

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Verify an artifact that is about to leave the building — a partnership brief, pitch page, press release, customer email, RFP response, or any document sent to someone outside the org. Runs six checks before send — premise, confidentiality forward-test, evidence class, cold read by recipient personas, AI read, and tone metrics — and returns what to change with replacement copy. Use before sending anything outward-facing that carries customer detail, factual claims about a counterparty, or an ask.

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

Install, update, and manage the Hermes One desktop app via the `hermesone` npm package. Detects OS/arch, downloads verified releases, and installs with sha512 checksum verification.

Diagnoses and fixes failing installed skills by reading the SKILL.md and error output, classifying the failure, applying the smallest fix, and attaching a verification recipe.

Creates a temporary bot email address and checks its inbox via API, useful for testing signup flows, receiving verification codes, and automating email workflows.

Orchestrates the full academic research pipeline from exploration to final manuscript, coordinating research, writing, integrity verification, peer review, revision, and finalization stages with user confirmation checkpoints.

Visual verification workflow for UI changes to accelerate code review and catch ...

Organize email inbox, draft replies, send messages, and verify delivery with evidence-based confirmation.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.

Persists through implement-verify-fix loops until a task is fully completed and verified, overriding default stopping behavior.