New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify Artifact

by pedrohcgs in pedrohcgs/claude-code-my-workflow

Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands.

MITAuto-check: notesDocuments & Office

Install Verify Artifact

skills CLI
$ npx skills add pedrohcgs/claude-code-my-workflow --skill verify-artifact -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pedrohcgs/claude-code-my-workflow verify-artifact --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/verify-artifact .claude/skills/verify-artifact && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-artifact
GitHub stars
1.7k
Token cost
~1.2k tokens
SKILL.md length
611 words
Files
1
Skills in repo
59
Repo updated
First seen
Licence
MIT

At a glance

Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands.

  • Works in 5 steps: Rebuild from source, in one shell… → Integrity checks (mechanical, fast,… → Diff the derived artifact against its… → …
  • Tasks that involve Econometrics and empirical research
  • SKILL.md covers 1. Rebuild from source, in one…, 2. Integrity checks…, 3. Diff the derived artifact… and 4. Make the recipient prove…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify Artifact is an agent skill from pedrohcgs/claude-code-my-workflow. Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Rebuild from source, check integrity, diff the derived artifact against its source, and require the recipient to echo what they received. Use before sending a paper/PDF for review, shipping a release or replication package, handing files to a coauthor or collaborator, uploading anything to an external reviewer or model, or publishing. Prevents an entire review/QA cycle from being spent on defects…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Econometrics and empirical research. The repository describes itself as: A ready-to-fork Claude Code template for academics using LaTeX/Beamer + R. Multi-agent review, quality gates, adversarial QA, and replication protocols. The licence is MIT.

When your agent uses it

  • Tasks that involve Econometrics and empirical research

Example prompts

  • “/verify-artifact”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash, Write

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Rebuild from source, in one shell invocation
  2. Integrity checks (mechanical, fast, non-negotiable)
  3. Diff the derived artifact against its source
  4. Make the recipient prove what they got
  5. If findings look strange, suspect the artifact first

What it can do on your machine

Read from SKILL.md and the folder at commit ae72617. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Artifact loads about 1.2k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 611 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~146
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pedrohcgs/claude-code-my-workflow at commit ae72617, republished under its MIT licence (© pedrohcgs). 611 words, ~1,241 tokens.

Download SKILL.mdSave it as .claude/skills/verify-artifact/SKILL.md (or your agent's skills folder).
name
verify-artifact
description
Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Rebuild from source, check integrity, diff the derived artifact against its source, and require the recipient to echo what they received. Use before sending a paper/PDF for review, shipping a release or replication package, handing files to a coauthor or collaborator, uploading anything to an external reviewer or model, or publishing. Prevents an entire review/QA cycle from being spent on defects that exist only in the artifact, not in the work.
allowed-tools
Read, Grep, Glob, Bash, Write
metadata.protocol
data-lineage

Verify the artifact before it leaves

A review is only as good as the thing reviewed. If the artifact is corrupt, truncated, stale, or silently renumbered, a competent reviewer will return confident findings about defects that do not exist in your work — and you will spend a cycle chasing them. This is cheap to prevent and expensive to miss.

Rule: never send a derived artifact you have not diffed against its source.

1. Rebuild from source, in one shell invocation

Never send yesterday's build. Rebuild, then copy to the send location in the same command, so nothing can change underneath you.

Cloud-synced folders (Dropbox/iCloud/OneDrive) dehydrate files: a PDF can become 0 bytes or a partial copy between building and reading it. Symptoms: Syntax Error: Couldn't find trailer dictionary, a 70 KB file that should be 700 KB. Build-tool "up to date" messages are not evidence the file is intact — the tool checks timestamps, not content. Always stage to a local (non-synced) directory and verify there.

2. Integrity checks (mechanical, fast, non-negotiable)

  • Size and structure: byte size in the expected range; page/record/row count as expected.
  • It parses: open it with a real reader (pdfinfo, pdftotext, a JSON/CSV parser, unzip -t). A file that exists is not a file that works.
  • Sample the content: first and last page/record actually contain what you expect — truncation shows up at the end.
  • Unresolved markers: for documents, count ??, [cite], TODO, XXX, \ref{ leftovers, "Chapter ??"; for code/data, NaNs, empty cells, placeholder values.

3. Diff the derived artifact against its source

This is the step people skip and the one that pays. If you produced the artifact by transforming, excerpting, compressing, or subsetting, then enumerate what could have been lost and check it:

  • Labels/anchors/IDs: set of identifiers in source vs artifact. Anything defined in source and referenced but missing in the artifact is a break.
  • Numbering: removing a numbered object silently renumbers everything after it, so a citation that was "Lemma 10" becomes "Lemma 6" — every downstream reference now points somewhere plausible and wrong. Check numbering stability, not just presence.
  • Counts: sections, tables, figures, rows, functions, endpoints — before vs after.
  • Nested content: excerpting a block can remove statements nested inside it, not just the prose you meant to cut.

If you cut anything, leave a visible in-artifact note saying so, so a reviewer does not read an omission as a gap.

Show full SKILL.md (218 more words)Show less

4. Make the recipient prove what they got

Ask the reviewer (human or model) to state, at the top of their response, the exact filenames, page/record counts, and version they are reviewing. This catches stale caches, wrong attachments, and silent fallbacks to an older upload — failures that are otherwise invisible until the findings make no sense.

Use unique filenames per round (report_r6.pdf, not report.pdf). Repeated identical names invite the recipient's system to serve a cached earlier copy.

5. If findings look strange, suspect the artifact first

Before acting on a review, ask: could this finding be an artifact of what I sent? Signals: complaints about missing/undefined references, "sections appear truncated", "the proof ends mid-argument", numbering that does not match your copy, or objections to text you know is present. Re-verify the artifact before you re-verify the work. Applying "fixes" for artifact-induced findings actively damages correct material.

Minimum checklist

  1. Rebuild from source; stage to a local dir in the same shell command.
  2. Verify it parses; check size, counts, first/last content.
  3. Count unresolved markers — expect zero.
  4. Diff identifiers/numbering/counts against source; note any deliberate omissions in the artifact itself.
  5. Unique filename for this round.
  6. Require the recipient to echo filename + counts.

Cross-references

© pedrohcgs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/verify-artifact of pedrohcgs/claude-code-my-workflow.

Open the folder on GitHubat commit ae72617

Compare with similar skills

Verify Artifact next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Artifact compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Artifact this skillpedrohcgs/claude-code-my-workflow1.7k—~1.2kAutomated safety check: NotesMIT
Generate CodebookAperivue/medsci-skills333—~1.1kAutomated safety check: PassMIT
Tablebrycewang-stanford/Auto-Empirical-Research-Skills4.6k—~3.3kAutomated safety check: PassCustom licence
Fin Submit Checkcsmar432/finai-research109—~1.2kAutomated safety check: PassMIT
Fin Full Pipelinecsmar432/finai-research109—~5.1kAutomated safety check: PassMIT
Scholar Auto Researchjoshzyj/open-scholar-skill168—~21kAutomated safety check: PassCustom licence

Similar skills

  • Generate Codebook

    Aperivue/medsci-skills

    A skill your agent uses when a tabular dataset (CSV, Excel, Parquet, Stata, SAS) needs a data dictionary.

    333 GitHub stars~1.1k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed

  • Table

    brycewang-stanford/Auto-Empirical-Research-Skills

    Econometrics skill for creating publication-quality LaTeX regression and summary tables.

    4.6k GitHub stars~3.3k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed

  • Fin Submit Check

    csmar432/finai-research

    根据目标期刊要求，对论文进行投稿前全面检查，涵盖格式、引用、图表、数据可用性等所有投稿必需项. An agent skill from csmar432/finai-research.

    109 GitHub stars~1.2k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed

  • Fin Full Pipeline

    csmar432/finai-research

    经济金融研究端到端完整流程。从研究想法到可投稿论文，覆盖文献综述、想法生成、新颖性验证、实证方法设计、论文大纲、正文写作、图表生成、LaTeX编译和投稿前检查。

    109 GitHub stars~5.1k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed

  • Scholar Auto Research

    joshzyj/open-scholar-skill

    Stable, deterministic social-science research-paper pipeline from idea or data to verified manuscript, citations, replication package, and final md/docx/tex/pdf outputs.

    168 GitHub stars~21k tokensUpdated 22 days ago
    Documents & OfficeAuto-check passed

  • Referee2

    scunning1975/MixtapeTools

    Systematic audit and review by Referee 2. An agent skill from scunning1975/MixtapeTools.

    474 GitHub starsUsed in 2 repos~2.4k tokens
    Research & ScienceAuto-check passed

More from pedrohcgs/claude-code-my-workflow

All 59 skills in this repo

  • Devils Advocate

    pedrohcgs/claude-code-my-workflow

    Adversarial 5-7 question challenge to a deck's pedagogical choices — ordering, prerequisites, cognitive load, motivation.

    1.7k GitHub starsUsed in 2 repos~641 tokens
    Auto-check passed

  • Vaccinate

    pedrohcgs/claude-code-my-workflow

    Qualify a check before it is allowed to clear anything — prove it can detect the failure it is meant to catch.

    1.7k GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check: notes

  • Compile Latex

    pedrohcgs/claude-code-my-workflow

    Compile a Beamer LaTeX slide deck with XeLaTeX (3 passes + bibtex).

    1.7k GitHub starsUsed in 1 repo~492 tokens
    Auto-check: notes

  • Context Status

    pedrohcgs/claude-code-my-workflow

    Show current context status and session health. An agent skill from pedrohcgs/claude-code-my-workflow.

    1.7k GitHub starsUsed in 1 repo~613 tokens
    Auto-check: notes

  • Capture Environment

    pedrohcgs/claude-code-my-workflow

    Snapshot the computational environment for a replication package — detects the analysis stack (R / Stata / Python) and emits the right lockfiles (renv.lock + sessionInfo.txt, requirements.txt /…

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes

  • Checkpoint

    pedrohcgs/claude-code-my-workflow

    Save a structured state snapshot before stopping or handing off.

    1.7k GitHub stars~2.8k tokensUpdated 13 days ago
    Auto-check: notes

Categories

Questions about Verify Artifact

What does Verify Artifact do?

Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands. Verify Artifact is an agent skill from pedrohcgs/claude-code-my-workflow. Prove that the file you are about to send, publish, or hand off IS the thing you mean — before it leaves your hands.

When should I use Verify Artifact?

Verify Artifact fits situations like: tasks that involve Econometrics and empirical research.

How do I install Verify Artifact in Claude Code?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill verify-artifact -a claude-code`. Or copy the skill folder (.claude/skills/verify-artifact in pedrohcgs/claude-code-my-workflow) into .claude/skills/verify-artifact in your project. Claude Code loads it when a task matches its description.

How do I install Verify Artifact in Codex?

Run `npx skills add pedrohcgs/claude-code-my-workflow --skill verify-artifact -a codex`. Or copy the skill folder (.claude/skills/verify-artifact in pedrohcgs/claude-code-my-workflow) into .agents/skills/verify-artifact in your project. Codex loads it when a task matches its description.

Can I use Verify Artifact in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pedrohcgs/claude-code-my-workflow --skill verify-artifact -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-artifact, .gemini/skills/verify-artifact, .github/skills/verify-artifact and .opencode/skills/verify-artifact in your project.

What does Verify Artifact need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify Artifact is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash, Write.

Does Verify Artifact access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify Artifact safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Verify Artifact use?

Verify Artifact is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Artifact use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Artifact?

Skills that share tags, products or a category with Verify Artifact: Generate Codebook (Aperivue/medsci-skills, 333 stars), Table (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Fin Submit Check (csmar432/finai-research, 109 stars) and Fin Full Pipeline (csmar432/finai-research, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Artifact?

pedrohcgs (a GitHub user) maintains it in pedrohcgs/claude-code-my-workflow, which has 1,655 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on September 27, 2026.

Source: pedrohcgs/claude-code-my-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.