secure-delivery
Skill51 starsChanged 2 months agoApache-2.0View on GitHub
Deliver reports with trusted recipient provenance.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Tcuzzo/backs-aios-skillstheir own version, first seen Nov 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Tcuzzo/backs-aios-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- secure-reportSkill
- secure-researchSkill
- siq-agent-securitySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Use after secure-report when the task authorizes report delivery.
- Very specific: line 11
Run the built-in SkillRunner.delivery.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use after secure-report when the task authorizes report delivery. Input is
DeliveryInput(contact) plus ReportArtifact; output is DeliveryResult in
the application contracts.
Run the built-in SkillRunner.delivery. Resolve the contact from the configured
trusted directory and gather the separately labelled MCP candidate through the
gateway. Record MCP data with SIQ Report/Select APIs. The model may select a
candidate; it cannot supply a provenance ID, upgrade trust, or approve delivery.
Bind the selected candidate's actual provenance reference to /recipient.
The SIQ binary produces authorization decisions; the model does not decide
safety. The directory uses existing TRUSTED_DATABASE assertions. MCP remains
untrusted even if it returns exactly the same address as the trusted directory.
A refusal ends delivery before the restricted tool executes.
The competition uses a controlled HTTP sink, not external email. Its transport requires a separate SIQ network authorization. Tool success remains REPORTED; only independently collected sink evidence can satisfy scoped Completion.
Validation: apps/secure-agent/tests/test_skills.py checks both recipient origins,
actual provenance references and no delivery executor entry on rejection.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.