Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A newsletter is a standing invitation that can be withdrawn at any time. Every issue either renews it or spends it.
One issue, one job: teach something, argue something, or sell something. Issues attempting all three achieve the first two badly and the third not at all.
They are read together and should not repeat each other — the preview extends the subject rather than echoing it. Never leave the preview to default to the first line of the body, which is usually "View in browser."
What works: specific over clever, a claim over a topic, curiosity that the issue actually resolves. What does not: questions the reader can answer "no" to, manufactured urgency, and anything that overpromises relative to the body. Overpromising buys one open and costs the next five.
The first sentence decides whether the rest is read. Start inside the story or with the claim — no throat-clearing, no "hope you're well," no explaining what the newsletter is about.
Cut your first paragraph after drafting. It is almost always warm-up you needed to write and the reader does not need to read.
Short paragraphs. One idea each. Enough white space that the issue looks readable before it is read — people decide whether to read from the shape of the thing.
Signpost where the issue turns, so someone skimming still gets the argument. Most readers skim.
The thing that makes a newsletter worth opening is that it sounds like a person. Specifically:
Avoid the register tells: "In today's fast-paced world," "it's no secret that," "let's dive in," tricolon everywhere, and every paragraph the same length.
Earn the ask. When an issue sells, the value comes first and the pitch is clearly marked — readers forgive a clear pitch and resent a disguised one.
One call to action per issue. Multiple asks split attention and reduce all of them.
Replies are the strongest signal a newsletter is working, and they improve deliverability more than any technical fix.
Ask one specific question, occasionally rather than every issue, and make it easy to answer in a sentence. "What did I get wrong here?" outperforms "let me know your thoughts," which asks the reader to do the work of deciding what to say.
Then reply to the replies. A newsletter where the author answers is a different product from one where they do not, and readers tell each other about the first kind.
Three passes, in order: structure (is the order right, is anything missing), cut (remove what does not advance the argument), read aloud (anything you stumble over gets rewritten). The read-aloud pass catches what silent reading never does.
One issue contains several short-form posts, a talk track, and often a longer piece. Plan which before writing, so the sections that should stand alone are written to.
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.
日本語の概要は準備中です。原文の説明を表示しています。