Skip to content

legioncodeinc/littlebird-toolkit

v3.0.0AGPL-3.0-or-later

Turn Littlebird memory into evidence-backed operating work.

Littlebird Skills

Your work. Your record. Your skills.

Thirty Claude skills built on the Littlebird MCP. They read what already crossed your screen and what was already said on your calls, and hand you back something you can act on.


What this is

Littlebird watches your screen and transcribes your meetings. That means the record of your work already exists. What has been missing is anything that uses it.

These skills use it. They find the subscription you have paid for and not opened in ninety days. They rebuild the pipeline that only lives in your head. They write the SOP for the thing you did last Thursday, because Littlebird watched you do it. They mine the good line you said on a call and forgot by Thursday, and hand it back as a draft.

Every one was built the same way: real domain research archived to primary sources first, then the skill written from it. Every claim a skill makes carries a receipt with a timestamp and the app it came from. When a skill cannot honestly measure something, it says so instead of producing a confident number.

Install

This pack belongs to the Wasp Nest marketplace. After the version 3 marketplace is published, use these Claude Code commands:

/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nest
/plugin install littlebird-toolkit@wasp-nest

Each folder under skills/ is also a complete standalone skill. Zip one with a .skill extension, folder at the zip root, and upload it to Claude. The Wasp Nest marks all 30 as standalone in frontmatter. They run directly in the current assistant or a Routine and do not claim companion Drones.

Requirements. Most skills need the Littlebird MCP on a Power or Pro plan, connected at https://mcp.littlebird.ai/mcp. New to Littlebird? The code E6GP4BQE gets you two months free. The Facebook voice creator is the one skill that needs no Littlebird at all.

How you use them

Just ask. Every skill carries its own trigger phrases. Say "who has not paid me", "what did I promise", "write an SOP for that", "who is about to churn", and the right skill picks itself up. You never invoke anything by name unless you want to.

Or put it on a routine. Littlebird routines are unattended agents that run on a schedule and push you a report. The split that makes this work:

Routines observe. Cowork acts. A routine watches for a condition and writes a report. It cannot ask you a question, hold an approval open, or write a file. So it names what it found and hands off. You open Cowork, the skill picks up its own past reports, and does the heavy work.

Skills that have a recurring mode will set up their own routine. They show you the exact prompt text and the schedule, you approve it, and it gets created. You do not go configure anything by hand.

Nothing gets sent. Every skill that produces something for another human drafts it and holds it. Approving a plan is not approving the words, so you see the final text before anything leaves.


The skills

Money and business operations

SkillWhat it doesMode
money-leak-auditorRebuilds every software charge you actually pay from what crossed your screen, then proves which tools you have not opened in 90 daysMonthly + on demand
renewal-sentinelA 90-day calendar of everything about to auto-charge, sorted by the date you have to decide by rather than the date you get billedWeekly + on demand
invoice-chaserTurns "they still have not paid" into a drafted follow-up, without ever chasing a client who already paid youWeekly + on demand
deal-pipeline-reconstructorRebuilds the pipeline that only exists in your head into a board where every placement shows its evidenceWeekly + on demand

Lead generation and growth

SkillWhat it doesMode
lead-harvesterRebuilds the full list of people who raised a hand at your "comment KEYWORD" campaign, ranks them, drafts each first messageOn demand + campaign daily
comment-to-crm-piperCatches new hand-raisers since the last run, dedupes against your CRM, tags by campaign, queues a first messageDaily
content-repurposerTurns one long piece into a week of derivatives that each take a different angle, so nobody reads the same idea five timesOn demand
said-it-alreadyMines what you already said well on calls, screens it, rebuilds it for reading, and hands you a bank of draftsWeekly
testimonial-minerBanks the praise you already earned as verbatim quotes, and tells you which ones you are allowed to publishMonthly + on demand
competitor-watchTracks what your market is actually talking about this week, from what crossed your own screenWeekly

Meetings and follow-through

SkillWhat it doesMode
meeting-scribeTurns one call into a sendable follow-up, a decisions record with the quote behind each, and a list of what never landedDaily evening + on demand
commitment-trackerA two-column ledger of what you owe and what you are owed, checked against evidence the thing actually got doneWeekly
who-am-i-ghostingFinds the conversations you left hanging, ranked by what the silence costs rather than how old it isWeekly
pre-call-prepA one screen brief for every call, where every line carries a fact you did not already have in your headDaily
client-health-radarWhich client is about to leave and which is quietly eating your margin, in bands backed by dated quotesWeekly + on demand

