Today’s Skill: Assign a Fixed Disk Path to Every Agent Task

Today’s recommended skill is simple yet effective: assign a fixed disk storage path to every agent task.

Many agent tasks fail not because the model is incapable, but because the delivery criteria are too vague. For instance, “write a popular science article” may sound clear, but it provides no concrete acceptance criteria for the system. A better approach is to specify: “Save the draft to `/reports/daily-pipeline/drafts/science-xxx.md`. The file must include frontmatter, titles in three languages, abstracts in three languages, the main body, a risk checklist, and next steps.” Upon task completion, the controller must execute `ls -la` and `wc -l` to verify the output.

This practice applies to all tasks that produce tangible artifacts: documents, reports, SQL drafts, QA conclusions, cover manifests, and release checklists. It is not suitable for pure discussions or brainstorming sessions, where conversational flexibility should be preserved. However, once a task moves into the execution phase, instructions should shift from “please complete this” to “please write to this specific file so that the host system can verify it.”

Recommended guidelines:

• Assign only one primary output path per task.
• The output path must be an absolute path.
• Filenames should include the date, task name, and track.
• Specify minimum byte count or line count in the brief.
• Success criteria must include raw output from host-side `ls` and `wc` commands.
• The agent’s natural-language summary should serve only as supplementary explanation, not as primary evidence of passing.

The value of this skill lies in reducing ambiguity and disputes. No file means the task is incomplete; a file that is too small fails quality standards; a file that exists but contains weak content proceeds to QA. With clear boundaries, team collaboration becomes significantly smoother and more efficient.