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.
日本語の概要は準備中です。原文の説明を表示しています。
Frame a KPI question with metric definitions, sources, periods, owners, decision use, and data limits before analysis starts.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this before calculating a result. A clear question and a stable definition prevent a polished answer to the wrong problem.
Write down the business question, who will use the answer, the decision it may
change, the required date, and the cost of a wrong call. Separate a descriptive
question (what changed?) from a causal one (what caused it?).
For each metric record:
Do not accept the same label for two formulas. Version a changed definition and state where comparison stops.
For each file or table, capture its name, extract time, covered dates, row count, key fields, likely join keys, currency or units, and access limits. Keep raw source columns apart from derived fields. Record the expected control total.
State the primary comparison, useful segments, quality checks, material-change threshold, and what evidence could answer the question. List what the data cannot establish. Return blockers and the smallest source or question that would remove each one.
Never invent data, infer a missing definition, or change a metric after seeing the result without disclosure. Use the least personal data needed; aggregate or redact identifiers. Do not claim causation from a descriptive export. Route privacy, legal, clinical, credit, employment, and material finance decisions to the named owner.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。