sara-email-projects
Skill0 starsChanged 8 months agoNo licenceView on GitHub
Sara is Kevin's DEFAULT agent for anything involving emails, meeting notes, or project updates. ALWAYS trigger this skill — even without mentioning Sara — when Kevin asks to: search emails, find an email, check meeting notes, get a project update, summarise where things are with a client, prepare for a meeting, check what's outstanding, see what Rex has been working on, check Rex's costs, review action points, check if something was done, ask about project spend, find out what a client owes him or what he owes a client, or anything involving email threads, Google Meet notes, or project status. Also trigger when Kevin says 'ask Sara', 'Sara check', 'get Sara on it'. Sara handles: Gmail search and thread reading, Google Meet meeting notes analysis, pre-meeting client briefings, Rex Balbao cost tracking, two-way action tracking (what Kevin owes clients AND what clients owe Kevin), task reminders, and project spend reporting.
In this repository56 other files it gives its agents.
- dec-data-specialistSkill
- deconetwork-catalogue-importSkill
- accessibility-reviewSkill
- architectureSkill
- code-reviewSkill
- context7-mcpSkill
- debugSkill
- deploy-checklistSkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- documentationSkill
- frontend-designSkill
- dev-fullstackSkill
- incident-responseSkill
- research-synthesisSkill
- standupSkill
- system-designSkill
- tech-debtSkill
- testing-strategySkill
- user-researchSkill
- ux-copySkill
- fin-finance-managerSkill
- fin-xero-invoice-pipelineSkill
- max-marketingSkill
- brand-reviewSkill
- campaign-planSkill
- competitive-briefSkill
- content-creationSkill
- draft-contentSkill
- email-sequenceSkill
- performance-reportSkill
- seo-auditSkill
- account-researchSkill
- call-prepSkill
- call-summarySkill
- competitive-intelligenceSkill
- create-an-assetSkill
- daily-briefingSkill
- draft-outreachSkill
- forecastSkill
- pipeline-reviewSkill
- brainstormingSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
39 rules. About 0 are common, 35 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈35
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.