Personal productivity

SkillWhat it doesMode
daily-briefOne screen every morning, built around the field that earns the open: what changed since yesterdayDaily
day-reconstructorRebuilds a work session into a dev log and a changelog block, including the problems no commit message recordsDaily at session end
focus-forensicsThe structure of your week: where work held together, where it broke apart, what changed since last weekWeekly
learning-capturerStops you re-debugging the same wall, filing each fix keyed on the error text you will actually search forWeekly
weekly-reviewOne scorecard per week, composed from your other skills' reports, willing to say plainly that the week was poorWeekly

Knowledge and writing

SkillWhat it doesMode
sop-forgePoint it at something you already did and it writes the SOP, because Littlebird watched you do itOn demand
knowledge-base-builderTurns a project's calls and threads into the documentation pack that makes every future AI session productiveOn demand + monthly refresh
osint-investigatorPoint it at a name and get one evidence-graded brief from your record plus their public footprint, disagreements left standingOn demand only
research-synthesizerGive it a topic, get back what you already knew versus what is new, with working linksOn demand + optional weekly
brand-voice-guardianThe last read before you hit send: marks up the draft, counts the AI tells, rewrites it in your voiceOn demand only

Meta and automation

SkillWhat it doesMode
routine-architectScores your routines against nine failure modes and proves what is broken by quoting your own reports backOn demand + monthly
skill-suggesterFinds the work you did by hand four times this quarter and drafts the SKILL.md for the one worth buildingMonthly

Voice

The original three. Several skills above draft in your voice when one of these has been run, and say so plainly when none has.

SkillWhat it doesMode
combined-voice-creatorYour voice skill from both Littlebird memory and a Facebook export. The deepest cloneOn demand
littlebird-voice-creatorYour voice skill from Littlebird capture aloneOn demand
facebook-voice-creatorYour voice skill from a Facebook export alone, with a screenshot-guided walkthroughOn demand

Which ones to put on a routine

Routine slots are limited by your Littlebird plan, so treat them as scarce. Do not turn on fifteen routines in one afternoon. A report you stop opening is worse than no report, because it trains you to ignore the next one.

Start with five

These five cover the most ground for the fewest slots, and each one hands off cleanly to a skill you run when you want to act.

RoutineWhenWhy this one first
daily-briefDaily, about 45 minutes before your first real decisionThe only one you read every day. It pulls from the others, so it gets better as you add them
pre-call-prepDaily, 18:30 the evening beforeEvening beats morning, because it leaves you time to fix a forgotten commitment before the call
commitment-trackerWeekly, Monday 08:00The column nobody tracks is what other people owe you
money-leak-auditorMonthlyThe one that pays for itself on the first run
weekly-reviewWeekly, Friday 16:30Reads the other four rather than re-deriving them, so it costs almost nothing to add

Add as they earn their place

Daily. meeting-scribe at 18:00 if you run more than two calls a day. day-reconstructor at your session end plus an hour if you write code. comment-to-crm-piper at 08:00 only while a campaign is live, then pause it.

Weekly. who-am-i-ghosting, client-health-radar, and competitor-watch all default to Monday 07:30, so stagger them across the morning rather than stacking three reports at once. invoice-chaser and renewal-sentinel on Monday. deal-pipeline-reconstructor midweek. said-it-already and learning-capturer Friday afternoon, when the week has something in it. focus-forensics Monday, since it reports on the week that just ended.

Monthly. testimonial-miner and skill-suggester on the 1st. routine-architect once a month to audit everything above, which is the routine that keeps the other routines honest.

Deliberately never on a routine

sop-forge, osint-investigator, brand-voice-guardian, and the three voice creators. Each needs an approval gate or a redaction pass that an unattended run cannot hold open. osint-investigator refuses a routine for a second reason worth stating: a standing job that periodically re-researches a named person is surveillance, not diligence.


What makes these different

Four rules hold across all thirty.

Receipts or it did not happen. Every finding carries its source, the app, and the timestamp: [Tuesday, August 11, 2026 23:40 EDT | chrome]. You can check any line.

