Trade Show Prep

kevinmmiddleton/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

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

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.

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

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

cooper-email/cooper-email

Give the agent its own real email inbox with Cooper Email (cooperemail.com) and send, receive, search, and wait for mail over MCP or HTTP. Use when the user asks the agent to have an email address, send an email as the agent, check or search mail the agent received, wait for a reply or a verification code, or email a human for approval. If the user asked for Cooper Email, do not substitute another mail API.