outreach-status
Skill1 starsChanged 2 months agoMITView on GitHub
Report where the internship outreach stands for one or both people — what is sent, awaiting reply, due for follow-up, and the literal next action. Use when starting a session cold, or when asked "where are we" or "what's next".
In this repository37 other files it gives its agents.
- wsb-data-pipelineSkill
- docx-exportSkill
- harvard-mdxSkill
- humanise-docx-reportSkill
- make-pdfSkill
- bom-builderSkill
- ring-testSkill
- batch-draftSkill
- cold-emailSkill
- cv-intakeSkill
- cv-upgradeSkill
- find-contactSkill
- followupSkill
- humanize-emailSkill
- log-outreachSkill
- target-researchSkill
- erc-statusSkill
- log-sessionSkill
- score-auditSkill
- submission-checkSkill
- sumo-statusSkill
- trial-runSkill
- vr-statusSkill
- academic-registerSkill
- aviation-data-sourcesSkill
- business-frameworksSkill
- consultancy-registerSkill
- excel-deliverablesSkill
- forecasting-methodsSkill
- operations-frameworksSkill
- secondary-data-sourcesSkill
- archive-indexSkill
- event-proposalSkill
- meeting-minutesSkill
- read-boxnoteSkill
- captureSkill
- new-scriptSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Do the tracker rows match the files in sent/?
- Very specific: line 24
Say so explicitly where they disagree: If PROJECT_NOTES claims Phase 3 and shared/companies/ is empty, the project is in Phase 2.
- Very specific: line 67
If PROJECT_NOTES says a phase is done and the deliverable is not on disk, the phase is not done.
- Very specific: line 68
Never report a contact as verified when the tracker says pattern or unverified.
- Very specific: line 70
Senders in different fields do not share a target list: Never report one sender's state against another's targets.
≈ “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
/outreach-status, the honest snapshot
Usage: /outreach-status (both) · /outreach-status "<Person Name>"
Fast and honest. No encouragement, no padding.
Steps
- Read
.claude/PROJECT_NOTES.md— the phase tracker and next action are the stated position. - Check the stated position against what is on disk. Notes drift and stale notes mislead the next session:
- Does
<person>/cv/actually contain a CV, or is the profile still running on vault data? - Does
profile.mdstill containTBD? - How many files are actually in
drafts/versussent/? - Does
shared/companies/have real dossiers or empty stubs? - Does
shared/targets.mdhave real companies or only the seed list? - Do the tracker rows match the files in
sent/?
- Does
- Say so explicitly where they disagree. If PROJECT_NOTES claims Phase 3 and
shared/companies/is empty, the project is in Phase 2. - Compute what is due — spawn
followup_plannerif anything has been sent. - Report per person, then the shared state.
- Give exactly one next action. The plan lists everything; this skill picks the next thing.
Output format
## Outreach status — <date>
### Phase: <n, name> (<on track | behind | blocked>)
### <Person Name>
Profile: complete | TBD in <fields>
Sent: <n> · Awaiting reply: <n> · Replied: <n> · No-reply: <n>
Follow-ups due: <n>
In drafts: <n> (<statuses>)
### <Second Person>
<same>
### Shared
Targets: <n> (T1 <n> / T2 <n> / T3 <n>)
Dossiers written: <n>
Contacts verified: <n> of <n>
### Notes vs reality
<discrepancies, or "consistent">
### Blocked on
<what, and who has to unblock it>
## Next action (do this literally next)
<one concrete step>Rules
- One next action, not five.
- Respect phase discipline. Never suggest a Phase N+1 task while Phase N's deliverable does not exist.
- If PROJECT_NOTES says a phase is done and the deliverable is not on disk, the phase is not done. Say it.
- Never report a contact as verified when the tracker says
patternorunverified. - Report reply rates as they are. A zero reply rate after ten sends is information about the angle, and hiding it wastes the next ten.
- Senders in different fields do not share a target list. Never report one sender's state against another's targets. While a sender still has open questions in their
profile.md, lead with those.
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.

