Define when a file creation task is complete: the deliverable is saved, contains the required content, and uses the correct format and location. Verify those conditions, then report completion without searching for an unnecessary submission tool.
Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required
Review the instructions the agent will receive before you install.
This skill addresses a common misconception during document and file creation tasks: agents sometimes search for or attempt to use a submit_work, finalize, or similar tool after creating the deliverable. No such step is required. Task completion is achieved when the file is successfully created with the required content.
File creation = Task completion
When a task requests you to create a document, report, script, or any file-based deliverable, the task is complete once:
There is no additional submission, finalization, or confirmation step needed.
Use the appropriate file creation method for your task:
# For programmatic file creation
with open('deliverable.docx', 'wb') as f:
f.write(document_content)
# For shell-based creation
echo "content" > output.txt
Or use available tools like write_file, create_file, etc.
Confirm the file exists and contains expected content:
ls -la deliverable.docx
# or
cat output.txt
Once verification passes, the task is complete. Do not:
submit_work toolfinalize_task functionSimply report that the deliverable has been created successfully.
| ❌ Incorrect | ✅ Correct |
|---|---|
| Creating file, then searching for submit tool | Creating file, verifying, declaring done |
| Assuming a finalization API exists | Treating file creation as the final step |
| Adding unnecessary confirmation steps | Completing after successful write |
Task: "Create a negotiation strategy document covering BATNA, ZOPA, and timeline."
Correct Execution:
negotiation_strategy.docxNo reviews yet. Tell others what you thought.
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.
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.