About evidence-upload
A workflow skill for publishing local evidence files through the Pylot asset lifecycle and returning the required reference or URL. It directs users to the repository playbook and pylot-cli rather than defining upload behavior itself.
Key features
- 01Checks repository evidence policy
- 02Uses pylot-cli Assets guidance
- 03Returns asset receipt and reference
- 04Treats upload issues as advisory unless gated
Use cases
- 01Publish an image or recording as evidence
- 02Return an asset reference for review
- 03Follow a repository’s evidence policy
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/evidence-uploadin Claude Code to confirm it loaded.
Details
From the project READMEevidence-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
- Read the owning repo's playbook and determine its evidence policy and the intended destination.
- Invoke or read
pylot-cli, then follow its Assets section exactly. It is the single source for supported actions, flags, retention, and upload transport. - 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-clias 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.
Comments
Markdown supported