Observed, inferred, external, and unknown are four different things. A skill never promotes an inference to an observation by dropping the hedge, and never turns an absence into a negative finding. "No evidence of X in 90 days" and "X did not happen" are different claims, and only one of them is supportable.

Skills refuse to produce numbers they cannot honestly measure. client-health-radar will not give you a health score, because transcription drops the sentiment-bearing word in roughly one utterance in six. focus-forensics will not tell you that you lost six hours, because periodic snapshots cannot measure duration. deal-pipeline-reconstructor will not give you a win probability. Each of those refusals came out of the research, and each is written into the skill.

Confirm before you encode, confirm before you send. Anything about to be recorded as durable fact gets confirmed first. Anything about to reach another person gets approved as final text, not as a summary of the intent.

Behind each skill sits its own research archive: primary sources fetched and stored one file per source with a URL and a fetch date, a cited distillation, and domain guides that never make a claim the archive does not support. Where sources conflicted, both readings are recorded. Where coverage was thin, the gap is named rather than filled with a guess. Three hundred and eighty sources across the marketplace.

What is Littlebird

Littlebird is an ambient memory app for your computer. It captures your screen activity, joins and transcribes your meetings, connects your calendar, and exposes all of it to Claude through an MCP server (docs). That memory is what every skill here runs on. One to two weeks of normal computer use is enough for most of them to be useful.

Repo layout

littlebird-skills/
├── .claude-plugin/
│   ├── plugin.json          Plugin manifest
│   └── marketplace.json     Marketplace manifest (this repo IS a marketplace)
├── skills/                  30 skills, each with SKILL.md, README.md, references/
├── AGENTS.md                Briefing for coding agents working in this repo
├── CLAUDE.md                Claude-specific pointer to AGENTS.md
├── LICENSE.md
└── README.md

Each skill folder holds a README.md for humans, a SKILL.md for the model, references/ with the domain guides, and references/research/ with the archived sources everything traces back to.

The Wasp Nest build bundles this pack as a plugin under its own marketplace. It omits the source checkout's marketplace manifest, contributor-only CLAUDE.md, and the archived tarball in skills/_to_delete/ from that plugin package. The thirty skill folders remain intact.

License and attribution

Created by Mario Aldayuz and Legion Code Inc. First-party material is licensed under AGPL-3.0-or-later.

Built for people who want the record to actually do something. Go check what you are paying for.

Choose a capability

This pack contains 30 skills, 0 agents and 1 source command. The table explains each source skill; open its linked instructions for exact inputs, outputs and limits.

The skill descriptions and run modes above cover all thirty source skills. Follow each linked skill's own inputs and approval steps.

Start one task

Required packs: wasp-nest-core

Install the selected pack and its prerequisites through the marketplace. For the version 3 layout, purge the previous installation first. Select the skill shown by your client, or paste this request with real paths and scope:

After adding the Wasp Nest marketplace, Claude Code uses these installation instructions:

/plugin install wasp-nest-core@wasp-nest
/plugin install littlebird-toolkit@wasp-nest

Other clients use their plugin selection UI or discovered skill selector. Installing a package and invoking a task are separate steps.

Use meeting-scribe with [meeting and date]. Check the available Littlebird evidence and draft the recap, decisions and follow-ups for review.

Expected result: Dated, source-backed reports or drafts from accessible records. Missing Littlebird or voice inputs remain explicit gaps.

Claude Code plugin command names:

CommandWhat it does
/littlebird-toolkit:review-my-work (procedure)Build a private evidence-based review of a defined work period using available Littlebird reports and stated limits.

Agent responsibilities

This pack declares no paired agents; its standalone skills run in the current assistant.

Codex can use the named skill or its generated source-command-<name> wrapper where a source command exists. Home installations may expose flat commands. Use the actual selector offered by the host. A pack with no paired agents runs its standalone skills directly; a skill name does not prove that a native agent was launched.

Prerequisites and boundaries

No extra workflow-specific pack prerequisite is declared. Tool and account requirements remain in each skill.

Core supplies shared routing and review methods. Native Codex role registration requires the explicit installed-plugin registry and trusted Core hook; a marketplace selection alone is not proof of registration. Read the linked skill before work. Missing source, browser, connector, renderer or account access is a reported gap. Installation does not authorize sending, publishing, paid work or live settings changes.