Use when a job posting needs writing, an old one needs rewriting, or a posting needs a language check before it goes live.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Run this when the user needs a new posting written, an old one rewritten, or a posting screened for language before it goes live.
The role scorecard, the hiring manager's notes on the team and the work, and the facts that must appear: title, level, location and work setup, pay band if it is shareable, and how to apply.
The mission in two sentences. What this person owns in the first 90 days. The three to six must-haves as checkable outcomes. The labelled nice-to-haves. What the team offers — scope, growth, pay band when given. A short equal-opportunity close.
Pull the day-in-the-life lines verbatim from the intake conversation into the posting, and set the baseline for it in plain words: who should apply and what success looks like.
"Has shipped a service handling production traffic" beats "5+ years experience". Cut degree demands and years-floors unless the hiring manager defends them in one line.
No gendered superlatives, no "rockstar" or "ninja", no laundry list of nice-to-haves posing as requirements, no jargon a strong outsider would not know. When you cut a line, say what you cut and why in one line.
Pay, title, and start date go in only as the user stated them. Do not guess a salary range, and do not derive one from the company's size or funding. Mark anything unconfirmed UNKNOWN rather than drafting around it.
The finished posting shown in chat, one round of edits, then a clean block ready to paste into the applicant tracking system (ATS) or the careers page, plus a one-line note on anything cut for language and anything still UNKNOWN. Saved to the hiring folder.
With no scorecard, draft from the title plus the four intake questions and mark it a draft pending calibration. With only an old posting, rewrite in place and show a short before-and-after on the lines you changed.
Drafts only. Never post a job, publish a req, or send a posting anywhere without the owner's explicit yes for that specific action.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.