Showing 31351–31380 of 77205 skills
Build battlecards and talk tracks from win/loss evidence. Use when asked to "write a battlecard", "build a competitor card", or "create talk tracks for objections".
tonone-ai/tonone
Design the onboarding ramp — 30/60/90 plan, certifications, quota ramp. Use when asked to "build a sales onboarding plan", "design a ramp for new AEs", or "create a 30-60-90 plan".
tonone-ai/tonone
Read-only audit of enablement — ramp time, call quality, content usage, win/loss insight. Use when asked to "audit our sales enablement", "why do new reps ramp slowly", or "review our sales training".
tonone-ai/tonone
Run a POC or pilot — success criteria, timebox, plan, exit decision. Use when asked to "scope a POC", "plan a pilot", or "set POC success criteria".
tonone-ai/tonone
Read-only audit of SE readiness — demo assets, POC history, questionnaire bank, technical win rate. Use when asked to "audit our sales engineering", "how good are our demos", or "review our POC process".
tonone-ai/tonone
Design a demo — discovery-driven narrative, flow, environment, failure handling. Use when asked to "design a demo", "prepare for the technical demo", or "write a demo script".
tonone-ai/tonone
Build the forecast — stage weights, commit/best-case/upside, accuracy tracking. Use when asked to "build a sales forecast", "set up forecast categories", or "forecast this quarter".
tonone-ai/tonone
Read-only audit of the CRM and forecast process — data quality, stage integrity, forecast accuracy. Use when asked to "audit our CRM", "why is our forecast off", or "check pipeline hygiene".
tonone-ai/tonone
Design territories and quotas — account segmentation, fairness, assignment rules. Use when asked to "design sales territories", "set quotas", or "rebalance territories".
tonone-ai/tonone
Write the board revenue narrative — bookings, pipeline, forecast, risks, asks. Use when asked to "prep the board revenue update", "write the revenue section of the board deck", or "explain the quarter to the board".
tonone-ai/tonone
Build the bookings capacity model — ramped reps, quota, attainment, hiring plan. Use when asked to "build a capacity plan", "how many reps do we need", or "set quotas for next year".
tonone-ai/tonone
Read-only audit of the revenue engine — coverage, capacity, conversion, org gaps. Use when asked to "audit our revenue engine", "why are we missing the number", or "assess our GTM org".
tonone-ai/tonone
Build the target list — ICP scoring, triggers, enrichment, suppression. Use when asked to "build a prospect list", "define our ICP", or "find accounts to target".
tonone-ai/tonone
Read-only audit of the outbound engine — ICP, list quality, sequences, deliverability, handoff. Use when asked to "audit our outbound", "why is our SDR team not booking meetings", or "review our prospecting".
tonone-ai/tonone
Write the outbound sequence — multi-touch cadence, copy, A/B plan, handoff rules. Use when asked to "write an outbound sequence", "draft cold emails", or "build a cadence".
tonone-ai/tonone
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
tonone-ai/tonone
Audit developer experience — measure onboarding time, build speed, deployment friction, and developer satisfaction. Use when asked to "DX audit", "developer experience review", "why is development slow", "onboarding assessment", or "DORA metrics".
tonone-ai/tonone
Platform reconnaissance — inventory all developer tooling, environments, build systems, and developer workflows for project takeover. Use when asked to "understand the dev setup", "developer tooling assessment", "platform assessment", or "how do developers work here".
tonone-ai/tonone
Build API test suites — endpoint testing, contract testing, load testing for REST/GraphQL/gRPC APIs. Use when asked to "test this API", "API tests", "endpoint testing", "contract tests", or "load test".
tonone-ai/tonone
Audit test suite health — find flaky tests, slow tests, coverage gaps, and testing anti-patterns. Use when asked to "audit tests", "fix flaky tests", "why are tests slow", "test health", or "improve test suite".
tonone-ai/tonone
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
tonone-ai/tonone
Run /be's review gauntlet SERIALLY — /lens-debate (lowy ⇄ hickey), then /codex-debate, then /simplify, then code-police, each editing and committing on the live branch in turn. Use from /be §4, or when the user asks to "run the review gauntlet". Requires Claude Code's Skill tool.
srid/emanote
Reference for the `odu` runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs. Trigger when the user asks to "run CI", "run the pipeline", "re-run a check", to run named lanes or recipes (e.g. "run fmt and nix", "just the e2e lane", bare selectors like `fmt`/`nix`/`e2e`), or names a recipe by `<recipe>@<platform>`. This skill — not a repo's local `just ci` / `just <recipe>` — is how an odu-run request is served.
srid/emanote
Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit. Two explicit subcommands. `review` (also the bare/back-compat default) — codex (reviewer) critiques the current diff and a Claude subagent (author) fixes/disputes, looping until they agree. `answer` — Claude and codex each answer a freeform prompt in parallel, then cross-check until they agree, and a unified answer is returned. Use when the user types `/codex-debate`, asks to "have codex review this", "run the codex debate", "review this PR with codex", "argue this with codex until you agree", or passes a question to "have Claude and codex debate/answer until they agree".
srid/emanote
Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types `/do` or `$do`; never auto-select from a natural-language request, even one that sounds like an end-to-end task.
srid/emanote
Reference for the dpella/mcp Haskell library — types, handler shape, transports, and the conventions Emanote uses. Load this before adding MCP resources/tools/subscriptions so you don't re-discover the API by WebFetch.
srid/emanote
Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned). Use when creating or updating PRs. Leads with narrative paragraphs and reaches for lists, tables, and diagrams when content is genuinely structured.
srid/emanote
Drive one AI agent from another through kolu's terminals: spawn a Claude Code / Codex / opencode session in a PTY, prompt it, watch the screen for its reply, read it, and prompt again — a create→send→snapshot loop run with the `kaval-tui` CLI directly (no MCP). `kaval-tui` writes input and reads scrollback; `pulam-tui` adds a precise agent-state done-signal when you drive hooked terminals. Triggers on "drive another agent", "send a prompt to a terminal agent", "have one agent prompt another", "agent drives agent", "orchestrate agents in terminals", "make Claude drive Codex", "prompt the agent running in that terminal", or wiring a loop where one coding agent supervises another.
srid/emanote
Run a structural-review debate between two lenses — lowy (volatility-based decomposition) and hickey (structural simplicity) — on the current diff. Each reviews independently, then they cross-examine every finding until they agree per-finding, and the agreed fixes are applied. Use when the user types `/lens-debate`, or asks to "have lowy and hickey review this", "run the lens debate", "debate this diff structurally", or "argue the structure of this PR until the lenses agree".
srid/emanote
Use this when setting up Nix for a development project (devShell + package build) and you care about `nix develop` being fast. Covers the zero-inputs flake.nix + npins + default.nix/shell.nix layout, sub-flakes for non-user-facing Nix, and language-specific recommendations.
srid/emanote