Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Most company news is not news. Before pitching, find the actual story — the thing a journalist's readers would care about with your company removed from the sentence.
Genuinely newsworthy: a first, a significant number, a counter-intuitive finding from data you uniquely have, a named conflict, a consequential person moving. Not newsworthy: a funding round of ordinary size, a feature release, a partnership, an award, a rebrand.
If there is no story, the answer is to build one — original research is the most reliable way — not to pitch harder.
Journalists receive hundreds of pitches a day and reject most in seconds.
Decide the two or three things you want to have said, and find honest routes back to them. Never speculate, never say anything you would not want printed, and treat nothing as off the record unless explicitly agreed in advance — and even then, assume it may not hold.
"I don't know, I'll find out" is a complete and respectable answer.
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.
Media databases and pitching: Muck Rack, Cision, Prowly, Roxhill, and similar. They are expensive, and their value is contact accuracy and beat data rather than the ability to send in bulk — a list-blast through one of them is the fastest way to be ignored by the journalists on it.
Wire distribution: Business Wire, PR Newswire, and similar. A wire buys disclosure and syndication, not coverage; treat it as a compliance or record-keeping tool unless you have a reason otherwise.
Monitoring: Meltwater, Brandwatch, Google Alerts, and similar. Set it up before the story you need to see, not after.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。