Track tasks that require several output files with an upfront checklist, checks after each file is created, and a final review. Confirm that every required file exists and has a nonzero size before reporting completion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Ensure all required output files are created and verified before marking a task complete
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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>.
Use this skill when a task requires creating multiple output files (e.g., spreadsheet + document, report + summary, data file + visualization).
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.
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.
After creating each file, immediately verify it exists and has non-zero size:
ls -la [filename.extension]
Expected output should show file size > 0 bytes. If size is 0 or file is missing, troubleshoot before proceeding.
Before declaring <COMPLETE>, run a final verification of ALL deliverables:
ls -la file1.ext file2.ext file3.ext
Or use a loop for many files:
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
Only output <COMPLETE> after all files have been verified with non-zero size.
| Pitfall | Prevention |
|---|---|
| Creating only some deliverables | List all deliverables upfront and track completion |
| Not verifying file sizes | Always run ls -la after each file creation |
| Declaring complete too early | Final verification step is mandatory |
| Assuming success without checking | Explicitly check each file before proceeding |
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>
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.