Individual skill
signal-interpreter
Use this skill when interpreting a raw GTM signal — a business event or an intent spike — into relevance, meaning, strength, confidence, category, why-now, and open questions, before any tiering or routing happens. It is a pure interpretation layer with no side effects: it never assigns tiers, chooses actions, sends alerts, or writes memory.
skills/din-arbel/signal-interpreter/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 21,924 bytes
Read excerpt
# Signal Interpreter
_Pure interpretation layer for GTM signals — returns relevance, meaning, strength, confidence, category, why-now, and open questions. No tier math or memory writes. Runs before your tier-scoring stage._
---
## Template placeholders
- `{{COMPANY_NAME}}` — Your company's name.
- `{{ICP_DOMAIN}}` — The operational world your product lives in: the set of activities, asset types, workflows, and regulatory contexts where a prospect's signal becomes relevant to you. Define it as a concrete list, not a category label. E.g., for a digital-asset custody company: digital assets, stablecoins, treasury flows, tokenized assets, crypto/payment infrastructure, wallet governance, custody, compliance, cross-border settlement, and regulated financial services. Write yours with the same specificity — this list powers the Relevance Gate and every strength/confidence judgment below.
- `{{ICP_VOCABULARY}}` — The specific operational-complexity vocabulary of your domain, used to phrase business implications. E.g., for the same custody company: wallet governance, transaction policy, treasury movement, custody, compliance workflows, settlement operations, approval flows, key management.
Worked examples throughout use the digital-asset custody domain (the domain this skill was battle-tested in) — substitute your own everywhere.