signal-to-sequence
Skill0 starsChanged 48 days agoMITView on GitHub
Convert a normalized signal into a short outbound path without auto-enrolling anyone. After signal-scout ranks a trigger and account-mapper confirms a persona. Plans are artifacts for human approval. Hooks must keep irreversible enrollment fenced.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- KarlRaf/gtm-starter-kittheir own version, first seen Apr 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- KarlRaf/gtm-starter-kit★ 213same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clay-table-designSkill
- competitor-teardownSkill
- deploy-surface-checkSkill
- fde-handoff-packSkill
- hermes-herdr-loopSkill
- icp-scorecardSkill
- jev-typesafe-briefSkill
- n8n-flow-scaffoldSkill
- trigger-job-patternSkill
- weekly-pipeline-pulseSkill
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 7
After signal-scout ranks a trigger and account-mapper confirms a persona.
- Very specific: line 16
Write plan to ops/<slug>/sequences/<signal-id>-plan.md.
≈ “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
Skill: signal-to-sequence
Convert a normalized signal into a short outbound path without auto-enrolling anyone.
When to use
After signal-scout ranks a trigger and account-mapper confirms a persona.
Steps
- State the signal in one sentence with date and source.
- Pick persona and channel.
- Choose sequence shape: 1-touch bump, 3-step light, or research-heavy custom (default: 3-step light).
- Draft step intents (not full copy unless outreach-drafter is invoked): day 0 hook, day 3 value, day 7 break-up or proof.
- List enrollment criteria and kill criteria.
- Write plan to
ops/<slug>/sequences/<signal-id>-plan.md.
Guardrail
Plans are artifacts for human approval. Hooks must keep irreversible enrollment fenced.
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.

