How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/fellowship-dev/dogfooded-skills --skill evidence-uploadBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
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
- 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.




