メニュー
Use when scoring a signal from weirdness_ledger.md or source_map.csv using the 0-16 demand quality rubric, or when the user asks how strong a signal is.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/az9713/early-market-signal --skill ems-scoreコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when reviewing accumulated signals to group repeated pains, identify which are noise versus interview candidates, and decide what to kill or promote to thesis. Use after 10 or more ledger entries exist.
Use when a signal has been validated through interviews showing urgency, to draft a specific priced manual offer that tests willingness to pay before building any software.
Use when reviewing all open signals to assign a definitive next action to each one, or when signals are accumulating without clear decisions. Use after a scan session or scoring batch.
SKILL.md を表示中
SOC 職業分類に基づく
| name | ems-score |
| description | Use when scoring a signal from weirdness_ledger.md or source_map.csv using the 0-16 demand quality rubric, or when the user asks how strong a signal is. |
Scores a named signal using the 0-16 rubric. Bases the score only on evidence already captured in source_map.csv and weirdness_ledger.md. Updates signal_scorecard.csv with the result and reasoning.
Score each criterion 0, 1, or 2:
0: absent1: weak or occasional2: repeated and strong| Criterion | What to Look For |
|---|---|
| Rough UX tolerated | Users stay despite bad product quality |
| User tutorials | Unprompted explainers, guides, scripts |
| Incumbent replacement | Old tool or process being abandoned |
| API/integration requests | Users asking for connections to other tools |
| Hacked use cases | DIY workflows, forks, templates, scripts |
| Vocabulary forming | New terms appearing before category names |
| Copycats appearing | Multiple tools claiming to solve the same thing |
| Outside curiosity growing | Non-users asking how the behavior works |
| Total | Meaning | Next Action |
|---|---|---|
| 0-4 | Probably noise | ignore |
| 5-8 | Watchlist | watch |
| 9-12 | Early market candidate | interview users |
| 13-16 | Serious founder attention | interview / test concierge offer |
weirdness_ledger.md and source_map.csvsignal_scorecard.csvSignal: [ID and name]
Score: [X/16] — [interpretation]
Criterion scores:
- Rough UX tolerated: [0/1/2] — [reason]
- User tutorials: [0/1/2] — [reason]
- Incumbent replacement: [0/1/2] — [reason]
- API/integration requests: [0/1/2] — [reason]
- Hacked use cases: [0/1/2] — [reason]
- Vocabulary forming: [0/1/2] — [reason]
- Copycats appearing: [0/1/2] — [reason]
- Outside curiosity growing: [0/1/2] — [reason]
Assumptions or gaps: [list]
Next action: [ignore / watch / interview users / test concierge offer]