subject-line-not-filtered
Skill0 starsChanged 4 months agoMITView on GitHub
Write subject lines that are concrete and specific — a real thing the reader would say out loud — not clickbait and not vague. Every email that needs to be opened. Cold outreach, follow-ups, anything competing in a full inbox.
In this repository29 other files it gives its agents.
- devils-advocate-first-passSkill
- load-bearing-assumptionSkill
- pre-mortemSkill
- reversibility-checkSkill
- three-option-framingSkill
- boundary-setting-declineSkill
- cold-intro-structureSkill
- customer-reply-tone-matchSkill
- quote-follow-upSkill
- end-of-day-reflectionSkill
- inbox-triageSkill
- project-scaffoldingSkill
- quote-drafting-from-notesSkill
- vendor-invoice-categorizationSkill
- competitor-pricing-extractSkill
- customer-voice-extractSkill
- source-verificationSkill
- tactic-extractionSkill
- vertical-landscape-scanSkill
- discovery-call-note-captureSkill
- lead-qualificationSkill
- objection-handlingSkill
- proposal-drafting-frameworkSkill
- stack-the-deck-closeSkill
- dont-be-a-chatbotSkill
- honest-hedgingSkill
- lead-with-the-actionSkill
- specific-over-genericSkill
- write-like-the-userSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Write it like a sentence the reader would actually say, not a marketing headline.
- Distinctive: line 22
No clickbait, no fake urgency, no all-caps, no "Don't miss out." Those train the reader to ignore you and train filters to bury you.
- Distinctive: line 24
If the email has one ask or one fact, put it in the subject: "Crew slot open the week of the 14th."
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Subject Lines That Get Opened
A subject line is a promise about what's inside. Make it concrete enough that the reader knows the email is for them, without the clickbait that gets it filtered or ignored.
The technique
- Be specific: name the thing the email is about — the job, the number, the date — not "Following up" or "Quick question."
- Write it like a sentence the reader would actually say, not a marketing headline.
- No clickbait, no fake urgency, no all-caps, no "Don't miss out." Those train the reader to ignore you and train filters to bury you.
- Shorter wins on mobile — the first 4–5 words carry it. Front-load the specific.
- If the email has one ask or one fact, put it in the subject: "Crew slot open the week of the 14th."
Do this, not that
Do: "Your supplement got approved — $3,100"
Don't: "IMPORTANT: Don't miss this exclusive opportunity!!! 🚨"
Why this works
The subject line is the only thing that competes for the open. Vague ones ("Touching base") give no reason to click; clickbait ones get the open once and the unsubscribe right after. A concrete, honest subject earns the open and sets up the email to be believed — the reader already knows you don't waste their attention.
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.

