jeffrschneider/agentcatalog/agree-the-terms-of-a-proof

Claude Code and agent skill by jeffrschneider/agentcatalog

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Decides whether the buyer needs to see the thing work on their own data. Use it when running `ref/sls/run-a-proof-of-value` and `ref/sls/shape-the-solution`.

Install

npx vskill@latest install jeffrschneider/agentcatalog/agree-the-terms-of-a-proof

SKILL.md

The same SKILL.md was published earlier as jeffrschneider/agentcatalog/agree-the-terms-of-a-proof.

Agree the terms of a proof

What it does

Decides whether the buyer needs to see the thing work on their own data. If they do, the terms are settled in writing before anything is built: what counts as a pass, who does what on each side, and which data and which access the proof runs on.

Where it happens

The agent does this in five activities across two reference processes. Each one names the activity as that process words it.

  • Agree the Data and the Access
  • ref/sls/run-a-proof-of-value, activity 5 -

Run a Proof of Value

  • Agree the Success Criteria
  • ref/sls/run-a-proof-of-value, activity 2 -

Run a Proof of Value

  • Decide Whether a Proof Is Needed
  • ref/sls/shape-the-solution, activity 13 -

Shape the Solution

  • Decide a Proof Is Warranted
  • ref/sls/run-a-proof-of-value, activity 1 -

Run a Proof of Value

  • Name Who Does What
  • ref/sls/run-a-proof-of-value, activity 4 -

Run a Proof of Value

What to record

The shape at a version, with what the prior shapes for similar problems taught. The separation of what ships now from what is committed and what is only planned, with the source of each line. Every specialist reading: who read it, what they said, and when. The build gap written as work rather than as a promise. The cut, naming what came out and who signed it. The requirement map, with a reason attached to every refusal, seen by the buyer before they see the shape. The buyer's corrections in the buyer's words. Every change after agreement raising the version and going to everyone holding the old one. For a proof: the pass criteria agreed in writing before anything was built, the two dates, the named people on both sides, the line-by-line score with its evidence, and what the result corrected in the shape.

That contract covers every activity this abstract agent takes on, and it is repeated in com.agentcatalog.agent/RECORDS.md. What the abstract agent does not do is in com.agentcatalog.agent/NOT.md.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/jeffrschneider/agentcatalog/agree-the-terms-of-a-proof/badge)](https://verified-skill.com/skills/jeffrschneider/agentcatalog/agree-the-terms-of-a-proof)

Something wrong with this skill or its page? Tell us.