fit-check
Skill2 starsChanged 57 days agoMITView on GitHub
Gatekeeper — answers yes, maybe, or no for each lead against the outbound brief, using Pastel's match reasons, and shows the reason so the user can overrule it. Use on any list before research or writing, for "are these a fit", or to clean a lead list.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Mahashwetha/Job-search-email-system-claudetheir own version, first seen Nov 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mahashwetha/Job-search-email-system-claude★ 12same 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- buying-committeeSkill
- call-readySkill
- campaign-launchSkill
- command-centerSkill
- competitor-watchSkill
- 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
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read Pastel's match reasons with pastel_get_details (five at a time), then:
≈ “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
Fit check — Gatekeeper
House rules: ../command-center/shared/house-rules.md · Pastel tools: ../command-center/shared/pastel-tools.md
Pastel already scored each lead against the ICP definitions. This skill adds the user's own brief on top, and makes every verdict readable.
Three gates
Read Pastel's match reasons with pastel_get_details (five at a time), then:
- Account gate — would this company appear in the market map? Sector, headcount, and country inside the lines; not a current customer; not on the off-limits list.
- Person gate — is this role close to the problem we solve? Read what the headline says they work on, not just the title: a "Head of Partnerships" rarely touches the tools a sales-tooling product replaces, even at the right company.
- Timing gate — is the signal still alive? Activity older than 60 days, or a role change older than 6 months, closes the gate unless something newer reopens it.
Yes = all three open → why-now. No = a gate is closed. Maybe = a gate can't be judged from what Pastel holds → listed separately with the one question that would settle it, for the user to decide.
Each verdict shows its reason in one line, so the user can overrule any of them at a glance. For the no group, prepare one batched mark_lead_status → NOT_INTERESTED request, sent after approval.
Output
# Fit check — [date]
Yes: n · Maybe: n · No: n
| Person | Company | Account | Person | Timing | Verdict | Reason |
Maybe — needs your call:
- [Person]: [the open question]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.

