Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Collateral gets used when it solves a problem the seller has in a live conversation. Everything else is filed and forgotten.
Before making anything, find where deals die: first call, after the demo, at pricing, at security review, at the champion's boss. Each stall has a different remedy, and building for the wrong one produces beautifully designed collateral nobody opens.
Pitch deck — a structure, not a script. Problem the buyer recognizes, why current approaches fail, what you do differently, proof, commercials, next step. Ten to fifteen slides, each with a takeaway headline.
One-pager — what the champion forwards internally to people you will never meet. It must survive being read with no context and no presenter. This is usually the highest-leverage asset and the most neglected.
Objection handling — the real objections, in the words prospects use, with responses that acknowledge the legitimate part first. A response that denies the objection reads as evasion and ends trust.
Battlecards — per competitor: where they genuinely win, where you do, the traps to avoid, and what to say when the prospect raises them. Cards claiming you win everywhere get ignored by sellers, who know better.
Case studies — situation, what changed, measurable result, in the buyer's language. One verifiable number beats a page of adjectives.
Demo the outcome, not the interface. Start where the value is visible, not at login and settings.
Tailor to the problem they told you about — a feature tour of everything demonstrates that you were not listening. Prepare for the three things that always go wrong, and know how to reach the value moment inside five minutes when time gets cut.
Collateral rots. Every asset needs an owner and a review date, and anything referencing pricing, competitors, or product capability needs checking every quarter. A battlecard describing a competitor's old product loses deals.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。