deliverable-completion
Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required
- License 许可
- MIT
- 所属仓库
- HKUDS/AgentPilot
- 最近更新
- 2026-11-12
- Stars
- ★ 8.0k
- Forks
- 944
01 前言 Front Matter
- name
- deliverable-completion
- description
- Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required
02 资源文件 1
- 其他.skill_id36 B
03 SKILL.md 正文
Deliverable Completion Protocol
Purpose
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.
Core Principle
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:
- The file has been written to disk
- The file contains the required content
- The file is in the correct format and location
There is no additional submission, finalization, or confirmation step needed.
Execution Workflow
Step 1: Create the Deliverable
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.
Step 2: Verify Creation
Confirm the file exists and contains expected content:
ls -la deliverable.docx
# or
cat output.txt
Step 3: Declare Completion
Once verification passes, the task is complete. Do not:
- Search for a
submit_worktool - Look for a
finalize_taskfunction - Attempt to "upload" or "submit" the file elsewhere
- Add extra confirmation steps
Simply report that the deliverable has been created successfully.
Common Mistakes to Avoid
| ❌ 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 |
Example Task Flow
Task: "Create a negotiation strategy document covering BATNA, ZOPA, and timeline."
Correct Execution:
- Write the document content
- Save as
negotiation_strategy.docx - Verify file exists (~43KB, contains all sections)
- Report: "Negotiation strategy document created successfully"
- Task complete — no further action needed
When This Applies
- Document creation (.docx, .pdf, .md, .txt)
- Code file generation (.py, .sh, .js)
- Data exports (.csv, .json, .xlsx)
- Configuration files (.yaml, .toml, .ini)
- Any file-based deliverable
When This Does NOT Apply
- Tasks explicitly requiring external submission (e.g., "submit to API endpoint")
- Tasks requiring human review/approval workflows
- Tasks where the file is an intermediate step (not the final deliverable)
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.