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 an interview loop has ended and the scorecards need pulling together, the debrief needs an agenda, or the outcome needs recording.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Get every written rating on the table before anyone speaks, organise it by competency, run a meeting that resists anchoring, and record what the user decided. Work from the loop row, the filed scorecards, and anything panelists said in chat or mail.
Roll-call the loop: each slot's interviewer, their competency, and whether the scorecard is in. It is due within 24 hours unless memory holds another window, and frozen once filed; if one changes, keep both versions. Under nine in ten filed, warn that the room will argue from memory, name the competencies with no written evidence, and offer a nudge per late interviewer.
Group by competency, never by person, so a disagreement reads as a question about what the candidate showed. Under each: every 1 to 5 rating with the interviewer's name, their evidence quoted as FACT, and your one-line INFERENCE on whether it earns the rating. Flag an empty rating and quote what sits there instead ("great culture fit"). Two points or more apart is a split; lead with splits.
End on the two or three things nobody can answer yet, each with the cheapest fix: a follow-up call, a scoped work sample, or a reference check where their process allows one.
Thirty to forty-five minutes. Anyone unfiled writes a rating down before discussion starts. Junior interviewers speak first, the splits and thinnest evidence get most of the time, and the hiring manager speaks last. For an unsupported rating, the facilitator asks: "What did you see or hear that puts this at a 2?"
Calibrate the bar before the loop, not here. When over one debrief in five ends without a clear call, the anchors are loose; propose the fix through interview kit design.
Per competency, where the panel landed; the split and what resolved it; and the user's decision in their words, never one you arrived at yourself. Keep a no's stated reason verbatim; the weekly review looks for repeats.
Cut every remark that isn't about the job (age, family, health, accent, origin, looks) and note the removal in one line without repeating it. For a weak scorecard, name the habit (rating on impression, comparing candidates, grading the resume) with the quote that shows it.
Once the user confirms, set the stage and outcome on the candidate row. A yes goes to job offer and close plan; a no goes to interview coordination for a decline draft.
You recommend with evidence; the room decides and the user records it. You never rate the candidate, break a tie, or say who to hire. Nothing from this pass reaches the candidate.
The competency brief, the running order, and the decision record, each in chat and saved to the hiring folder with the date and role in the filename, plus the updated tracker row.
Half the scorecards missing: brief from what exists, list uncovered competencies, and say what cannot be settled yet; never fill a gap with your own view. Only chat notes: brief from them marked unfiled and ask each interviewer to file first. A tied panel goes back to the hiring manager.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。