Skip to content
Diagnosis · Data

sign-receipt

Bind an off-runtime action claim to opaque evidence references in a signed Runx receipt without pretending Runx verified the external action

Sorting a stream of records into a picture

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 5 Oct 2026
On the repository’s main branch.

What it does

Record a bounded attestation about something that happened outside Runx so a later governed run can cite exactly what was claimed, by whom, on which evidence, and for what reliance scope. The native Runx receipt signature proves the attestation packet was sealed without later modification. It does not prove the external action itself happened.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs. It changes how your AI works; it does not bring code of its own.

    How we know

    Listed the 6 files in the skill’s folder on GitHub; none is a script or program.

  • No known risk pattern found

    Launch7’s automated check read all 6 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit 37f69a7 by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to runxhq/runx: 2026-10-05 (0 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

  • cve-audit

    Audit exact npm dependency versions against OSV through Runx native HTTP and emit replay-verified evidence with no unverified findings

    runxhqIncludes 3 scripts
  • github-sync

    Read or synchronize bounded GitHub issues, threads, and pull requests through the local authenticated gh CLI or any compatible hosted…

    runxhqIncludes 1 script
  • issue-to-pr

    Implement one bounded repository issue with normal host tools, prove the tested change through one scafld finalize wall, and optionally…

    runxhqIncludes 1 script
  • loop-orchestration

    Reference loop-orchestration example; a local loop host chains governed runx turns through receipts, budgets, context, and stop policy

    runxhqIncludes 3 scripts
  • nitrosend

    Operate a Nitrosend account through one governed Runx skill: inspect readiness and analytics, plan and apply campaign/flow/template/segment…

    runxhqIncludes 6 scripts