Skip to content
cccskills
FreePublished on GitHub

task-verification-checkpoints

Check deliverables before marking a task complete. Review the requested file format, confirm every reference file was used, and compare the result with the original request to catch omissions and work that misses the goal.

OriginalShow the original description

Verify output format, file coverage, and task alignment before completing

See how to install

Good for

  • Checking deliverables before submission
  • Reviewing coverage of multiple reference files
  • Verifying requested output formats
  • Checking revisions against the original request

Files included (2)

  • SKILL.md4.9 KB
  • .skill_id43 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Task Verification Checkpoints

Before declaring a task as <COMPLETE>, perform these verification checks to ensure the deliverable matches requirements and prevents wrong-task completion.

Overview

This skill prevents common failures where agents:

  • Create outputs in wrong formats (PDF vs PPTX vs DOCX)
  • Skip processing some reference files
  • Drift from the actual task requirements

Three Critical Checkpoints

Checkpoint 1: Output Format Verification

Question: Does the output file format match task requirements?

Actions:

  1. Re-read the task prompt for explicit format requirements
  2. Check file extensions of all output files
  3. Verify the actual file type matches the extension
  4. Confirm against any format specifications (e.g., "revised PDF report")

Example validation:

def verify_output_format(task_prompt, output_files):
    """Check if output format matches task requirements."""
    required_format = extract_format_requirement(task_prompt)  # e.g., 'pdf', 'pptx'
    
    for f in output_files:
        actual_ext = f.split('.')[-1].lower()
        if actual_ext != required_format:
            return False, f"Expected .{required_format}, got .{actual_ext}"
    
    return True, "Format verified"

Checkpoint 2: Reference File Coverage

Question: Were ALL reference/input files processed?

Actions:

  1. List all files mentioned in the task as inputs
  2. Confirm each was read/analyzed/used (check file access logs)
  3. Document which content from each file contributed to output
  4. Flag any unprocessed reference files

Example validation:

def verify_reference_coverage(task_files, accessed_files):
    """Ensure all reference files were actually processed."""
    missing = set(task_files) - set(accessed_files)
    if missing:
        return False, f"Unprocessed files: {missing}"
    return True, "All references processed"

Checkpoint 3: Task Alignment Verification

Question: Does the deliverable address the ACTUAL task prompt?

Actions:

  1. Re-read the original task description verbatim
  2. Compare output purpose against stated task goal
  3. Check for scope creep or task drift
  4. Verify the output solves the stated problem (not a different one)

Example validation:

def verify_task_alignment(task_prompt, output_description):
    """Confirm output addresses the actual task."""
    task_verbs = extract_action_verbs(task_prompt)  # e.g., 'review', 'revise', 'create'
    output_verbs = extract_action_verbs(output_description)
    
    if not set(task_verbs).issubset(set(output_verbs)):
        return False, "Output actions don't match task requirements"
    
    return True, "Task alignment verified"

Pre-Completion Checklist

Execute this checklist before marking ANY task complete:

def pre_completion_verification(task_prompt, output_files, reference_files):
    """
    Complete verification before declaring task done.
    Returns (success, message) tuple.
    """
    checks = []
    
    # Check 1: Format
    format_ok, format_msg = verify_output_format(task_prompt, output_files)
    checks.append(('Format', format_ok, format_msg))
    
    # Check 2: Coverage
    coverage_ok, coverage_msg = verify_reference_coverage(reference_files, get_accessed_files())
    checks.append(('Coverage', coverage_ok, coverage_msg))
    
    # Check 3: Alignment
    alignment_ok, alignment_msg = verify_task_alignment(task_prompt, get_output_summary())
    checks.append(('Alignment', alignment_ok, alignment_msg))
    
    # Report results
    all_passed = all(ok for _, ok, _ in checks)
    
    if not all_passed:
        print("❌ VERIFICATION FAILED - Do not mark complete")
        for name, ok, msg in checks:
            status = "✓" if ok else "✗"
            print(f"  {status} {name}: {msg}")
        return False, "Verification failed"
    
    print("✓ All verification checkpoints passed")
    return True, "Ready for completion"

When to Apply

Use this skill whenever:

  • Creating deliverables from input/reference files
  • Task specifies output format requirements
  • Multiple files must be processed/analyzed
  • Task involves transformation, revision, or synthesis
  • Always before any <COMPLETE> declaration

Common Failure Modes to Catch

Failure TypeExamplePrevention
Format mismatchCreated PPTX when PDF requestedCheckpoint 1
Incomplete coverageSkipped Photographs.zipCheckpoint 2
Task driftCreated new report instead of revising existingCheckpoint 3
Assumption errorsAssumed format without verificationAll checkpoints

Quick Reference

Before <COMPLETE>:
  □ Output format matches requirements?
  □ All reference files processed?
  □ Deliverable addresses actual task?
  
If ANY box unchecked → Do NOT complete, fix first.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill