Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when someone picks a topic, a calendar row or a URL and needs a brief another person can write from: the angle, the proof to gather and who holds it, the links, title options, the one action the asset asks for, and who reviews and approves it.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this when someone picks a topic, a calendar row or a URL and needs a brief another person can build from. The brief is what you deliver. Write the finished piece only if they ask for it outright.
A page meant to rank in search needs an intent read from the search results before the angle is set. If the team has an SEO specialist or an SEO brief for the page, start from that. If not, do a short intent read yourself (the queries, what the ranking pages cover, and the gap) and label it as your read rather than research.
Name the asset, the primary term or hook, who it is for, and where it ships. Ask only for what the calendar row leaves out.
Read the pages or posts already doing this job well. Note what all of them cover, and, more usefully, what none of them do. That gap is usually the angle.
[need this: what], never as a filled-in fact.Close with the two or three voice rules this asset is likeliest to trip over, quoted from the voice guide.
Never invent a statistic, a customer name, a quote or a date to make the brief look complete. Never mark the row drafted, approved or scheduled off your own say-so; those move on something real. Never promise a ranking or a timeline.
Show the brief here first, then file a dated copy and deliver it where they asked for it to live: a document, a workspace page, or a backlog item. Once it has landed, move the calendar row to briefed.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
日本語の概要は準備中です。原文の説明を表示しています。
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
日本語の概要は準備中です。原文の説明を表示しています。
Write ad variants that each test one idea, within platform limits and supported claims.
日本語の概要は準備中です。原文の説明を表示しています。
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
日本語の概要は準備中です。原文の説明を表示しています。