agentsclimarketplace

Verify task

Skill S3YED/appie-kit/skills/meta/verify-task

Build Your Own AI Employee. The complete starter kit for OpenClaw + Hermes Agent. 155 deduplicated skills, drag-and-drop workspace, case studies, install scripts.

Install
npx -y skills add S3YED/appie-kit --skill verify-task

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

MUST use after completing any multi-step task or project. Verifies completion against the original plan, checks quality criteria, and documents outcomes.

SKILL.md

2.3 KB, 506 tokens by cl100k_base, as published. Nobody here has run it

Verify Task

Overview

Confirm successful completion and document outcomes against the original plan.

When to Verify

  • All tasks from plan are marked complete
  • User asks "is it done?" or "did it work?"
  • Before declaring a project finished
  • After each checkpoint in long-running tasks

Verification Process

Step 1: Load Original Plan

Read the plan that was created by write-plan skill.

Step 2: Verify Each Checkpoint

Go through each checkpoint and confirm:

  • All tasks marked complete
  • Verification criteria met
  • Quality standards achieved

Step 3: Final Quality Checks

General quality criteria:

  • Output matches original goal
  • No obvious errors or issues
  • Documentation updated (if applicable)
  • User can use/access the result

Step 4: User Confirmation

"Verification complete. Final checks:

✓ All tasks from plan completed (X/Y)
✓ Quality criteria met
✓ [Specific checks]

[Preview/demonstrate result]

Does this meet your expectations? Any adjustments needed?"

Step 5: Document Completion

Save completion report to: memory/plans/YYYY-MM-DD-<project>-complete.md

Template:

# [Project] - Completion Report

**Date Completed:** YYYY-MM-DD
**Original Goal:** [from plan]
**Final Result:** [brief description]

## Completion Summary

| Metric | Planned | Actual |
|--------|---------|--------|
| Checkpoints | X | X |
| Tasks | Y | Y |
| Time | Z min | W min |

## Verification Checklist

- [x] All tasks complete
- [x] Quality criteria met
- [x] User approved

## What Was Delivered

[Description of final output]

## Blockers Encountered

1. [Blocker] → [Resolution]

## Lessons Learned

- [What worked well]
- [What to do differently next time]

Handling Issues

If verification fails:

Minor issues: Quick fixes, proceed Major issues: Return to doing-tasks or re-plan

Principles

  • Objectivity - Verify against the plan, not assumptions
  • Thoroughness - Check all criteria
  • Honesty - Report issues, don't hide problems
  • User-centric - Final approval comes from user satisfaction

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.