pay-signal
Use when deciding whether a need is worth building on, when someone asks "is there real demand for this", "should I build this", "would people pay for this", "validate this idea", "is this market worth entering", "check whether this is just noise", "how do I know people actually want this", or when a feature request or an upvote thread is being treated as evidence that a product should exist. Separates stated preference, which costs its speaker nothing, from revealed preference, which costs money, migration effort or a private workaround, and reports which needs have no verified position rather than ranking them anyway. Does NOT predict revenue, price or willingness to pay; those need a transaction.
- Version
- 1.0.0
- License
- MIT
- Compatibility
- linux, macos, windows
Pinned to revision cdbd705c8b3e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/pay-signal/SKILL.md
- skills/pay-signal/backlog.json
- skills/pay-signal/fixtures/corpus.json
- skills/pay-signal/instrument/pay_signal.py
- skills/pay-signal/ledger.json
- skills/pay-signal/references/limits.md
- skills/pay-signal/references/traps.md
- skills/pay-signal/scripts/check_traps.py
- skills/pay-signal/scripts/elohim_run.py
Every link opens the file at its source, pinned to the revision this page describes.