adjustleads

deadline-research

Use when someone asks what clock applies to a claim in a state. Researches current statute and policy conditions, cites each source, lists deadlines to confirm.

first-notice-checklist

Use when a new loss call or email comes in and you want to capture everything before it is lost. Intake checklist, questions in order, paste-ready summary.

inspection-narrative

Use when you are back from a site visit and want field notes and a photo list turned into a dated inspection note. Room by room, with what is still missing.

settlement-counter

Use when a carrier estimate comes back and you want to know what to challenge. Reads the pasted estimate, lists items to question, drafts the counter to review.

announcement

Use when someone must tell customers about a release, feature, policy change, or price change and asks for the announcement, release note, or email.

customer-email

Use when a customer or client wrote in and someone asks for a reply, a response, or what to say back. Answers first, in the owner's voice, no canned closers.

cut-it-in-half

Use when a draft runs long and someone asks to cut, shorten, tighten, or trim it, or get it down to half. Halves the length and keeps every fact.

say-it-plainly

Use when a draft sounds like an AI wrote it, or someone asks to make it less AI, more human, plain English, or like them. Rewrites it, facts unchanged.

dunning-email

Use when a payment failed or an invoice is past due and you want a personal note, not the processor's robot. Three short emails, subject lines, a reply plan.

exit-interview

Use when a customer just canceled and you want to learn why without a survey. One-question email, the reply if they answer, and a line for your reasons list.

save-play

Use when a customer is about to cancel, went quiet, or asked to downgrade, and you need to decide what to say. Says why they are churning and drafts the note.

pack-readme

Use when a pack is ready to list and someone asks for the README, store page, or buyer summary. Writes who it's for, one line per skill, and what buyers need.

release-notes

Use when a new pack version ships and someone pastes a diff or a list of changes and asks for release notes. Writes what changed for the buyer, nothing more.

trigger-check

Use when a skill won't fire, or someone asks if a description matches what buyers type. Tests eight buyer phrasings and rewrites the description till they hit.

write-a-skill

Use when someone wants to turn a process into a skill, or asks how to write a SKILL.md. Asks five questions, then writes the full file with frontmatter.

DevOps & Infrastructure Listed

decision-log-entry

Use when someone pastes meeting notes, a transcript, or a thread and asks what was decided. Extracts every decision, owner, and deadline into a log entry the team can hold each other to.

follow-up-email

Use when a meeting just ended and someone asks for the follow-up, recap, or next-steps email. Writes a short email that confirms decisions and assigns actions without corporate filler.

meeting-prep-brief

Use when someone shares an upcoming meeting, an agenda, or a calendar invite and wants to walk in prepared. Produces a one-page brief with the goal, the questions to ask, and the risks to watch.

weekly-priorities

Use when someone dumps their task list, inbox, or worries and asks what to work on this week. Turns the pile into a ranked plan with a reason for every cut.