Customer Commitment Validation

What it does

When your agent uses it

• Interpreting meeting outcomes
• Letters of intent
• Case-study offers
• Unclear next steps

Example prompts

• “/customer-commitment-validation”

Requirements

• Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

1. 1Restate the meeting context and what the team hoped would happen next.
2. 2Classify the outcome as commitment, advancement, rejection, weak interest, or
3. 3Identify what the other person gave up, if anything.
4. 4If the outcome is fuzzy, propose a concrete next ask that creates a decision.
5. 5If there was rejection, preserve the learning and decide whether it changes
6. 6If there was commitment, define the owner, date, success criteria, and follow

What it can do on your machine

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

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  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.

• Compatibility

  Codex, Claude Code, and other Agent Skills-compatible clients.

  From compatibility in the SKILL.md frontmatter.

Context cost

Customer Commitment Validation loads about 941 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 393 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~89

When it runs · the whole SKILL.md, loaded when a task matches

~941

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

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 hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its MIT licence (© hashgraph-online). 393 words, ~941 tokens.

name

customer-commitment-validation

description

Evaluate whether customer, sales, investor, partner, or product meetings produced real commitment and advancement instead of polite interest. Use when interpreting meeting outcomes, stalled leads, trial requests, letters of intent, preorders, warm intros, case-study offers, unclear next steps, or compliments after a pitch.

compatibility

Codex, Claude Code, and other Agent Skills-compatible clients.

license

MIT

metadata.version

0.1.3

metadata.displayName

Customer Commitment Validation

metadata.category

Marketing

metadata.tags

customer-discovery,sales,validation,startups,commitment

# Commitment Review

## Meeting
- Person/company:
- Context:
- Stage:

## Outcome
- Classification, evidence, currency given up:

## Interpretation
- What this proves / does not prove:
- Risks, missing decision makers, approval path:

## Next Ask
[A concrete ask that creates advancement or rejection.]

## Follow-Up
- Owner, deadline, success criteria:

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

Files

SKILL.md and 2 other files in plugins/LVTD-LLC/skills/skills/customer-commitment-validation of hashgraph-online/awesome-codex-plugins.

• SKILL.md
• agents/openai.yaml
• workflows/classify-meeting-outcome.md

Open the folder on GitHubat commit 16b4156