credible-claims skillA
credible-claims is agent-read markdown (skill) from pedrohcgs/claude-code-my-workflow: Research-brief + claim-record discipline for delegated or AI-assisted research work. Use when starting any substantive research task or long autonomous run (write the brief first), and when reporting results that will support a claim in a paper or decision (produce the claim record). Keeps faster execution from being confused with credible evidence..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Credible claims: the brief before, the record after Cheaper generation increases demand for scarce validation. The fix is two lightweight artifacts: a **research brief** that constrains what the system may do, and a **claim record** that constrains what may be reported. Applies to agents, workflows, sims, proof patches, data construction — anything delegated. ## Three standing rules 1. **Delegate only after inputs, boundaries, and completion criteria are clear.** No open-ended "make it better" runs. 2. **Require evidence, not confident conclusions.** Every delegated task returns inspectable evidence: locations, diffs, diagnostics, counts, failing cases, logs — never just "done/looks fine." 3. **Escalate anything that changes the economic object, the identifying assumptions, the inferential procedure, or the reporting language.** Those decisions return to the researcher (the user), always. A standing user ruling counts as a returned decision; record it. ## The research brief (before execution) One short block, written before launching the work: - **Question / target:** what exactly is being estimated, proved, built. …
Read the whole file at its exact version.
How to install
mdr add pedrohcgs/claude-code-my-workflow/credible-claims@git:20260821.6600333mdr add pedrohcgs/claude-code-my-workflow/credible-claims@sha256:19cab4a6f7b568e6Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_s76tja3l35gutpsb)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4371 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
pedrohcgs/claude-code-my-workflow · 1,598 stars · license MIT · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s76tja3l35gutpsb GET https://markdownregistry.com/api/v1/resolve?ref=pedrohcgs/claude-code-my-workflow/credible-claims GET https://markdownregistry.com/api/v1/blob/19cab4a6f7b568e6c419677b2d45afb61593efbe18f7fe5b03943d28024c572d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.