zip-deliverable-finalization
Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- zip-deliverable-finalization
- description
- Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step
02 资源文件 1
- 其他.skill_id42 B
03 SKILL.md 正文
ZIP Deliverable Finalization
Purpose
When a task requires delivering a codebase or project directory, do not assume that creating the project structure equals completion. A dedicated final iteration must explicitly package the deliverable as a ZIP archive.
When to Apply
Apply this skill when:
- The task involves creating a codebase, project, or multi-file deliverable
- The output should be exportable or downloadable
- A ZIP archive is the expected or implied deliverable format
Steps
1. Recognize Deliverable Requirements
Before starting work, identify if the task requires a ZIP export. Look for phrases like:
- "export as ZIP"
- "package the project"
- "deliverable archive"
- "downloadable codebase"
- Any mention of sharing, exporting, or distributing the project
2. Complete All Project Work First
Finish creating all project files, directories, and content. Ensure:
- All code files are written and saved
- All configurations are in place
- All documentation is complete
- The project structure is finalized
3. Create Dedicated Final Iteration
Do NOT combine ZIP creation with file creation. Allocate a separate, explicit iteration for packaging:
Iteration N: [File creation and project setup]
Iteration N+1: [ZIP packaging and finalization] <-- Dedicated step
4. Execute ZIP Command
Run the ZIP command explicitly in the final iteration:
zip -r project.zip ./project
Or for a custom project directory name:
zip -r {project-name}.zip ./{project-name}
5. Verify the Archive
Confirm successful creation:
ls -la project.zip
unzip -l project.zip # List contents without extracting
6. Report Completion
Explicitly state that the deliverable has been packaged and is ready. Include:
- Confirmation that ZIP was created
- Location of the ZIP file
- Brief summary of contents
Common Mistakes to Avoid
| Mistake | Correct Approach |
|---|---|
| Assuming file creation = deliverable complete | Explicitly create ZIP in separate step |
| Combining ZIP with file edits | Dedicate final iteration to packaging only |
| Forgetting to verify ZIP was created | List and confirm archive contents |
| Not mentioning ZIP in final report | Explicitly confirm deliverable is packaged |
Example
Task: Create a smart contract project and deliver as ZIP
Correct Execution:
Iteration 1: Create contract files, tests, and configs
Iteration 2: Create frontend components
Iteration 3: Run 'zip -r smart-contract-project.zip ./smart-contract-project'
Iteration 4: Verify and report: 'Deliverable packaged successfully'
Incorrect Execution:
Iteration 1: Create all files and mention "project is complete"
[No ZIP step - deliverable incomplete]
Notes
- This pattern applies to any multi-file deliverable requiring archival
- The dedicated iteration approach ensures the packaging step is not overlooked
- Always verify the ZIP exists before marking task complete
04 同仓库更多 Skills
agentpilot
Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.
remember
Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.
skill-discovery
Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.
delegate-task
Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.