call-ready
Skill2 starsChanged 56 days agoMITView on GitHub
Screener — decides whether a hot conversation is ready for a call by checking three things (pain, power, priority), then writes either the booking message or the one question that closes the gap. Use on hot replies, demo requests, or "is this worth a call".
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- campaign-launchSkill
- command-centerSkill
- competitor-watchSkill
- fit-checkSkill
- human-voiceSkill
- intent-radarSkill
- market-mapSkill
- message-writerSkill
- morning-briefSkill
- nudgeSkill
- outbound-briefSkill
- post-studioSkill
- priority-rankSkill
- reach-checkSkill
- reply-deskSkill
- social-warmupSkill
- what-worksSkill
- why-nowSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read the whole conversation with pastel_get_conversation.
- Very specific: line 28
Write the next message; run human-voice.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Call ready — Screener
House rules: ../command-center/shared/house-rules.md · Pastel tools: ../command-center/shared/pastel-tools.md
fit-check already judged the account. Here, only the conversation counts: what the person actually wrote.
Three checks
| Check | The question | Evidence |
| Pain | Did they describe, in their words, a problem we solve? | their sentence, quoted |
| Power | Can they decide, or bring in whoever does? | what they said about their role or team |
| Priority | Is there a reason to act soon — a deadline, a target, an event? | the date or event they mentioned |
- 3 of 3 → Book. Propose a call the way
outbound-brief.mdprefers, with its booking link if it has one. - 2 of 3 → Ask. One question aimed at the missing check.
- 0–1 → Keep talking. Answer what they asked, and ask about their situation; the call comes later.
Steps
- Read the whole conversation with
pastel_get_conversation. - Fill the three checks with evidence.
- Write the next message; run
human-voice. - Once a call is booked, prepare
mark_lead_status→PROCESSED.
Output
# Call ready? — [Person]
Decision: book | ask | not yet
Pain: "…"
Power:
Priority:
Next message:
> …
Booking link: [link] | [missing]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.