New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify All Deliverables

by HKUDS in HKUDS/OpenSpace

Ensure all required output files are created and verified before marking a task complete

MITAuto-check passedAgent Workflows

Install Verify All Deliverables

skills CLI
$ npx skills add HKUDS/OpenSpace --skill verify-all-deliverables -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenSpace verify-all-deliverables --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/verify-all-deliverables .claude/skills/verify-all-deliverables && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-all-deliverables
GitHub stars
7.8k
Token cost
~751 tokens
SKILL.md length
278 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Ensure all required output files are created and verified before marking a task complete

  • Works in 5 steps: Identify All Deliverables Upfront → Create Each Deliverable in Sequence → Verify Each File After Creation → …
  • Agent Workflows work in your project
  • SKILL.md covers Purpose, When to Use, Instructions and Common Pitfalls, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify All Deliverables is an agent skill from HKUDS/OpenSpace. Ensure all required output files are created and verified before marking a task complete

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

It sits in Agent Workflows. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/verify-all-deliverables”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify All Deliverables Upfront
  2. Create Each Deliverable in Sequence
  3. Verify Each File After Creation
  4. Final Verification Before Completion
  5. Only Then Declare Complete

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify All Deliverables loads about 751 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 278 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~751

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 278 words, ~751 tokens.

Download SKILL.mdSave it as .claude/skills/verify-all-deliverables/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
verify-all-deliverables
description
Ensure all required output files are created and verified before marking a task complete

Verify All Deliverables Before Completion

Purpose

This skill prevents premature task completion in multi-deliverable workflows by ensuring every required output file is created, verified to exist with non-zero size, and confirmed before declaring <COMPLETE>.

When to Use

Use this skill when a task requires creating multiple output files (e.g., spreadsheet + document, report + summary, data file + visualization).

Instructions

Step 1: Identify All Deliverables Upfront

CRITICAL CHECKPOINT: Do not proceed to Step 2 until this step produces visible output.

Before starting any file creation, you MUST output a complete deliverable list in this exact format:

REQUIRED DELIVERABLES CHECKLIST:
☐ [filename1.extension] - [brief description]
☐ [filename2.extension] - [brief description]
☐ [filename3.extension] - [brief description]

This checklist must appear as visible text in your output before executing any file creation commands. Track completion by updating checkboxes (☐ → ☑) as each file is created.

Step 2: Create Each Deliverable in Sequence

Execute the creation of each file one at a time. Do not proceed to the next step until the current file creation command has completed.

Step 3: Verify Each File After Creation

After creating each file, immediately verify it exists and has non-zero size:

bash
ls -la [filename.extension]

Expected output should show file size > 0 bytes. If size is 0 or file is missing, troubleshoot before proceeding.

Step 4: Final Verification Before Completion

Before declaring <COMPLETE>, run a final verification of ALL deliverables:

bash
ls -la file1.ext file2.ext file3.ext

Or use a loop for many files:

bash
for file in file1.ext file2.ext file3.ext; do
  if [ -s "$file" ]; then
    echo "✓ $file exists ($(stat -c%s "$file") bytes)"
  else
    echo "✗ $file missing or empty"
    exit 1
  fi
done
Step 5: Only Then Declare Complete

Only output <COMPLETE> after all files have been verified with non-zero size.

Common Pitfalls

PitfallPrevention
Creating only some deliverablesList all deliverables upfront and track completion
Not verifying file sizesAlways run ls -la after each file creation
Declaring complete too earlyFinal verification step is mandatory
Assuming success without checkingExplicitly check each file before proceeding

Example Workflow

Task: Create tracking spreadsheet and email template document

1. Identify deliverables:
   - June_2025_Declined_Payments_Outreach.xlsx
   - Email_Template.docx

2. Create spreadsheet → verify with ls -la → confirm size > 0

3. Create Word document → verify with ls -la → confirm size > 0

4. Final check: ls -la *.xlsx *.docx → confirm both files present

5. Only then: <COMPLETE>

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/verify-all-deliverables of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Verify All Deliverables next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify All Deliverables compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify All Deliverables this skillHKUDS/OpenSpace7.8k—~751Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k36 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 36 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from HKUDS/OpenSpace

All 199 skills in this repo

  • Audio Track Production Workflow

    HKUDS/OpenSpace

    Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.

    7.8k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Cascade Failure Recovery

    HKUDS/OpenSpace

    Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.8k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed

  • Sandbox Code Execution Fallback

    HKUDS/OpenSpace

    Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.

    7.8k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback

    HKUDS/OpenSpace

    A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.

    7.8k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback and Path Anchoring

    HKUDS/OpenSpace

    Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.

    7.8k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback E81068

    HKUDS/OpenSpace

    Fallback workflow for executing Python code when executecodesandbox fails repeatedly

    7.8k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Verify All Deliverables

What does Verify All Deliverables do?

Ensure all required output files are created and verified before marking a task complete. Verify All Deliverables is an agent skill from HKUDS/OpenSpace.

When should I use Verify All Deliverables?

Verify All Deliverables fits situations like: agent Workflows work in your project.

How do I install Verify All Deliverables in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill verify-all-deliverables -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/verify-all-deliverables in HKUDS/OpenSpace) into .claude/skills/verify-all-deliverables in your project. Claude Code loads it when a task matches its description.

How do I install Verify All Deliverables in Codex?

Run `npx skills add HKUDS/OpenSpace --skill verify-all-deliverables -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/verify-all-deliverables in HKUDS/OpenSpace) into .agents/skills/verify-all-deliverables in your project. Codex loads it when a task matches its description.

Can I use Verify All Deliverables in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/OpenSpace --skill verify-all-deliverables -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-all-deliverables, .gemini/skills/verify-all-deliverables, .github/skills/verify-all-deliverables and .opencode/skills/verify-all-deliverables in your project.

What does Verify All Deliverables need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify All Deliverables is instructions for the agent only.

Does Verify All Deliverables access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify All Deliverables safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verify All Deliverables use?

Verify All Deliverables is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify All Deliverables use?

About 751 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify All Deliverables?

Skills that share tags, products or a category with Verify All Deliverables: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify All Deliverables?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,754 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.