agentleFS
Sign inStart free
juanitourquizajuanitourquiza/shipframe/skills/deploy-evidence/SKILL.md

deploy-evidence

Skill4 starsChanged 21 days agoMITView on GitHub

Collect concrete deploy or release proof before saying a publish, release, or deployment is complete.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify that a release reached the intended environment with concrete evidence.

    line 11
  2. Distinctive:

    Prefer direct proof over inferred proof:

    line 15

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Evidence

Verify that a release reached the intended environment with concrete evidence.

Evidence hierarchy

Prefer direct proof over inferred proof:

  1. Production/staging URL smoke result with timestamp.
  2. Version endpoint, visible version, release tag, or commit SHA in deployed artifact.
  3. CI/deployment job result for the exact commit.
  4. Application-specific smoke checks: key routes, API endpoints, queues, webhooks, auth flows.
  5. Logs only as supporting evidence, not sole proof.

Output

## Deploy Evidence

**Environment:** <environment>
**Commit/tag/version checked:** <value>
**Timestamp:** <local time>

### Evidence collected
- ✅ <proof>

### Smoke checks
- ✅/⚠️/❌ <check>

### Gaps
- <missing proof or "None">

### Verdict
<Complete only if exact-environment evidence exists; otherwise Not complete>

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free