Playbooks your experts follow. Teach them your way of working.
406 skills
Use when someone asks for the weekly marketing report or why a marketing number changed, or when the Monday read comes due: fix the period, check which sources you actually have, find the biggest moves, trace each to its cause, and say plainly when the numbers cannot explain themselves.
Build a nurture around one segment: the journey and the exit that stops it, the drafts, the experiment that decides whether it worked, the pre-send checks, and the incremental readout afterwards.
Use when someone hands over notes, bullets or a transcript and wants one draft built for a specific channel (email, landing page, post, blog, direct message, release notes), with every missing fact marked in place and two alternative openers.
Run the content calendar as the single source of truth: one row per asset with an owner and a ship date, plus the recurring read on what ships this week, what is late, and what is stuck waiting on one person.
Use when someone picks a topic, a calendar row or a URL and needs a brief another person can write from: the angle, the proof to gather and who holds it, the links, title options, the one action the asset asks for, and who reviews and approves it.
Turn a campaign goal into a brief the team can build from: the goal said back in one measurable line, the audience and the insight that moves them, the channel mix, the asset list with an owner and a date on each, and the two or three measures you will judge it on.
Build the layer above the voice guide: the positioning line, the three proof points you repeat, the claims you will never make, the language each persona gets, and where the tone sits for sales, support, marketing and social.
Use on the first chat with Maya, or whenever her memory holds no marketing preferences yet: learn what they sell and who buys it, where their work has to land, who approves anything a customer will see, and put one real piece of marketing work on screen in the same session.
Performs security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and generates a markdown report. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering it.
Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.
Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.
Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.
Plan a small, testable dependency upgrade with compatibility checks, owners, rollout evidence, and rollback steps.
Decide whether a CVE or advisory matters to the actual stack and show the data behind that judgement.
Triage dependency findings by verified affected versions, exposure, exploit conditions, impact, and available fixes.
Review outdated packages by support, change size, exposure, and value instead of treating every newer version as urgent.
Build an evidence-backed inventory of direct, transitive, runtime, development, and container dependencies.
Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.
Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".
Use to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
Google and Notion