# Evidence Upload

> Use when publishing visual evidence through Pylot assets for a PR, issue, report, mission, or conversation.

- Skill: `fellowship-dev/evidence-upload` (Agent Skill)
- Install (CLI): `npx skillmds@latest add fellowship-dev/evidence-upload`
- Raw SKILL.md: https://api.skillmd.com/api/skills/fellowship-dev/evidence-upload/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing, AI & ML
- Author: fellowship-dev (https://skillmd.com/u/fellowship-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/fellowship-dev/evidence-upload

---


# evidence-upload

Publish a local image, recording, or other accepted evidence file through the
Pylot asset lifecycle and return the resulting reference or public URL.

## Workflow

1. Read the owning repo's playbook and determine its evidence policy and the
   intended destination.
2. Invoke or read `pylot-cli`, then follow its **Assets** section exactly. It is
   the single source for supported actions, flags, retention, and upload transport.
3. Return the receipt required by the destination, including the asset id and
   any reference needed by the reviewer or conversation.

If the repo playbook defines no Pylot asset policy, do not invent one. Use the
repo's accepted evidence host and state what was used.

## Critical Rules

- Use `pylot-cli` as the single source of truth; do not copy its commands into
  this skill or call Pylot gateway asset endpoints directly.
- An upload problem is advisory unless the owning repo explicitly makes evidence
  a gate. Report the missing evidence instead of concealing it or failing an
  otherwise valid PR.