value-audit
Skill0 starsChanged 7 months agoApache-2.0View on GitHub
Value-critical QA methodology for enterprise product demos. Evaluates products from skeptical buyer perspective — value propositions, value flow coherence, data credibility, narrative strength. Use when asking about 'value audit', 'demo readiness', 'demo critique', 'value flow', 'demo QA', 'client perspective', 'enterprise demo', 'value chain analysis', 'demo data', 'narrative coherence', or 'product story'.
In this repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- nodes-referenceSkill
- workflow-patternsSkill
- deployment-gitSkill
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- gold-standardsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- conversation-uxSkill
- uiux-design-principlesSkill
- ai-interaction-patternsSkill
- eatp-referenceSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 33
Every page, section, and element is interrogated with:
- Very specific: line 43
Use the value-auditor agent (.claude/agents/value-auditor.md) to run automated audits via Playwright MCP.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Value Audit Skills
Enterprise demo QA methodology that goes beyond functional testing to evaluate whether a product tells a compelling, credible story to skeptical enterprise buyers.
Quick Reference
| Skill File | Purpose | When to Use |
| value-audit-methodology.md | Full audit methodology, Five Questions framework, 3-level evaluation | Running a complete value audit |
| demo-readiness-checklist.md | Pre-demo verification with pass/fail criteria | Quick readiness check before a demo |
| value-flow-patterns.md | Common value flow patterns for enterprise AI platforms, anti-patterns | Analyzing or designing value flows |
| full-demo-audit.md | Combined technical + value audit orchestration (testing-specialist + value-auditor) | Running both technical and value QA in sequence |
Core Concept
Traditional QA asks: "Does it work?" Value Audit asks: "Does it sell?"
A product can pass every functional test and still fail a demo because:
- Pages show zero data (empty room problem)
- Features exist in isolation without connecting to the value story
- Metrics contradict the narrative (100% success with 0 completions)
- The transformation story (before → after) is missing
The Five Questions
Every page, section, and element is interrogated with:
- What is this FOR? — Business outcome, not feature description
- What does it LEAD TO? — Connection in the value chain
- Why do I NEED this? — What breaks if it doesn't exist
- How do I USE this? — Path from viewing to getting value
- Where's the PROOF? — Evidence it works, not promise it can
Related Agent
Use the value-auditor agent (.claude/agents/value-auditor.md) to run automated audits via Playwright MCP.
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
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.

