Unpaid Intern
Unpaid Intern runs a portable second brain for knowledge work: a plain-file workspace for projects, decisions, follow-ups, and meeting notes, plus optional live reads of mail, chat, calendar, tracker, and wiki, so nothing starts from scratch between meetings. Use when someone wants to set up or run a work second brain, work agent, or work assistant; runs one of its commands (/briefing, /pulse, /prep, /who, /debrief, /capture, /close, /gofer, /project-status, /redline, /slots, /triage, /sync-kb, /kb-lint, /tidy, or another command from the kit) in that workspace; asks to prep a meeting, turn a
Install
npx skills add kevinmmiddleton/unpaid-intern --skill unpaid-interngit clone --depth 1 https://github.com/kevinmmiddleton/unpaid-intern.git /tmp/unpaid-intern
mkdir -p ~/.claude/skills
cp -r /tmp/unpaid-intern/skills/unpaid-intern ~/.claude/skills/unpaid-internPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Unpaid Intern A second brain for work. It's the intern, not the boss. The agent does the legwork: it finds the source, finds the prior work, drafts the note, and keeps the record. The person owns the call: what is true enough to say, what gets sent, and what stays out. Notes are not the product. A record the person can trust is. This skill is company-agnostic. Build everything from the current user's own workspace and answers. Never import another person's projects, people, voice, or guardrails, and never treat an example in this skill as a fact about the user. ## The three doors 1. **Drop it in.** A folder the user saves into: transcripts, PDFs, screenshots, exports, notes. If they can save it, the agent can read it. 2. **Go get it.** Optional live reads of mail, chat, calendar, tasks, tracker, and wiki, so the user stops pasting threads into chat. 3. **Keep it.** Every project has a home with status, decisions, follow-ups, and the sources behind them. ## First run Look for `START-HERE.md` and a `Memory/` folder in the working folder, or an uploaded `second-brain-*.zip` (restore it with `brain.py unpack <zip> <folder>`). Before the first script runs (this section and Session open both run them), settle the scripts, Python, and the Windows PowerShell file rule, as the Scripts section below says.
Details
- Skill name
unpaid-intern- Repository
- kevinmmiddleton/unpaid-intern
- Path
skills/unpaid-intern/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
- Listed in
- karanb192/awesome-claude-skills
FAQ
What does the Unpaid Intern skill do?
Unpaid Intern runs a portable second brain for knowledge work: a plain-file workspace for projects, decisions, follow-ups, and meeting notes, plus optional live reads of mail, chat, calendar, tracker, and wiki, so nothing starts from scratch between meetings. Use when someone wants to set up or run a work second brain, work agent, or work assistant; runs one of its commands (/briefing, /pulse, /prep, /who, /debrief, /capture, /close, /gofer, /project-status, /redline, /slots, /triage, /sync-kb, /kb-lint, /tidy, or another command from the kit) in that workspace; asks to prep a meeting, turn a
How do I install the Unpaid Intern skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add kevinmmiddleton/unpaid-intern --skill unpaid-intern. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Related skills
001 Jeremy Taskwarrior Integration
jeremylongshore/claude-code-plugins-plus-skills
Enforces complete Taskwarrior integration protocol for ALL coding tasks. Activates automatically when user mentions "taskwarrior", "task warrior", "tw", or discusses task management. Decomposes all coding work into properly tracked Taskwarrior tasks with full lifecycle: task add → task start → implementation → task done. Integrates with Timewarrior for automatic time tracking.
Trade Show Prep
DataOrigin/trade-show-prep-skill
Prepare, work and follow up a B2B trade show for an exhibitor or a visiting sales team. Builds a dated plan from 8 weeks before the fair, drafts meeting requests for the user's own accounts (email and LinkedIn), writes a booth qualification guide with a note template, and drafts a post-show follow-up sequence with cost per lead and ROI. Use when the user says "prepare our trade show", "we are exhibiting at", "we are visiting a fair", "meeting requests for the show", "booth qualification", "trade show follow-up", "post-show emails" or asks for help before, during or after a B2B fair or conferen
Analyzing Capacity Planning
jeremylongshore/claude-code-plugins-plus-skills
This skill enables Claude to analyze capacity requirements and plan for future growth. It uses the capacity-planning-analyzer plugin to assess current utilization, forecast growth trends, and recommend scaling strategies. Use this skill when the user asks to "analyze capacity", "plan for growth", "forecast infrastructure needs", or requests a "capacity roadmap". It is also useful when the user mentions specific capacity metrics like CPU usage, memory, database storage, network bandwidth, or connection pool saturation. This skill is ideal for proactive infrastructure planning and preventing per
Skill Skill
jack-reson8/skill-skill
Write, upgrade or audit a Claude skill so it actually changes what gets generated, not a pile of notes. Use whenever the user wants to create a skill, turn a conversation, workflow or methodology into a skill, rename it, add research or lessons, asks why a skill isn't taking effect, or wants to publish a skill and get it listed in awesome lists and plugin marketplaces. Covers distilling from real work (corrections, rejections, accepted outputs), forcing functions (required artifacts, gates, checklists, scripts), descriptions that trigger, naming, a static audit with a health score, a with/with
Building Gitops Workflows
jeremylongshore/claude-code-plugins-plus-skills
This skill enables Claude to construct GitOps workflows using ArgoCD and Flux. It is designed to generate production-ready configurations, implement best practices, and ensure a security-first approach for Kubernetes deployments. Use this skill when the user explicitly requests "GitOps workflow", "ArgoCD", "Flux", or asks for help with setting up a continuous delivery pipeline using GitOps principles. The skill will generate the necessary configuration files and setup code based on the user's specific requirements and infrastructure.
Project Planning Journaling
mh-mansouri/Project-Planning-Journaling
Scope a new project (or resume one) and set up a living, resumable documentation journal for it, including a routine weekly health check, not just updates triggered by commits. Use at the start of any project, before writing code, to ask about project type, Git repo status, short/long-term goals, and whether it should stay public/open-source or become a private product later. Also use when someone wants to document what has been done, wants a changelog or decision log, needs to resume work from a prior session without re-reading chat history, wants docs kept current after every commit, or want
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.