job-function-audit
Skill0 starsChanged 3 days agoNo licenceView on GitHub
Use whenever someone wants to inventory or document the full scope of what they (or a direct report) actually do: every responsibility, task, and workstream, especially to justify a decision like making the case for a new hire, deciding what to delegate/automate/offload, building a RACI or current-vs-target ownership map, clarifying a role, or prepping for a reorg. Reach for this skill even when the user does not say "audit" or name a skill; phrases like "document everything I do," "where does my time actually go," "spreadsheet of all my responsibilities with time and criticality," "what should I hand off," or "map my scope before I talk to my manager" all mean this. It mines the person's calls (Fathom), Slack, email, and tasks (Asana) into a scored, evidence-backed Google Sheet with a current-to-target ownership model. Not for profiling someone else, a single one-off delegation, calendar or meeting-time math, org charts, or weekly-accomplishment recaps.
In this repository76 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- academic-outcomesSkill
- add-domainSkill
- ai-level-upSkill
- airtableSkill
- bet-ideaSkill
- bet-planSkill
- bet-researchSkill
- bet-studioSkill
- kw:brainstormSkill
- braintrust-evalsSkill
- campus-roadshowSkill
- kw:compoundSkill
- connectSkill
- customerioSkill
- dashboard-designSkill
- data-intelSkill
- data-model-discoverySkill
- deployment-guideSkill
- email-ab-test-analysisSkill
- feature-branch-protocol-templateSkill
- frontend-slidesSkill
- full-shapeSkill
- gdoc-buildSkill
- gdoc-editSkill
- google-driveSkill
- google-slides-apiSkill
- gwsSkill
- help-centerSkill
- hex-accessSkill
- hubspotSkill
- instructional-designSkill
- interrogateSkill
- investigationSkill
- jd-builderSkill
- kb-articleSkill
- llm-email-workflowSkill
- macroscopeSkill
- n8nSkill
- netlify-deploySkill
- nsls-authSkill
- nsls-focus-groupSkill
- nsls-setmeupSkill
- nsls-slidesSkill
- personal-setupSkill
- kw:planSkill
- posthogSkill
- product-designSkill
- prompt-packSkill
- provision-builderSkill
- publish-to-dsrSkill
- pydoc-pipelineSkill
- quicknoteSkill
- receiptsSkill
- register-automationSkill
- kw:reviewSkill
- scorecard-builderSkill
- second-opinionSkill
- setupSkill
- signal-setupSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
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.