Skip to content
cccskills
FreePublished on GitHub

zip-export-deliverable

Package a completed codebase or project directory into a ZIP deliverable. The skill adds a dedicated final step to check project files, create the archive, verify its existence, size, and contents, and explicitly report completion.

OriginalShow the original description

Ensures codebase deliverables are properly exported as ZIP archives through a dedicated finalization step

See how to install

Good for

  • Delivering a completed codebase as a ZIP file
  • Packaging a project directory for handoff
  • Checking that a ZIP deliverable was actually created

Files included (2)

  • SKILL.md3.0 KB
  • .skill_id36 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

ZIP Export Deliverable Finalization

Purpose

When a task requires delivering a codebase or project directory as a ZIP archive, this skill ensures the deliverable is actually created through an explicit finalization step, rather than assuming directory creation equals completion.

When to Apply

Use this skill when:

  • The task deliverable is a codebase, project, or directory structure
  • The deliverable must be exported or packaged as a ZIP file
  • You have already created the project files and directory structure

Common Pitfall

Do NOT assume that creating the project directory and files means the deliverable is complete. The ZIP archive itself must be explicitly created as a final step.

Step-by-Step Instructions

Step 1: Verify Project Structure

Before creating the ZIP, confirm all required files and directories exist:

ls -la ./project/
# or
find ./project -type f | head -20

Step 2: Create Dedicated Final Iteration

Add a final step/iteration specifically for ZIP creation. This should be a distinct action, not combined with other tasks.

Step 3: Execute ZIP Command

Run the zip command with recursive flag:

zip -r project.zip ./project

Or with a custom name:

zip -r <deliverable-name>.zip ./<project-directory>

Step 4: Verify ZIP Creation

Confirm the ZIP file was created successfully:

ls -lh project.zip
# Should show file size > 0
unzip -l project.zip | head -20
# Should list contents

Step 5: Report Completion

Explicitly confirm the ZIP deliverable has been created in your final response to the user.

Code Example

import subprocess
import os

def finalize_deliverable(project_dir="project", zip_name="project.zip"):
    """Create ZIP archive of project deliverable."""
    
    # Step 1: Verify project exists
    if not os.path.exists(project_dir):
        raise FileNotFoundError(f"Project directory {project_dir} not found")
    
    # Step 2: Create ZIP
    result = subprocess.run(
        ["zip", "-r", zip_name, f"./{project_dir}"],
        capture_output=True,
        text=True
    )
    
    if result.returncode != 0:
        raise RuntimeError(f"ZIP creation failed: {result.stderr}")
    
    # Step 3: Verify
    zip_size = os.path.getsize(zip_name)
    print(f"Created {zip_name} ({zip_size} bytes)")
    
    return zip_name

Checklist

  • All project files are created in the expected directory
  • A dedicated step is allocated for ZIP creation
  • zip -r <name>.zip ./<directory> command is executed
  • ZIP file existence and size are verified
  • Deliverable completion is explicitly confirmed to the user

Related Patterns

  • File creation should always include verification steps
  • Deliverables should be explicitly validated before marking tasks complete
  • Archive/export operations need their own iteration, not implicit completion

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