Package a completed codebase or project directory as a ZIP archive in a separate final step. Verify that the archive exists, inspect its contents, and report the file location with a brief contents summary.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
Apply this skill when:
Before starting work, identify if the task requires a ZIP export. Look for phrases like:
Finish creating all project files, directories, and content. Ensure:
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
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}
Confirm successful creation:
ls -la project.zip
unzip -l project.zip # List contents without extracting
Explicitly state that the deliverable has been packaged and is ready. Include:
| 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 |
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]
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.