Task Snapshot
Productivitytask-snapshotTask Snapshot is an Agent Skill for productivity published in the marin-community/marin repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Create stable commit or tag snapshots for task milestones, experiment results, and reproducible artifact links.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/marin-community/marin/blob/HEAD/.agents/skills/task-snapshot/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/task-snapshot, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Task Snapshot
Use this when a result, milestone, or handoff needs stable references that will remain valid as a branch keeps moving.
Snapshot Choices
- Use a commit link for ordinary task milestones.
- Use an annotated tag for meaningful experiment checkpoints, published numbers, or long-lived handoffs.
- Include only relevant files in the snapshot commit.
Snapshot Comment
When posting a snapshot to an issue or PR, include:
- Commit or tag link.
- Pinned GitHub tree/file links for logbooks, benchmark outputs, configs, and reports.
- Exact command(s).
- Relevant details like: hardware/cluster and device count; critical, durable, non-secret environment variables; primary comparison table or a link to W&B/report artifacts.
Pinned GitHub tree links should include the commit or tag, for example:
https://github.com/marin-community/marin/tree/<commit-or-tag>/.agents/logbooks/foo.md
Prefer to use anchor text, even if it's just the filename.
Validation
Before presenting a snapshot as evidence:
- The command is reproducible from the snapshot.
- Shapes/configs and environment are explicit.
- The logbook and issue link to the same result.
- Dense data has an artifact, W&B, or dashboard link.