agentleFS
Sign inStart free
jasoncastonjasoncaston/two-body-verify/skills/verify-claims/SKILL.md

verify-claims

Skill0 starsChanged 21 days agoMITView on GitHub

Run two-body-verify against a project and claims file, then report evidenced, unsupported, and contradicted claims without changing the project.

  • Installs packages

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before invoking the command, check for it and fail with the install instruction if it is unavailable:

    line 13
  2. Very specific:

    Treat $ARGUMENTS as exactly two paths: the project path and the claims file.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

The two-body-verify Python package is a prerequisite for this plugin. Install it before running the skill:

python3.11 -m pip install "git+https://github.com/jasoncaston/two-body-verify.git@v0.1.1"

Before invoking the command, check for it and fail with the install instruction if it is unavailable:

if ! command -v two-body-verify >/dev/null 2>&1; then
  printf '%s\n' \
    'ERROR: two-body-verify is not installed or not on PATH.' \
    'Install it with: python3.11 -m pip install "git+https://github.com/jasoncaston/two-body-verify.git@v0.1.1"' >&2
  exit 2
fi

Treat $ARGUMENTS as exactly two paths: the project path and the claims file. Run two-body-verify <project-path> <claims-file>. Do not edit the project. Return the score, each claim status, and every finding exactly as the command reports them.

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