Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Events are the most expensive marketing channel per contact and the easiest to spend badly on, because the outputs — booth traffic, badge scans, attendance — feel like results and are not.
The question is never "should we be at this event" but "what specifically do we expect, and what is that worth." Answer three things first:
Small, self-hosted, targeted formats — a dinner for fifteen right accounts, a focused workshop — routinely outperform large sponsorships per dollar for enterprise pipeline, and are unglamorous enough that they get proposed rarely.
Most event spend is wasted after the event, not during it. A scanned badge is not a lead, and the value decays in days.
Agree before the event: who follows up, in what timeframe, with what message, and how those contacts
are treated differently from inbound. Route it through revenue:revenue-operations so the tracking
exists in advance, and hand the sequence to demand-generation:lifecycle-messaging.
Score contacts honestly. Everyone who took a branded item is not a lead, and passing them to sales as if they were is how sales stops working the source at all.
Same discipline, different economics. Registration is not attendance and attendance is not interest; the segment worth pursuing is people who stayed and asked something.
The recording usually outperforms the live event over time, so plan the content as a durable asset —
marketing:content-strategy and marketing:video-content — rather than as a one-time performance.
Events are structurally hard to attribute: they influence deals that close months later through paths no model captures cleanly. Overclaiming destroys the channel's credibility; refusing to measure destroys its funding.
Track influenced pipeline with the assumption stated, alongside the honest direct-source number, and
compare cost per opportunity against your other channels through
demand-generation:marketing-analytics.
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.
Event and webinar platforms, roughly by scale: Luma or Zoom Webinars for small and recurring formats; Goldcast, ON24 or Bizzabo where the recording and the follow-up data matter; Cvent for large multi-track events, and similar.
Lead capture at physical events: the organizer's badge scanning, or your own — and whichever it is, test the export path into the CRM before the event rather than discovering the format afterward.
The tooling that actually decides the outcome is the follow-up sequence, which lives in your lifecycle platform and should be built before the event opens.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。