thinkhard.si MCP
A free, public MCP server providing access to a library of 519 work prompts, a prompt grading tool, AI cost estimation, and AI terminology definitions. It allows agents to search, fetch, and grade prompts without requiring authentication or API keys.
Endpoint and access
No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.
MCP endpoint (Streamable HTTP)
https://thinkhard.si/mcpWhat you can do with it
- Search for ready-made prompts for specific jobs like meeting minutes
- Grade a prompt out of 10 based on ten quality checks
- Estimate the monthly cost of an AI feature across major models
- Define AI terms in plain English from a glossary
Source and maintenance
Vendor evidenceRegistry 1.2.0
Protocol and capabilities
- Server
- thinkhard.si 1.2.0
- MCP protocol
- 2025-06-18
- Tools
- 8 advertised
- Resources
- Not advertised
- Resource templates
- Not advertised
- Prompts
- 500 captured; incomplete (item-cap)
Server-advertised capabilities
{
"tools": {
"listChanged": false
},
"prompts": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
8 advertised
search_prompts — Search the prompt repository
Advertised read-only
Find ready-made, expert prompt templates for a work task in the thinkhard.si repository (500+ prompts for email, meetings, presentations, job search, marketing, sales, support, HR, finance, legal, spreadsheets, research and more). Use it whenever the user wants to write, plan, summarize, analyze or draft something at work, before writing a prompt from scratch. Then call get_prompt with the slug.
search_prompts input schema
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 8,
"maximum": 25,
"minimum": 1,
"description": "Optional: how many prompts to return, best match first (1 to 25, default 8)."
},
"model": {
"enum": [
"claude",
"gpt",
"gemini",
"any",
"agent",
"midjourney",
"image",
"video"
],
"type": "string",
"description": "Optional: only prompts laid out for this kind of model."
},
"query": {
"type": "string",
"description": "What the user wants to do, in plain words, for example \"cover letter\" or \"summarize a long contract\". Everyday words, abbreviations (CV, 1:1, P&L, SOP) and typos are understood, and results come best match first."
},
"collection": {
"enum": [
"office",
"writing",
"marketing",
"careers",
"sales",
"support",
"management",
"people",
"projects",
"research",
"data",
"finance",
"legal",
"operations",
"smallbiz",
"education",
"product",
"engineering",
"system",
"media"
],
"type": "string",
"description": "Optional: limit to one collection (see list_collections)."
}
}
}search_prompts output schema
{
"type": "object",
"required": [
"prompts"
],
"properties": {
"prompts": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"slug",
"title",
"use",
"collection",
"laid_out_for",
"score",
"url"
],
"properties": {
"id": {
"type": "string",
"description": "Registry number, such as CAR-002."
},
"url": {
"type": "string",
"description": "Its page on thinkhard.si."
},
"use": {
"type": "string",
"description": "When to use it."
},
"slug": {
"type": "string",
"description": "Pass it to get_prompt."
},
"score": {
"type": "integer",
"description": "Its own grade out of 10."
},
"title": {
"type": "string"
},
"collection": {
"type": "string",
"description": "The collection it belongs to."
},
"laid_out_for": {
"type": "string",
"description": "The kind of model it is laid out for."
}
}
},
"description": "Best match first. Empty when nothing matches."
}
}
}search_prompts annotations
{
"title": "Search prompts",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_prompt — Get a prompt template
Advertised read-only
Get the full text of one prompt from the thinkhard.si repository by its slug, registry number (such as CAR-001) or exact title, with its {{blanks}}, what goes in each, and why it works. If the name does not match exactly, it answers with the closest matches instead. Pass values to fill blanks with the user's details. Ask the user for any blank you cannot fill from the conversation instead of inventing it.
get_prompt input schema
{
"type": "object",
"required": [
"prompt"
],
"properties": {
"prompt": {
"type": "string",
"description": "The slug, registry number or exact title from search_prompts."
},
"values": {
"type": "object",
"description": "Optional: blank name → the user's text, for example {\"job_posting\": \"...\"}.",
"additionalProperties": {
"type": "string"
}
}
}
}get_prompt output schema
{
"type": "object",
"required": [
"id",
"slug",
"title",
"system",
"prompt",
"open_blanks",
"url"
],
"properties": {
"id": {
"type": "string",
"description": "Registry number."
},
"url": {
"type": "string"
},
"slug": {
"type": "string"
},
"title": {
"type": "string"
},
"prompt": {
"type": "string",
"description": "The user message, with the given values filled in."
},
"system": {
"type": "string",
"description": "The system prompt, with the given values filled in. Empty when the template has none."
},
"open_blanks": {
"type": "array",
"items": {
"type": "string"
},
"description": "Blanks still to fill. Ask the user for these."
}
}
}get_prompt annotations
{
"title": "Get prompt",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}list_collections — List the prompt collections
Advertised read-only
List the collections in the thinkhard.si prompt repository, with how many prompts each has.
list_collections input schema
{
"type": "object",
"properties": {}
}list_collections output schema
{
"type": "object",
"required": [
"collections"
],
"properties": {
"collections": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"code",
"name",
"blurb",
"count"
],
"properties": {
"id": {
"type": "string",
"description": "Pass it to search_prompts as collection."
},
"code": {
"type": "string",
"description": "Registry prefix, such as CAR."
},
"name": {
"type": "string"
},
"blurb": {
"type": "string"
},
"count": {
"type": "integer",
"description": "Prompts in the collection."
}
}
}
}
}
}list_collections annotations
{
"title": "List collections",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}grade_prompt — Grade a prompt out of 10
Advertised read-only
Score a prompt out of 10 on the ten checks thinkhard.si uses (what to make, who it is for, background facts, length, format, what to avoid, what good looks like, an example, what to do if unsure, layout for the model). Returns which checks pass and a plain question for each one that fails. It also reads the prompt against the 519 expert prompts in the repository: which task it is, which of that task's inputs are there (a resume, a job posting, a policy), how ready it is for that task out of 10, and the three changes that would help most. Use it to see what a prompt is missing before improving it. The prompt is read to answer and is not stored.
grade_prompt input schema
{
"type": "object",
"required": [
"prompt"
],
"properties": {
"prompt": {
"type": "string",
"description": "The prompt to grade (the user message)."
},
"system": {
"type": "string",
"description": "Optional system prompt, graded together with the prompt."
},
"target": {
"enum": [
"claude",
"gpt",
"gemini",
"any",
"agent",
"midjourney",
"image",
"video"
],
"type": "string",
"default": "any",
"description": "The model it is for. Layout is judged for this model."
}
}
}grade_prompt output schema
{
"type": "object",
"required": [
"score",
"band",
"target",
"checks"
],
"properties": {
"band": {
"type": "string",
"description": "The score in a word."
},
"score": {
"type": "integer",
"description": "Out of 10."
},
"checks": {
"type": "array",
"items": {
"type": "object",
"required": [
"check",
"pass"
],
"properties": {
"pass": {
"type": "boolean"
},
"check": {
"type": "string"
}
}
},
"description": "The ten checks, in order."
},
"engine": {
"type": "object",
"required": [
"readiness",
"match",
"next"
],
"properties": {
"next": {
"type": "array",
"items": {
"type": "object",
"required": [
"kind",
"name",
"label",
"ask"
],
"properties": {
"ask": {
"type": "string",
"description": "What to add, in plain words."
},
"kind": {
"enum": [
"input",
"check"
],
"type": "string"
},
"name": {
"type": "string"
},
"label": {
"type": "string"
},
"expert": {
"type": "string",
"description": "How the expert prompt for this task handles it."
}
}
},
"description": "The changes expected to raise readiness most, best first, at most three."
},
"task": {
"type": "object",
"required": [
"slug",
"title",
"collection",
"url"
],
"properties": {
"url": {
"type": "string"
},
"slug": {
"type": "string",
"description": "Pass it to get_prompt for the expert version."
},
"title": {
"type": "string"
},
"collection": {
"type": "string"
}
}
},
"match": {
"enum": [
"template",
"sure",
"likely",
"unsure",
"none"
],
"type": "string",
"description": "How the task was found: template (the prompt started from that thinkhard.si template), sure, likely or unsure; none when the repository has no such task, and readiness then rests on the ten checks alone."
},
"inputs": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"label",
"status"
],
"properties": {
"name": {
"type": "string",
"description": "The input's blank name in the expert prompt."
},
"label": {
"type": "string"
},
"status": {
"enum": [
"given",
"missing",
"mentioned",
"blank",
"optional"
],
"type": "string",
"description": "given; missing; mentioned (named but not pasted in); blank (left as {{name}}); optional (missing, and the task works without it)."
}
}
},
"description": "What this task needs, in the expert prompt's order."
},
"others": {
"type": "array",
"items": {
"type": "object",
"required": [
"slug",
"title",
"url"
],
"properties": {
"url": {
"type": "string"
},
"slug": {
"type": "string"
},
"title": {
"type": "string"
}
}
},
"description": "Other tasks it might be when the match is not sure, or the nearest ones when no task fits."
},
"readiness": {
"type": "integer",
"description": "Out of 10: how ready the prompt is for this task, from the ten checks weighed for it and the inputs it needs."
}
}
},
"target": {
"type": "string",
"description": "The model it was read for."
}
}
}grade_prompt annotations
{
"title": "Grade prompt",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}estimate_ai_cost — Estimate what an AI feature costs
Advertised read-only
Estimate the monthly cost of running a prompt on current AI models (Claude, GPT, Gemini, DeepSeek, Qwen and others), from thinkhard.si's price catalog, which is checked against each provider's pricing page. Give token counts, or paste the prompt text to estimate them.
estimate_ai_cost input schema
{
"type": "object",
"properties": {
"models": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional: model names or ids to include, such as \"Claude Sonnet 5.5\". Default: every current model."
},
"prompt_text": {
"type": "string",
"description": "Optional: the prompt, to estimate input tokens (about 4 characters a token)."
},
"input_tokens": {
"type": "integer",
"minimum": 0,
"description": "Input tokens per call. Omit to estimate from prompt_text."
},
"output_tokens": {
"type": "integer",
"default": 500,
"minimum": 0,
"description": "Output tokens per call."
},
"calls_per_month": {
"type": "integer",
"default": 1000,
"minimum": 1,
"description": "How many times the prompt runs in a month, across all users (default 1,000)."
}
}
}estimate_ai_cost output schema
{
"type": "object",
"required": [
"checked",
"calls_per_month",
"input_tokens",
"output_tokens",
"models"
],
"properties": {
"models": {
"type": "array",
"items": {
"type": "object",
"required": [
"model",
"ref",
"per_call_usd",
"monthly_usd",
"input_per_million",
"output_per_million",
"note"
],
"properties": {
"ref": {
"type": "string",
"description": "Provider and model id."
},
"note": {
"type": "string",
"description": "Empty unless something about the price needs saying."
},
"model": {
"type": "string"
},
"monthly_usd": {
"type": "number",
"description": "US dollars a month."
},
"per_call_usd": {
"type": "number",
"description": "US dollars per call."
},
"input_per_million": {
"type": "number",
"description": "US dollars per million input tokens."
},
"output_per_million": {
"type": "number",
"description": "US dollars per million output tokens."
}
}
},
"description": "Cheapest first."
},
"checked": {
"type": "string",
"description": "When the prices were last checked against each provider."
},
"input_tokens": {
"type": "integer"
},
"output_tokens": {
"type": "integer"
},
"calls_per_month": {
"type": "integer"
}
}
}estimate_ai_cost annotations
{
"title": "Estimate AI cost",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}fix_bad_answer — Fix a bad AI answer
Advertised read-only
When an AI answer goes wrong (it made up a source or a number, ignored an instruction, came back too long or in the wrong shape, sounded robotic or generic, changed every time, refused, or lost track of a long chat), find the likely cause and the exact line to add to the prompt. Draws on the thinkhard.si troubleshooter of 33 common problems. Describe what went wrong in plain words.
fix_bad_answer input schema
{
"type": "object",
"required": [
"problem"
],
"properties": {
"limit": {
"type": "integer",
"default": 3,
"maximum": 5,
"minimum": 1,
"description": "Optional: how many likely causes to return, best match first (1 to 5, default 3)."
},
"problem": {
"type": "string",
"description": "What went wrong, in plain words, for example \"it invented a statistic\" or \"it keeps ignoring my word limit\"."
}
}
}fix_bad_answer output schema
{
"type": "object",
"required": [
"matches"
],
"properties": {
"matches": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"problem",
"kind",
"why",
"fix",
"line_to_add",
"url"
],
"properties": {
"id": {
"type": "string"
},
"fix": {
"type": "string",
"description": "What to change."
},
"url": {
"type": "string"
},
"why": {
"type": "string",
"description": "Why the model does it."
},
"kind": {
"type": "string",
"description": "The kind of problem."
},
"problem": {
"type": "string",
"description": "The problem, as the troubleshooter names it."
},
"line_to_add": {
"type": "string",
"description": "A line to paste into the prompt; {{blanks}} are for the user's details."
}
}
},
"description": "Best match first. Empty when nothing matches."
}
}
}fix_bad_answer annotations
{
"title": "Fix a bad answer",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}get_prompt_pattern — Get a prompt pattern
Advertised read-only
The 24 prompt patterns from thinkhard.si: small moves that change the answer, such as giving the facts, naming the reader, showing one example, setting a length, fencing off pasted text or asking for reasoning first. Each comes with when it helps, when it does not, a before-and-after pair with scores, and the line to add. Ask by a pattern's name or by what you want the prompt to do better; leave the query empty to list all 24.
get_prompt_pattern input schema
{
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 3,
"maximum": 24,
"minimum": 1,
"description": "Optional: how many patterns to return, best match first (1 to 24, default 3). Ignored when the query is empty."
},
"query": {
"type": "string",
"description": "A pattern's name, or what to improve, such as \"stop it inventing numbers\" or \"answers are too generic\". Leave it out to list every pattern."
}
}
}get_prompt_pattern output schema
{
"type": "object",
"required": [
"patterns"
],
"properties": {
"patterns": {
"type": "array",
"items": {
"type": "object",
"required": [
"slug",
"name",
"group",
"summary",
"what",
"when",
"limits",
"line_to_add",
"before",
"before_score",
"after",
"after_score",
"url"
],
"properties": {
"url": {
"type": "string"
},
"name": {
"type": "string"
},
"slug": {
"type": "string"
},
"what": {
"type": "string",
"description": "What the pattern is."
},
"when": {
"type": "string",
"description": "When it helps."
},
"after": {
"type": "string",
"description": "The same prompt with it."
},
"group": {
"type": "string",
"description": "Which part of a prompt it works on."
},
"before": {
"type": "string",
"description": "A prompt without the pattern."
},
"limits": {
"type": "string",
"description": "When it does not."
},
"summary": {
"type": "string"
},
"after_score": {
"type": "integer",
"description": "Its score out of 10."
},
"line_to_add": {
"type": "string",
"description": "The line to add, with {{blanks}}."
},
"before_score": {
"type": "integer",
"description": "Its score out of 10."
}
}
},
"description": "Best match first; all 24 when no query is given."
}
}
}get_prompt_pattern annotations
{
"title": "Get prompt pattern",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}define_ai_term — Define an AI term
Advertised read-only
Plain-English definitions of 97 AI words from the thinkhard.si glossary (token, context window, hallucination, temperature, system prompt, RAG, fine-tuning, agent, MCP and more), written for people who use AI at work rather than build it.
define_ai_term input schema
{
"type": "object",
"required": [
"term"
],
"properties": {
"term": {
"type": "string",
"description": "The word or phrase, such as \"context window\" or \"RAG\"."
},
"limit": {
"type": "integer",
"default": 3,
"maximum": 5,
"minimum": 1,
"description": "Optional: how many definitions to return, closest match first (1 to 5, default 3)."
}
}
}define_ai_term output schema
{
"type": "object",
"required": [
"terms"
],
"properties": {
"terms": {
"type": "array",
"items": {
"type": "object",
"required": [
"id",
"term",
"definition",
"group",
"url"
],
"properties": {
"id": {
"type": "string"
},
"url": {
"type": "string"
},
"term": {
"type": "string"
},
"group": {
"type": "string"
},
"definition": {
"type": "string",
"description": "In plain English."
}
}
},
"description": "Best match first. Empty when nothing matches."
}
}
}define_ai_term annotations
{
"title": "Define AI term",
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Prompts
500 captured; incomplete (item-cap)
upset-customer-reply — Reply to an upset customer
A customer is angry or frustrated, and you need a reply that calms things down without promising what your policy does not allow.
- company
- Your company or product name.
- policy
- The refund, credit and escalation rules the reply must follow, pasted from your policy or macros.
- account_facts
- What your systems show about this customer and the issue: order, dates, charges, earlier contacts.
- customer_message
- The customer's message, exactly as received.
- agent_name
- The name the reply is signed with.
support-ticket-triage — Triage support tickets into JSON
You want every incoming ticket labeled with a category, an urgency and a summary, in a shape a script can route.
- product
- Your product or service name.
- categories
- Your categories, one per line, each with a short definition, for example "billing: charges, refunds, invoices".
- ticket
- The ticket text, inserted by your app for each ticket.
help-center-article — Turn resolved tickets into a help-center article
The same question keeps coming in, and you want a help article written from how your team actually solved it.
- product
- Your product name.
- resolved_tickets
- Three or more resolved tickets on the same question, including the replies that fixed it. Remove customer details first.
- product_facts
- Anything else true and current: plan limits, where the setting lives, known bugs.
escalation-summary — Summarize a long support thread for escalation
A case has bounced between people for days, and you need to hand it to an engineer or manager who has read none of it.
- escalation_team
- Who receives the case, for example "the payments engineering on-call" or "the account manager".
- thread
- The whole thread: emails, chat transcript and internal notes, oldest first.
cold-email-first-touch — Write a first cold email that is about them
You are writing to a specific prospect for the first time and have real notes on them, not a list of ten thousand names.
- company
- Your company name.
- offer
- What you sell and the specific problem it solves, in a few sentences.
- proof_points
- Results or customers you are allowed to mention. Write "none" if you have none yet.
- prospect_name_and_role
- For example "the head of operations", with their name.
- prospect_company
- The prospect's company.
- prospect_notes
- What you actually know: a post they wrote, a job opening, a launch, a talk. Include where you saw it.
landing-page-copy — Draft landing page copy from product facts
You have a product or feature to launch and a page to fill, and you want copy built from what is true, not from hype.
- product
- The product or feature name.
- audience
- Who the page is for, as specifically as you can, for example "finance leads at companies with 50 to 200 staff".
- primary_action
- The one action the page asks for, for example "start a free trial" or "book a demo".
- product_facts
- Everything true about the product: what it does, how, for whom, prices, limits, proof you can publish.
- voice_sample
- A few paragraphs of your existing copy to match. Leave it empty for a plain default.
ad-copy-variants — Write ad variants within character limits
You need a set of headline and description options for a search or social ad, each under the platform's limits and each testing a different angle.
- product_facts
- What the product does, for whom, and any proof or offer you are allowed to advertise.
- audience
- Who the ad is for.
- keywords
- The search terms or interests you are targeting, comma separated.
- char_limits
- Your platform's limits, for example "headline 30, description 90". Check the platform's current rules.
- platform
- Where the ad runs, for example Google search ads or LinkedIn.
- past_ad
- Optional. An ad of yours that performed well, so the new ones match its voice. Leave it empty if you have none.
case-study-from-interview — Turn a customer interview into a case study
You have notes or a transcript from a happy customer and want a case study that sticks to what they actually said.
- publish_where
- Where it will appear, for example "website", "sales deck" or "newsletter".
- company
- Your company name.
- customer_name
- The customer company's name.
- customer_industry
- Their industry and size, for example "regional logistics, 300 staff".
- approval_notes
- Which quotes and figures the customer approved for publication, or "none yet".
- interview
- The transcript or your notes from the interview.
line-edit-keep-voice — Edit a draft for clarity without losing your voice
Your draft says the right things but reads heavily, and you want it tightened, not rewritten by someone else.
- draft
- The text to edit.
- audience
- Who will read it.
- where_it_appears
- For example company blog, board memo or LinkedIn post.
- keep_as_is
- Product names, legal wording or phrases that must not change. Write "none" if there are none.
executive-summary — Summarize a long document for a busy executive
A decision-maker needs to grasp a long report, proposal or thread in two minutes and see what they are being asked to decide.
- reader
- Who reads the summary, for example "our CFO" or "the board".
- document
- The report, proposal or thread to summarize.
plain-language-rewrite — Rewrite expert text in plain language
You have technical, legal-sounding or specialist text that ordinary readers need to understand and act on.
- audience
- Who will read it, for example "tenants" or "first-time customers".
- reader_goal
- What the reader must be able to do afterward, for example "decide whether to apply".
- text
- The text to rewrite.
- reading_grade
- A US school grade level, for example 8 for a general audience.
coding-agent-bug-fix — Brief a coding agent to fix a bug
You are handing a bug to Claude Code, Codex or another coding agent and want a root-cause fix with proof, not a guess.
- symptom
- What goes wrong, in one sentence.
- expected_behavior
- What correct behavior looks like, as specifically as you can.
- location
- The files, functions or endpoints involved, as far as you know.
- repro_steps
- The steps or the request that triggers the bug.
- error_output
- The exact error, stack trace or log lines, pasted rather than described.
- ruled_out
- What you already checked, so the agent does not repeat it. "Nothing yet" is fine.
- off_limits
- Files, folders or systems that must not change, for example migrations or generated code.
- test_command
- The command that runs the tests, for example npm test or pytest.
coding-agent-write-tests — Brief a coding agent to add tests before a refactor
A module has thin or no test coverage, and you want an agent to pin down its behavior without changing it.
- module_path
- The file or folder to test, for example src/billing/invoice.ts.
- test_command
- The command that runs the tests, for example npm test or pytest.
- pattern_test_file
- An existing test file whose style the new tests should copy.
- module_purpose
- One or two sentences on what the code does and what depends on it.
- known_cases
- Inputs and results you know matter, for example "an order with zero items is rejected". "None" is fine.
explain-unfamiliar-code — Explain unfamiliar code before you change it
You have inherited code you did not write and need to understand what it really does before touching it.
- language
- The language and framework, for example "TypeScript with React".
- file_path
- The file's path, so the explanation can refer to it.
- code
- The code to explain, with line numbers if your editor can copy them.
- related_context
- Anything that helps: the caller, the types, a README section. Leave it empty if you have nothing.
- planned_change
- What you intend to change, in one sentence.
pull-request-description — Write a pull request description from a diff
You have finished a change and want a description reviewers can use, with the why, the risks and how to test it.
- team
- The team or repository the reviewers belong to.
- notes
- Why you made the change, the ticket link, and how you tested it.
- diff
- The output of git diff, or the changed files.
survey-response-themes — Find themes in open-ended survey responses
You have hundreds of free-text answers and need themes with real counts and exact quotes, not an impression.
- survey_question
- The exact question respondents answered.
- responses
- The answers, one per line. Remove names and email addresses first.
- stakeholders
- Who will see the results, for example "the product leadership team".
- decision
- What they will decide with it, for example "which of three features to build next".
spreadsheet-formula — Write a spreadsheet formula from a plain description
You know what you want a spreadsheet to calculate, but not the formula, and you want one others can maintain.
- spreadsheet_app
- For example Excel for Microsoft 365, Google Sheets or LibreOffice Calc.
- what_it_should_do
- The calculation in plain words, for example "total sales per region for the current month".
- sheet_layout
- Sheet names, which columns hold what, whether row 1 has headers, and roughly how many rows.
- target_cell
- Where the formula goes, for example Summary!B2.
- locale
- For example US with commas, or a locale that separates arguments with semicolons.
explain-metric-change — Explain why a metric moved
A number went up or down and you need a careful write-up of what the data does and does not show before anyone acts on it.
- audience
- Who the explanation is for, for example "the weekly leadership meeting".
- metric_name
- The metric's name.
- metric_definition
- How it is calculated, for example "paid orders divided by sessions".
- change
- What moved, for example "down from 3.1% to 2.6%".
- periods
- The periods compared, for example "the week of October 6 against the four weeks before".
- data
- A table or CSV with the metric by period and by segment, such as channel, platform or region.
- known_events
- Anything that happened in the period. Write "none known" if nothing did.
user-interview-synthesis — Synthesize user interviews into findings
You have run several customer interviews and need findings backed by counts and quotes, not the loudest anecdote.
- research_goal
- What the research set out to learn, ideally as two to four questions.
- interview_notes
- Notes or transcripts, each starting with a label such as P1. Remove names first.
- team
- Who will use the findings.
- decision
- What they will decide, for example "whether to rebuild onboarding this quarter".
one-page-product-spec — Turn feature notes into a one-page spec
You have a feature idea and scattered notes, and need a short spec that engineers and designers can challenge before work starts.
- feature
- The feature's working name.
- team
- The team that will build it.
- notes
- Meeting notes, a chat thread, customer requests, rough ideas: whatever you have.
competitor-comparison — Compare competitors from pages you paste
You want a fair side-by-side comparison of competing products, based on their own current pages rather than the model's memory.
- competitor_pages
- Text copied from each competitor's own pages (pricing, features, docs), each starting with the product name, URL and date copied.
- our_product
- The same facts about your product.
- criteria
- What to compare, one per line, for example pricing model, single sign-on, API access, data residency.
- use_case
- What the comparison is for, for example "sales battlecard" or "positioning review".
job-description — Write an inclusive job description
You are opening a role and want a post that attracts people who could do the job well and promises nothing you have not agreed.
- role_title
- The job title as it will be posted.
- team
- The team, who the role reports to, and who they work with most.
- location
- For example "remote within the US" or "hybrid, three days a week in the office".
- pay_range
- The range you will publish. Leave it empty if it is not decided.
- role_notes
- What the person will do, why the role exists now, and what success looks like after six months.
- benefits
- Benefits and perks that are actually offered.
- how_to_apply
- Where and how to apply, and what to include.
- past_post
- Optional. A job post of yours that drew good candidates, so the new one matches its tone. Leave it empty if you have none.
contract-clause-plain-english — Explain contract clauses in plain English (not legal advice)
You have been sent an agreement and want to understand what it says, and what to ask a lawyer, before you sign.
- contract_text
- The clauses you want explained, copied exactly. Remove names and account numbers if you prefer.
- my_role
- Your side of the agreement, for example the customer, the contractor or the tenant.
- jurisdiction
- Country or state, or "unknown".
- concerns
- For example getting out early, liability if something goes wrong, or who owns the work.
standard-operating-procedure — Turn a messy process into a standard operating procedure
A process lives in one person's head or a chat thread, and you need a checklist anyone on the team can follow.
- who_follows_it
- Who will follow it, for example "a new support hire in their first week".
- where_it_lives
- For example the team wiki or a shared drive.
- process_name
- The process's name.
- trigger
- For example "every Monday" or "when a customer asks for a data export".
- process_notes
- How it is done today: notes, chat messages, or a transcript of someone walking through it.
customer-assistant-system-prompt — Hardened system prompt for a customer-facing assistant
You are putting a chat assistant in front of customers, and it must stay on topic, protect personal data, resist manipulation and hand off to a person.
- company
- Your company or product name.
- channel
- Where the assistant runs, for example "the help widget on our website".
- scope
- What the assistant may help with, for example "orders, shipping, returns and account settings".
- knowledge
- Your help articles, policies and facts, pasted in. Only what the assistant is allowed to share.
- handoff_method
- How a handoff happens, for example "tell the customer you are connecting them, then reply with HANDOFF on its own line".
- input
- The customer's message. Your app inserts it at run time; the Chatbot Safety Test puts its attack probes here.
rag-answer-with-citations — Document answerer that cites sources and refuses outside them
You are building retrieval-augmented answers (RAG) over your own documents and need cited answers, with a clean refusal when the documents do not cover the question.
- audience
- Who asks the questions, for example "employees" or "developers using our API".
- source_description
- Where the documents come from, for example "our HR policies, each dated when last revised".
- documents
- The retrieved passages, inserted by your app, each wrapped like <doc id="doc-1" title="..." date="...">...</doc>.
- input
- The user's question, inserted by your app at run time.
tool-using-agent-system-prompt — System prompt for an agent that uses tools safely
You are giving a model tools that read and change things, and it must confirm before anything irreversible and never act on instructions hidden in tool results.
- user_description
- Who the agent works for, for example "the operations team at a small online store".
- environment
- The systems it can reach, for example "our shared drive, calendar and order system".
- forbidden_actions
- Actions that are never allowed, for example "deleting customer records, emailing anyone outside the company".
- input
- The user's request, inserted by your app at run time.
midjourney-product-photo — Midjourney studio product photo
You need a clean, catalog-style product image for a store listing, an ad or a mockup.
- product
- The product, specifically, for example "a pour-over coffee dripper".
- material
- What it is made of, for example "matte black ceramic".
- surface
- What it stands on, for example "a pale oak table".
- background_color
- The backdrop color, for example "warm light gray".
- key_detail
- The feature the shot should show off, for example "the ribbed inner wall".
- style_reference
- An image URL or style code to match. If you have none, delete --sref and this value.
blog-header-image-with-text — Blog header illustration with a rendered headline
You want a header or social image with a short headline set in it, from a plain-language image model such as Nano Banana or GPT Image.
- topic
- What the post is about.
- publication
- Who reads it, for example "a developer blog" or "a small-business newsletter".
- scene
- The concrete picture, for example "a paper airplane folded from an invoice, flying over a row of filing cabinets".
- palette
- Three or four colors, for example "deep navy, cream and soft coral".
- headline
- The exact words to render. Shorter headlines render more reliably.
product-video-shot — Product video shot with sound, for Veo or Runway
You need a short b-roll clip of a product for a landing page, an ad or a social post, from a text-to-video model.
- subject
- The product, specifically, for example "a brushed-steel insulated water bottle".
- action
- What happens, for example "with condensation running down its side".
- setting
- Where it stands, for example "a stone kitchen counter by a window".
- use_case
- Where the clip will be used, for example "landing page hero" or "social ad".
- detail
- The last thing the camera settles on, for example "the engraved logo on the lid".
- duration_seconds
- A clip length your video model supports; check its settings.
- sound_effects
- One or two sounds, for example "the faint fizz of a freshly poured drink".
interview-scorecard-for-role — Build a structured interview plan and scorecard for a role
You are about to interview for a role and want every interviewer asking job-related questions and scoring answers against the same bar.
- role_title
- The job title, as posted.
- role_requirements
- What the person will do and what the job truly needs: the job description, plus the hiring manager's notes on what success looks like.
- interview_stages
- The stages and who runs each, for example "phone screen with the recruiter, skills interview with the team lead, panel with two peers".
- interview_length
- How long each interview lasts, for example 45 minutes.
- interviewers
- Who will use the plan, for example "the hiring manager and three team members".
interview-notes-to-scorecard-feedback — Turn rough interview notes into evidence-based feedback
You have just finished an interview and need to write up feedback for the hiring team from scribbled notes, tied to the scorecard and free of snap judgments.
- role_title
- The job title.
- scorecard
- The competencies you were asked to assess and the scoring guide for each, from the interview plan.
- interview_notes
- Your notes from the interview, as rough as they are.
candidate-rejection-after-interview — Write a kind rejection email after an interview
A candidate interviewed and will not move forward, and you want to tell them clearly and respectfully without saying anything you would regret.
- candidate_first_name
- The candidate's first name.
- role_title
- The job title.
- company
- Your company name.
- sender_name
- The name the email is signed with.
- stage_reached
- For example "final panel interview" or "first interview with the hiring manager".
- approved_feedback
- Feedback the hiring team has agreed to share, tied to the role's requirements. Write "none" to give no reason.
- future_contact
- For example an invitation to apply for future roles, only if you mean it. Write "none" otherwise.
reference-check-call-guide — Prepare a reference check call
You are about to call a candidate's references and want questions that get specific, job-related answers rather than polite generalities.
- role_requirements
- What the job needs, from the job description or interview plan.
- open_questions
- Concerns or gaps from the interviews you want the reference to speak to. Write "none" if there are none.
- reference_relationship
- For example "their manager at their last job for two years".
- call_length
- For example 15 minutes.
- role_title
- The job title.
new-hire-onboarding-plan — Plan a new hire's first 90 days
Someone is starting soon and you want a week-by-week plan that gets them productive without burying them in their first week.
- role_title
- The new hire's job title.
- team
- The team they are joining.
- start_date
- Their first day.
- day_90_outcome
- What they should be doing on their own by day 90, for example "run month-end reconciliations for two entities".
- experience
- The relevant experience they bring, from their resume or interviews, in a sentence or two.
- people_to_meet
- People and teams they should meet, one per line, with why.
- resources
- Tools, documents, training and accounts they will need.
hr-policy-employee-faq — Turn an HR policy into an employee FAQ
A policy is accurate but hard to read, and you want an FAQ employees can follow, with every answer traceable to the policy text.
- policy_text
- The policy, pasted in full, with its section numbers or headings.
- common_questions
- Questions employees already ask about this policy, one per line. Write "none" if you have none.
- audience
- Who the policy applies to, for example "all US hourly staff".
- contact
- Who employees should ask, for example "your HR business partner".
- owner
- Who checks the FAQ before it goes out, for example "the HR policy owner".
exit-interview-themes — Find patterns in exit interview notes
You have a stack of exit interview notes or survey answers and want honest patterns about why people leave, with counts and quotes, without identifying anyone.
- exit_responses
- Exit interview notes or survey answers, one person per entry, each labeled E1, E2 and so on. Remove names first.
- period
- The period covered, for example "the last 12 months".
- leaver_count
- How many people left in the period. Write "unknown" if you do not have it.
- decision
- What leadership wants to decide, for example "where to spend next year's retention budget".
- audience
- Who reads the summary, for example "the leadership team".
workplace-complaint-interview-summary — Summarize workplace investigation interviews neutrally
You are looking into a workplace complaint and need a neutral record of what each person said, kept apart from any conclusion, for the person who will decide.
- decision_maker
- Who decides the outcome, for example "the head of HR".
- advisor
- Who advises them, for example "employment counsel", or "no one".
- complaint
- The complaint as it was received, with personal details that are not needed removed.
- interview_notes
- Notes from each interview, labeled by role rather than name.
- policy
- The policy sections that may apply, pasted in. Write "none yet" if you have not identified them.
performance-review-from-manager-notes — Draft a performance review from your own notes
Review season is here and you have a year of notes, a self-review and peer feedback, and you need a fair, specific first draft to edit.
- review_guidelines
- Your company's review form or guidance: sections, rating scale, any word limits. Write "none" if there is none.
- goals
- The goals set for this period.
- manager_notes
- Your notes from the period: wins, misses, 1:1 notes, feedback you gave. Dates help.
- self_review
- The employee's self-review, or "none".
- peer_feedback
- Feedback from peers or stakeholders, or "none".
- employee_role
- Who the review is for, for example "the senior analyst on my team". A first name is enough.
- review_period
- For example "the first half of the year".
- intended_rating
- The rating you plan to give, on your company's scale. You decide it; the draft does not.
one-on-one-meeting-agenda — Prepare a 1:1 agenda with a direct report
You have a 1:1 coming up and want it to be about their work and growth, not another status update.
- report_role
- Who the 1:1 is with, for example "Sam, a product designer on my team".
- meeting_length
- For example 30 minutes.
- previous_notes
- Your notes from the last one to three 1:1s, including actions.
- current_work
- Their current projects, deadlines and anything you have noticed.
- growth_goals
- What they are working toward, for example "leading a project end to end".
- feedback_to_give
- The situation and what you observed. Write "none" if there is nothing this time.
delegate-a-task-brief — Write a clear brief when you delegate a task
You are handing work to someone on your team and want them to know the outcome, their authority and when you will check in, without micromanaging.
- person
- Who you are delegating to, by first name or role.
- experience_level
- For example "has done similar work twice" or "new to this kind of task".
- task_notes
- What needs doing, the deadline, budget, who is involved, what you care about and anything that is not negotiable.
decision-memo-with-options — Write a decision memo with options and a recommendation
A decision needs sign-off from someone senior, and you want the options, the trade-offs and your recommendation on one page.
- background
- The situation, why a decision is needed now, and anything already decided.
- options
- Each option you considered, with what you know about its costs, benefits and risks.
- criteria
- What the decision should be judged on, one per line, for example cost, time to launch, risk to customers.
- decision_maker
- Who decides, for example "the COO".
- deadline
- When the decision is needed.
- my_recommendation
- The option you recommend, or "none yet" for a neutral comparison.
difficult-conversation-plan — Plan a difficult conversation with someone on your team
You need to raise a problem with a direct report, such as missed deadlines or friction with colleagues, and want to open well and stay on the facts.
- situation
- The problem in a few sentences, for example repeated missed deadlines or friction with a colleague.
- observations
- Specific things you saw or heard yourself, with dates. Say which ones are second-hand.
- desired_outcome
- What you want to come out of the conversation, for example "an agreed plan for the next two deadlines".
- context
- Anything relevant: earlier conversations, their workload, recent changes. Write "none" if there is nothing.
- person
- Their role or first name.
- hr_contact
- Who to involve, for example "our HR business partner".
team-change-announcement — Announce a change to your team
Something is changing for your team, such as a reorg, new priorities or a new process, and you need to explain it clearly before rumors do it for you.
- team
- Who receives it, for example "the customer operations team".
- channel
- For example email, a team chat post, or a script for a team meeting.
- change_notes
- What is changing and when, why, who is affected and how, and what is decided versus still open.
- not_shareable
- Anything that must not be shared yet. Write "none" if everything can be shared.
quarterly-team-goals — Draft measurable quarterly goals for your team
Planning season is here and you need a few team goals that tie to company priorities and can be checked at the end of the quarter.
- company_priorities
- The company's priorities or goals for the period, as leadership wrote them.
- team_scope
- What the team owns, in a sentence or two.
- capacity
- Who is available next quarter, for example "five engineers, one on leave for half the quarter".
- last_quarter
- Results against last quarter's goals, with numbers where you have them.
- committed_work
- Work already promised for next quarter. Write "none" if there is none.
- team_name
- The team's name.
budget-variance-commentary — Write budget vs. actual variance commentary
Month-end numbers are in and you need commentary on the variances that matter, with drivers you can trace and unconfirmed causes clearly marked.
- budget_vs_actual
- The budget vs. actual table by line for the period, pasted as CSV or a copied table.
- driver_notes
- What you know about why lines moved: notes from budget owners, known events. Write "none" if you have nothing yet.
- period
- For example "September" or "the third quarter".
- threshold
- Your materiality rule, for example "over 5 percent and over 10,000".
- audience
- Who reads the report, for example "department heads in the monthly leadership pack".
- key_line
- The line the summary leads with, for example operating profit or total operating expenses.
overdue-invoice-reminder-sequence — Write overdue invoice reminders that escalate politely
A customer has not paid and you need a short series of reminders, from a friendly nudge to a firm final notice, that stay professional.
- sender_name
- Who signs the emails.
- company
- Your company name.
- stage_1
- When to send the first reminder, for example "3 days after the due date".
- stage_2
- When to send the second, for example "14 days after the due date".
- stage_3
- When to send the final notice, for example "30 days after the due date".
- customer_name
- The customer's company or name.
- invoice_details
- Invoice number, amount with currency, and original due date.
- how_to_pay
- The payment link or instructions, as you would give them to the customer.
- customer_history
- How long they have been a customer, their payment record, and any replies about this invoice.
- consequences
- What your terms allow you to say, such as a late fee in your contract or pausing work. Write "none" to mention no consequence.
explain-pnl-to-budget-owners — Explain a P&L to colleagues outside finance
You need department heads or a founder to understand a profit and loss statement well enough to make decisions, without an accounting lesson.
- audience
- Who will read it, for example "department heads" or "our founder".
- reader_goal
- What they need to do with it, for example "plan next quarter's hiring".
- period
- The period the P&L covers.
- comparison
- What it is compared with, for example "the same month last year" or "budget".
- pnl
- The P&L as a table or CSV, with column headings and units.
- finance_notes
- What finance knows about the period's movements. Write "none" if there are none.
expense-policy-assistant-system-prompt — System prompt for an expense policy assistant
You want an internal assistant that answers expense questions from your actual policy, sends edge cases to finance and never approves anything itself.
- company
- Your company name.
- channel
- Where the assistant runs, for example "the finance help channel in our team chat".
- policy
- Your current expense and travel policy, pasted in full, with section names.
- finance_contact
- Who handles questions the policy does not answer, for example "the expenses team at the finance inbox".
- input
- The employee's question. Your app inserts it at run time; the Chatbot Safety Test puts its probes here.
spend-request-business-case — Make the case for a purchase or budget request
You want approval to buy a tool, hire a contractor or add budget, and need a short business case that finance can check line by line.
- request
- What you want to buy or fund, in one line.
- cost
- The quoted price and its terms, for example per seat per month, plus any setup fee.
- budget_line
- Where the money would come from, or "new budget".
- problem_and_benefits
- The problem today and what the purchase would change, with any numbers you have and where they come from.
- alternatives
- Other options you looked at, including doing nothing, with what you know about each.
- approver
- Who decides, for example "the finance director".
vendor-invoice-discrepancy-email — Query a supplier invoice that does not match the order
A supplier invoice does not match the purchase order or what was delivered, and you need a clear, polite email that gets a corrected invoice.
- supplier_contact
- The person at the supplier who handles billing, if you know them.
- supplier
- The supplier's name.
- sender_name
- Who will send the email.
- invoice_details
- The invoice lines, quantities, prices, totals, invoice number and date, copied from the invoice.
- our_records
- The matching purchase order lines and what was received, with dates.
- terms
- Payment terms and any agreed prices or discounts, for example "net 30, agreed price 40.00 per unit".
vendor-proposal-comparison — Compare vendor proposals against your requirements
You have several quotes or proposals for the same need and want a fair side-by-side comparison against your criteria, with every claim traced to a proposal.
- requirements
- What you need, one per line, each marked must-have or nice-to-have.
- proposals
- Each proposal or quote as text, starting with the vendor's name and the date it was sent.
- cost_basis
- The basis for comparing cost, for example "total over 3 years for 60 users, including setup".
- need
- What you are buying, for example "a payroll provider".
- decision_makers
- Who will choose, for example "the operations lead and the finance director".
contract-terms-against-playbook — Check a contract against your standard terms before legal review
A vendor or customer sent their own contract, and you want to know where it departs from your usual terms so your lawyer's time goes to what matters.
- playbook
- Your standard positions or contract playbook: your usual terms on liability, payment, termination, data and so on, and which matter most.
- contract_text
- The contract, or the sections to compare, copied exactly with clause numbers.
- our_role
- For example customer, supplier or partner.
- deal_summary
- What the contract is for, in a sentence.
- governing_law
- The law named in the contract, or "not stated".
- reviewer
- Who will review it, for example "our outside counsel".
rfp-response-draft — Draft RFP or questionnaire answers from approved content
A request for proposal or a vendor questionnaire has dozens of questions, and you want first-draft answers built only from content your team has already approved.
- company
- Your company name.
- owner
- Who reviews and approves the answers, for example "the bid manager".
- answer_limits
- The buyer's word or character limits, for example "250 words per answer", or "none stated".
- questions
- The buyer's questions, numbered as in their document.
- approved_content
- Your approved answer library, past submissions, policies or product facts, each labeled with a short source name.
operational-incident-review — Write a blameless review of an operational incident
Something went wrong, such as a missed shipment, a payment run error or an outage, and you need a factual review that leads to fixes rather than blame.
- audience
- Who will read the review, for example "the operations team and the head of operations".
- owner
- Who owns the review, for example "the operations manager".
- incident_notes
- Everything you have: timeline notes, chat messages, emails, system logs, with times where possible.
- impact
- Who or what was affected and how, as far as you know.
- actions_taken
- What has already been done to fix or contain it.
raci-chart-from-project-notes — Turn project notes into a RACI chart
A project or process involves several people and teams, and nobody is sure who decides, who does the work and who just needs to know.
- project_notes
- Notes on the project or process: activities, decisions, meeting notes, chat threads about who does what.
- people
- The people and teams involved, one per line, with their role.
- project_name
- The project or process name.
refund-return-decision-reply — Explain a refund or return decision within policy
Someone has already decided whether a refund or return is approved, partly approved or declined, and you need a reply that explains it clearly and fairly.
- company
- Your company or shop name.
- refund_policy
- Your refund and return policy, pasted as customers see it.
- order_facts
- What your systems show: order date, items, amounts, delivery date, earlier contacts.
- customer_request
- The customer's message, exactly as received.
- decision
- The outcome: approved, partly approved or declined, and for which items.
- decision_reason
- Why, in your own words, for example "outside the 30-day window".
- alternatives
- What the customer can still do, such as an exchange or a repair. Write "none" if nothing applies.
- agent_name
- The name the reply is signed with.
cancellation-request-reply — Reply to a cancellation request without making it hard
A customer wants to cancel a subscription or service, and you want to confirm it cleanly, with one relevant alternative if you have one to offer.
- company
- Your company or product name.
- service
- What is being canceled, for example "the monthly plan" or "weekly cleaning visits".
- agent_name
- The name the reply is signed with.
- cancellation_facts
- How cancellation works: whether you can cancel for them, when access ends, and what happens to billing, data and any refund.
- approved_alternatives
- Alternatives you are allowed to offer, each with who it suits. Write "none" if you offer none.
- customer_message
- The customer's message, exactly as received.
support-macro-rewrite — Rewrite a saved reply so it sounds like a person
Your team's macros or canned responses read stiff or out of date, and you want them clearer and warmer without losing any policy detail.
- macro_text
- The saved reply as it is today, including its fill-in fields.
- must_keep
- Wording that must not change, such as legal text or a plan name. Write "none" if nothing must.
- voice_notes
- How your team sounds, in a few words or a sample reply you like.
- channel
- Where agents mainly send it, for example email or in-app messages.
- company
- Your company or product name.
outage-customer-update — Write a customer update during an outage or incident
Something is broken or slow for customers, and you need a status update that says what is known and what is not, without promising a fix time.
- company
- Your company or product name.
- channel
- Where it goes, for example "our status page and an in-app banner".
- as_of_time
- The time and time zone these facts refer to.
- incident_notes
- What the incident team knows: affected features, regions or plans, symptoms, any workaround, current status.
- approved_to_share
- What the incident lead has cleared for customers, such as the cause. Write "symptoms only" if nothing else is cleared.
- next_update_time
- When the next update will be posted, for example "within the hour".
support-contact-reasons-report — Find the top reasons customers contact support
You have a month of ticket subjects or summaries and want to show the product team which problems cause the most contacts, with counts and examples.
- ticket_export
- One ticket per line with its ID and subject or summary, exported from your help desk. Remove personal details first.
- period
- The dates the export covers.
- known_issues
- Known bugs and existing help articles on these topics, or "none".
- audience
- Who reads it, for example "the product team's monthly review".
cold-email-follow-ups — Write follow-ups for a cold email that got no reply
You sent a first email to a prospect and heard nothing, and want two or three follow-ups that each add something new instead of just bumping the thread.
- company
- Your company name.
- first_email
- The first email you sent, with its subject line.
- prospect_notes
- What you know about the prospect and their company, with where you saw it.
- follow_up_material
- Things you can use, one per line: a customer result you may share, an article, an event, a new feature.
- number_of_follow_ups
- How many follow-ups, usually 2 or 3.
- spacing
- The gap between emails, for example "3 to 5 business days apart".
discovery-call-prep-brief — Prepare for a discovery call from the prospect's own website
You have a first call with a prospect coming up and want a one-page brief with hypotheses and questions, built from their site and your notes rather than guesses.
- company
- Your company name.
- prospect_contact
- Who you are meeting and their role.
- prospect_company
- The prospect's company.
- call_length
- For example 30 minutes.
- our_offer
- What you sell and the problems it solves.
- ideal_customer
- What a good-fit customer looks like, and the signs of a poor fit.
- prospect_pages
- Text copied from their website, such as the home, about, careers or product pages, each labeled with the page name.
- call_notes
- How the meeting came about, what they asked for, anything from earlier emails. "None" is fine.
linkedin-post-from-project — Write a LinkedIn post about a real project or result
You finished something worth sharing at work and want a post that tells what happened and what you learned, without sounding like a motivational poster.
- my_role
- Your job title and field, for example "operations manager at a logistics company".
- audience
- Who you want to read it, for example "other operations managers".
- post_goal
- What the post is for, for example "to share what we learned" or "to show the kind of work our team does".
- project_notes
- What happened: the problem, what you did, the result, and what you learned.
- shareable_facts
- Numbers, client names and details cleared for public use, or "nothing beyond the notes".
- voice_sample
- One or two posts you wrote before. Leave it empty for a plain default.
seo-titles-meta-descriptions — Write SEO titles and meta descriptions for a set of pages
You have a batch of pages that need title tags and meta descriptions written to length, each matching what the page actually says.
- pages
- For each page: its URL, its target keyword, and its main text or a summary of it, clearly separated.
- brand
- Your brand or site name as it should appear.
- searchers
- Who searches for these pages and what they want, for example "homeowners comparing roof repair costs".
- title_limit
- Your title length limit, for example 60. Check your SEO tool's current guidance.
- description_range
- Your description length range, for example "120 to 155". Check your SEO tool's current guidance.
newsletter-from-notes — Turn rough notes into an email newsletter
You have a pile of updates, links and half-sentences for this month's newsletter and want a readable issue in your own voice.
- newsletter_name
- The newsletter's name.
- sender
- Who it comes from, a person or the business.
- audience
- Who subscribes, for example "customers of a garden center".
- reader_value
- Why readers open it, for example "what's new in the shop and upcoming workshops".
- notes
- Everything for this issue: updates, links, dates, prices, half-written thoughts.
- past_issue
- A previous issue to match for voice. Leave it empty if this is the first.
- section_count
- How many sections, for example 3 or 4.
sales-call-recap-email — Send a recap email after a sales call
You just finished a call with a prospect and want to send a short recap of what you heard, what was agreed and the next step, while it is fresh.
- company
- Your company name.
- recipients
- Who it goes to, with their roles.
- sender_name
- Your name as you sign emails.
- call_notes
- Your notes or the transcript: their situation, priorities, questions, objections, what was agreed. Mark anything internal.
repurpose-article-social-posts — Turn one article into posts for several channels
You published a blog post, guide or report and want a handful of social posts that each carry one real point from it.
- article
- The full text of the article, guide or report.
- channels
- The channels and their limits, for example "LinkedIn; Instagram caption, 300 characters; X, 280 characters".
- brand_voice
- A few words on how you sound.
- past_post
- Optional. One post of yours that did well, so the new ones match its voice. Leave it empty if you have none.
- posts_per_channel
- How many posts per channel, for example 2.
- audience
- Who the posts are for.
- article_link
- The URL the posts point to.
inbox-backlog-triage — Sort a batch of emails by what needs you
You are back from time off or behind on email and want the pile sorted into what needs a reply today, what can wait, and what is only for your information.
- my_role
- Your role, for example "an office manager at a dental practice".
- priority_people
- People whose requests always come first, for example your manager or a key client.
- my_responsibilities
- What you own, in a line or two, so the sorting knows what is yours.
- delegation_notes
- Who handles what, for example "invoices go to accounts". "None" is fine.
- emails
- The emails, each with sender, date, subject and body, oldest first. Remove anything you may not share with an AI tool.
meeting-agenda-from-goals — Build a meeting agenda from what the meeting must decide
You are running a meeting and want an agenda with time boxes, owners and the outcome each item needs, so the meeting ends with decisions.
- meeting_name
- What the meeting is, for example "Q3 planning with the regional leads".
- meeting_length
- For example 45 minutes.
- attendees
- Names or roles, one per line.
- meeting_goals
- What must be decided or produced by the end.
- requested_topics
- Topics people have asked to add, or "none".
- materials
- Documents attendees should read first, or "none".
meeting-notes-to-action-items — Turn meeting notes into decisions and action items
You have messy notes or an auto-generated transcript and need a short summary of what was decided and who is doing what, to send to the group.
- meeting_name
- The meeting's name or topic.
- meeting_date
- The date it took place.
- attendees
- Who was there, by name or role.
- also_send_to
- Anyone else who should get the summary, or "nobody else".
- notes
- Your notes or the transcript, however messy.
polite-decline-email — Say no to a request politely and keep the relationship
Someone asked for your time, a favor, a meeting or extra work, and you need to decline clearly without sounding cold or leaving the door half open.
- requester
- Who asked, by name or role.
- request
- Their message, or a description of what they asked for.
- relationship
- For example "my manager's peer", "a long-time client" or "a former colleague".
- reason
- Your real reason, marking which part you are happy to share.
- alternative
- A smaller thing you can offer, a referral, or "nothing".
- channel
- Email, chat or text.
weekly-status-update-from-notes — Write a weekly status update from rough notes
You owe your manager or stakeholders a weekly update and have a jumble of notes, and you want something they can read in a minute.
- weekly_notes
- Your notes for the week: what you did, what moved, what is stuck. Fragments are fine.
- last_update
- Last week's update, to compare against. Leave it empty if this is the first.
- word_limit
- For example 150.
- audience
- Who reads it, for example "my manager" or "the project steering group".
- project_or_role
- The project, team or role the update covers.
difficult-work-email — Write a difficult work email: bad news or pushback
You have to tell someone something they will not like (a delay, a no, a mistake, a disagreement) and want it clear, calm and fair.
- situation
- What happened and why this email is hard to write.
- facts
- The facts that matter: dates, numbers, what was agreed before.
- recipient
- Their name or role, and your working relationship.
- recipient_priorities
- What they care about most, for example "hitting the launch date" or "not surprising their own boss".
- goal
- What you need, for example "agree a new deadline" or "decline the change without losing the client".
- offer
- What you can offer or commit to, or "nothing beyond the facts".
- off_limits
- Anything you must not admit, promise or mention, such as a confidential reason. "Nothing" is fine.
email-thread-catch-up — Catch up on a long email thread you were copied into
You have been added to a long thread or are taking it over, and need to know what was decided, what is still open, and what anyone expects from you.
- my_name_and_role
- Your name as it appears in the thread, and your role, so requests to you can be spotted.
- how_i_joined
- For example "copied in yesterday" or "taking over from a colleague who left".
- thread
- The whole thread, oldest message first, with senders and dates.
negative-review-reply — Reply to a negative online review
A customer left a bad review on Google, Yelp or a marketplace, and you want a public reply that is calm and specific, plus an optional private message.
- platform
- Where the review is, for example Google, Yelp or Etsy.
- rating
- The star rating, for example 2 of 5.
- review_text
- The review, exactly as posted.
- owner_account
- What happened from your side, and anything you are willing to do to put it right. Say if you cannot find a record of the customer.
- business_name
- Your business name.
- contact_method
- How unhappy customers can reach you, for example an email address or phone number.
- signer
- Who signs the reply, for example "Maria, owner".
product-listing-from-specs — Write a product listing from your own specs
You sell on Etsy, Shopify, Amazon or your own site and need a title, bullets and description built from the facts you have, not invented features.
- marketplace
- Where you sell, for example Etsy or your own Shopify store.
- target_buyer
- Who buys it, for example "people furnishing a first apartment".
- title_limit
- The platform's title limit, for example 140. Check its current rules.
- tag_count
- How many tags the platform allows, for example 13.
- product_specs
- Everything true about the product: what it is, materials, size, colors, what is included, care, shipping, who makes it.
- keywords
- Search terms buyers use, comma separated.
- shop_voice
- A few words on how your shop sounds, or a past listing you like.
supplier-price-increase-pushback — Push back on a supplier's price increase
A supplier announced higher prices and you want to question or negotiate the increase in writing without souring a relationship you depend on.
- supplier
- The supplier's name, and your contact there if you have one.
- my_business
- What your business is, in a few words.
- my_goal
- What you want, for example "to delay the increase by three months" or "to understand it before I accept it".
- price_notice
- The supplier's announcement, exactly as received.
- relationship_facts
- True facts you can mention: how long you have bought from them, typical order size, how reliably you pay.
- my_offer
- For example a larger order, a longer commitment, faster payment, or "nothing".
- alternatives
- Other suppliers or options you have. Mark any you are willing to mention.
customer-price-increase-notice — Tell your customers about a price increase
You are raising prices and want a short, honest notice with the date and the reason, without apologizing too much or burying the change.
- business_name
- Your business name.
- price_change
- Which products or services change, with the old and new prices if you will share them.
- effective_date
- When the new prices start.
- reason
- The real reason, in a sentence or two.
- what_softens_it
- For example "current prices held for bookings already made", or "nothing".
- customers
- Who receives it, for example "regular clients of a hair salon".
- contact
- How customers can ask questions.
- signer
- Who signs it, for example the owner's first name.
quote-estimate-email — Send a quote or estimate that sets clear expectations
A customer asked what a job will cost, and you want an email that presents your price with what is included, what is not, and what happens next.
- customer_request
- What the customer asked for, in their words if you have them.
- price
- The price exactly as you want it shown, for example a fixed price, or a range with what moves it.
- included
- The work and materials the price covers.
- excluded
- What the price does not cover, such as materials, permits or disposal.
- timing
- When you could do the work, as specifically as you can commit to.
- validity
- How long the price holds, for example 30 days.
- payment_terms
- For example deposit and balance, and the payment methods you accept.
- how_to_accept
- What the customer does to go ahead, for example reply to the email or sign the attached form.
- business_name
- Your business name.
- signer
- Who signs the email.
- past_quote
- Optional. A quote email you sent before and were happy with, so this one matches its tone. Leave it empty if you have none.
returns-policy-from-decisions — Write a simple returns and refunds policy from your decisions
You need a clear returns policy for your shop or website and have already decided the rules, but not how to write them so customers understand.
- business_name
- Your business name.
- where_published
- For example your website, your receipts and your marketplace shop page.
- what_i_sell
- What you sell, in a line.
- customer_location
- Where your customers are, for example "US only" or "US and Canada".
- contact
- How customers reach you about returns.
- decisions
- Your rules in any form: return window, condition, who pays shipping, refund method and timing, exchanges, items you won't take back, damaged items.
property-listing-description — Write a property listing description from verified facts
You are listing a home or rental and want MLS or portal copy built only from the property's real features, written with fair housing rules in mind.
- listing_site
- Where it will be posted, for example your MLS or a rental portal.
- property_facts
- Everything verified: type, bedrooms, bathrooms, size, features, upgrades with dates, lot, parking, fees, nearby places with distances.
- highlights
- What the owner most wants buyers or renters to notice.
- length_limit
- For example "1,000 characters" or "250 words". Check your MLS or portal rules.
- agent_details
- Brokerage name, license line or contact details, or "none".
press-release-from-facts — Write a press release from confirmed facts
You have news to announce, a set of approved facts and quotes, and you need a release a reporter can use without calling you to check what is true.
- announcement
- What you are announcing, in one line, for example "a new office in Denver" or "the general release of our mobile app".
- organization
- Your company or organization name.
- target_outlets
- Who you want to cover it, for example "local business press" or "trade publications for logistics managers".
- style_guide
- The style for dates and datelines, for example AP style or your own house style.
- release_timing
- "FOR IMMEDIATE RELEASE", or the embargo date and time.
- facts
- Every confirmed fact: what, when, where, who it is for, prices, availability, figures you are allowed to publish.
- approved_quotes
- Quotes that the speaker has approved, each with their name and title. Write "none" if you have none yet.
- boilerplate
- Your standard "About" paragraph, as approved.
- media_contact
- Name, email and phone for press questions.
- past_release
- Optional. A release of yours that got good coverage, so this one matches its structure and tone. Leave it empty if you have none.
proofread-errors-only — Proofread for errors only, without rewriting
The text is final apart from typos and slips, and you want the mistakes fixed without anyone touching your wording.
- text_type
- What the text is, for example "a client proposal" or "a printed brochure".
- audience
- Who will read it.
- text
- The text to proofread.
- spelling_variety
- American or British, or the variety the text already uses.
- leave_as_is
- Names, product terms, quotations or deliberate spellings to leave alone. Write "none" if there are none.
translate-for-local-readers — Translate a document for local readers, keeping the meaning
You need a text in another language that reads as if it was written there, without losing facts, conditions or your product terms.
- source_text
- The text to translate.
- glossary
- Terms with fixed translations, one per line, such as product names or legal terms. Write "none" if you have none.
- source_language
- The language the text is written in.
- target_language
- The language to translate into.
- target_region
- Where the readers are, for example Mexico, Quebec or Brazil, since vocabulary and conventions differ by region.
- register
- How formal it should be, for example "formal, like a letter from a bank" or "friendly, like an app's help pages".
- audience
- Who will read the translation, for example "customers" or "warehouse staff".
check-claims-against-sources — Check a draft's claims against your sources
Before a report, article or proposal goes out, you want every factual claim matched to a source and anything unsupported pulled out for checking.
- sources
- Your source documents, each starting with a short label such as [S1] and its title or link.
- draft
- The draft to check.
- draft_type
- What the draft is, for example "a quarterly report" or "a grant proposal".
- audience
- Who will read it once it is out.
sql-from-question — Write a SQL query from a question and your schema
You know the business question and the tables, and you want a query that runs on your database and says what it assumed.
- dialect
- Your database, for example PostgreSQL, BigQuery, Snowflake, MySQL or SQL Server.
- question
- The business question in plain words, with the time window, for example "weekly active customers by plan for the last 12 weeks".
- audience
- Who will read the result, for example "the finance team" or "a dashboard for account managers".
- definitions
- How your team defines key terms, for example "active means at least one paid order in the period". Write "none" if there are none.
- schema
- CREATE TABLE statements, or each table with its columns, types and keys.
- sample_rows
- A few rows from each table with personal data removed, or "none".
clean-messy-columns — Plan the cleanup of messy spreadsheet columns
An export or a shared sheet has inconsistent dates, names, categories or numbers, and you want rules you can apply and check rather than a silently altered file.
- columns
- The column names to clean, each with what it should contain, for example "signup_date: the date the customer signed up".
- sample_rows
- 30 to 100 rows copied from the sheet, including the messiest ones you have noticed. Remove personal data first.
- target_format
- The format each column should end up in, for example "dates as YYYY-MM-DD, country names in English, amounts as plain numbers".
- data_source
- Where the data came from, for example "a CRM export merged from two regions".
- downstream_use
- What must work once it is clean, for example "the monthly revenue pivot groups every region correctly".
- tool
- Where you will clean it, for example Excel formulas, Power Query, Google Sheets, pandas or SQL.
ab-test-readout — Read out an A/B test result honestly
An experiment has finished and you need a write-up that says what the numbers show, how sure you can be, and what they do not show.
- audience
- Who reads the readout, for example "the product leadership meeting".
- decision
- What they will decide, for example "whether to roll out the new checkout to everyone".
- test_name
- The test's name or a one-line description of the change.
- hypothesis
- The hypothesis as it was written before the test started.
- primary_metric
- The one metric the test was designed to move, with its definition.
- guardrails
- Metrics that must not get worse, for example refund rate or page load time. Write "none" if there are none.
- test_setup
- Start and end dates, the planned split, and how users were assigned, for example "50/50 by user id".
- results
- Users and conversions or metric values per variant, plus the p-value or confidence interval if your tool gives one.
choose-chart-for-message — Choose the right chart for your data and message
You have a table of numbers and one point to make in a slide or report, and you want the chart type, its setup and a title that states the takeaway.
- data
- The table to chart, with headers and units, copied from your sheet.
- message
- The one point the chart should make, in a sentence.
- audience_and_place
- For example "the board pack, printed in black and white" or "a team slide shown on screen".
- tool
- For example Excel, Google Sheets, PowerPoint or Tableau.
user-stories-acceptance-criteria — Write user stories with testable acceptance criteria
A feature is agreed in outline and you need stories the team can estimate, build and test, with the edge cases written down before work starts.
- feature_notes
- What the feature should do: the spec, meeting notes or the agreed outline.
- user_types
- The kinds of user involved, for example "team admin, member, guest".
- known_limits
- Known limits: platforms, permissions, performance targets, deadlines. Write "none" if there are none.
- team
- The team that will build it.
spec-critique-before-review — Critique a product spec before the review meeting
You have a PRD or spec draft and want the hard questions a sharp reviewer would ask, while there is still time to fix it.
- reviewers
- Who will review it, for example "the engineering lead, the design lead and the head of product".
- spec
- The spec or PRD draft, in full.
- background
- Anything a reviewer would know: this quarter's goals, known constraints, related launches. Write "none" if not needed.
release-notes-from-changelog — Write release notes from a changelog
You have a list of merged changes or tickets and need notes customers will read, grouped by what changed for them, with internal items left out.
- changelog
- The changes in this release: merged pull request titles, ticket summaries or a raw changelog.
- product_version
- Your product name and version, for example "Mobile app 4.2".
- release_date
- The date the release goes out.
- readers
- Who reads the notes, for example "admins at customer companies" or "everyone who uses the app".
ab-test-plan — Plan an A/B test before you run it
You want to test a change and need the hypothesis, metrics and decision rule agreed in writing before anyone looks at results.
- team
- Who needs to agree, for example "the growth team and the analytics lead".
- change
- What the variant does differently, in one or two sentences.
- rationale
- Why you expect it to work: research, past tests, customer feedback.
- surface_and_audience
- The page, screen or email, and which users are included.
- baseline_and_traffic
- The main metric's current value and the weekly traffic, from your analytics.
- constraints
- Dates, other experiments, legal or privacy limits. Write "none" if there are none.
code-review-checklist — Review a code change against a checklist
You want a second pair of eyes on a diff before a human review, with findings ranked by how much they matter and nothing invented.
- language
- The language and framework, for example "Python with Django".
- change_description
- What the change is meant to do and why, from the ticket or pull request description.
- diff
- The output of git diff, or the changed files.
- conventions
- Team rules the code should follow, such as error handling or naming patterns. Write "none" if nothing is written down.
- team
- The team or repository the change belongs to.
explain-error-log — Explain an error or log and find the likely cause
Something failed with an error message, stack trace or log you do not fully understand, and you want the likely causes ranked with a way to confirm each.
- stack
- The language, framework and runtime, for example "Node.js with Express" or "Python 3.12 with pandas".
- environment
- Where it fails, for example "local development", "CI" or "production".
- experience_level
- How familiar you are with this code, for example "new to this codebase" or "comfortable with it, but new to this library".
- what_i_was_doing
- The command, request or action that triggered it.
- recent_changes
- Deploys, upgrades or config changes since it last worked. "Nothing that I know of" is fine.
- error_output
- The full error message, stack trace or log lines, pasted exactly. Remove secrets and personal data first.
- relevant_code
- The code the trace points to, if you have it, or "none".
unit-tests-for-function — Write unit tests for one function
You have a single function and want focused tests that cover the normal cases, the edges and the errors, in your project's test framework.
- function_code
- The function, plus any small helpers or types it uses.
- language
- The language and version, for example TypeScript or Python 3.12.
- test_framework
- For example Jest, Vitest, pytest, JUnit 5 or Go's testing package.
- intended_behavior
- What the function should do, including the rules for bad input. The tests check this, so be precise.
- example_test
- One existing test from your project, so the new tests match its style. Write "none" if there is none.
api-docs-from-code — Write API reference docs from the code
An internal or public API has endpoints nobody documented, and you want reference docs written from what the code actually does.
- audience
- Who reads the docs, for example "developers on other internal teams" or "engineers at customer companies".
- reader_goal
- What they need to do with the docs, for example "build an integration without asking us questions".
- stack
- For example "Python with FastAPI" or "TypeScript with Express".
- base_and_auth
- The base URL and how callers authenticate, for example "a bearer token in the Authorization header". Write "unknown" if you are not sure.
- code
- The route handlers and the types, schemas and validation they use.
- existing_notes
- Any existing docs, README sections or comments about the API. Write "none" if there are none.
coding-agent-small-feature — Brief a coding agent to build a small feature
You are handing a well-defined feature to Claude Code, Codex or another coding agent and want a plan first, code that fits the codebase, and tests as proof.
- feature
- What the feature does, in one or two sentences.
- users
- Who uses it, for example "account admins".
- user_outcome
- What it lets them do, for example "they can send a report to their finance team without reformatting it".
- location
- The files, modules or endpoints involved, as far as you know.
- pattern_files
- One or two existing files that do something similar, for the agent to copy.
- acceptance_cases
- Concrete examples, one per line: an input or action and the exact result, for example "export with no rows: shows 'Nothing to export'".
- max_files
- The number of files above which the agent must check with you first, for example 5.
- off_limits
- Files, folders or systems that must not change, for example migrations or generated code.
- check_commands
- The commands for tests, lint and types, for example npm test && npm run lint.
quiz-with-answer-key — Write quiz questions with an answer key from your material
You have a document, policy or lesson and need multiple-choice questions that test understanding, with plausible wrong answers and an explained key.
- material
- The document, policy, chapter or lesson the quiz is based on.
- objectives
- What learners should be able to do afterward, numbered, for example "2. Choose the right expense category for a purchase".
- question_count
- How many questions, for example 10.
- learners
- Who takes the quiz, for example "new support agents" or "grade 9 students".
- quiz_use
- When and why it is used, for example "at the end of the onboarding course, to see who needs a refresher".
training-session-plan — Plan a training session for adults at work
You have to run a workshop or training session and need a timed plan built around practice, not a slide-by-slide lecture.
- duration
- How long the session is, for example 90 minutes or half a day.
- topic
- What the session covers.
- participants
- Who attends and how many, for example "12 new team leads".
- outcome
- What they should be able to do at work afterward, for example "run a first one-on-one meeting with a direct report".
- delivery_format
- For example "in person, one room, a whiteboard and a projector" or "video call with breakout rooms".
- content
- What has to be taught: the policy, process or notes the session is based on.
- participants_background
- What they already know, and any concerns or resistance you expect.
new-hire-first-week-guide — Write a new hire's first-week guide
Someone starts soon and you want a day-by-day first week they can follow, built from your real tools, people and tasks.
- role
- The new hire's job title.
- team
- The team they join.
- manager
- The manager's name or role, for example "the support team lead".
- start_details
- The start date, working days and hours, and whether they are remote, hybrid or on site.
- tools_and_access
- Each tool or account they need and who sets it up.
- people_to_meet
- Who they should meet in the first week, with each person's role.
- first_task
- A small, real piece of work they can finish in the week.
- reading_list
- Documents, wiki pages or recordings, in rough priority order.
- tone
- For example warm and informal, or friendly but brief.
grading-rubric — Build a grading rubric from an assignment
You set an assignment or task and need a rubric that makes grading consistent and tells learners what good work looks like before they start.
- assignment
- The assignment brief as learners receive it.
- learners
- Who does the assignment, for example "10th grade history students" or "new analysts in their first month".
- objectives
- What the work should demonstrate, for example "build an argument from primary sources".
- scale
- For example four levels from Beginning to Exceeds, or points out of 20.
elearning-storyboard — Turn source material into an e-learning storyboard
You are building a short online course from a policy, process or expert notes, and need a screen-by-screen storyboard tied to learning objectives.
- source_content
- The policy, process document or expert notes the module teaches.
- objectives
- Three to five things the learner should be able to do afterward, numbered.
- learners
- Who takes the course and what they already know.
- authoring_tool
- For example Articulate Rise, Storyline, or "not decided".
- length_minutes
- The target length in minutes, for example 15.
internal-policy-assistant — System prompt for an internal policy Q&A assistant
You want employees to ask an assistant about HR and workplace policies, such as leave, benefits or remote work, and get answers quoted from the policy, with personal and sensitive cases sent to a person.
- organization
- Your organization's name.
- policy_areas
- The policies it covers, for example "leave, benefits, remote work and acceptable use of IT".
- policy_documents
- The current policy text, each document with its name, section numbers and last-revised date.
- contact
- Where people go for personal cases, for example "the HR team through the people help desk".
- input
- The employee's question. Your app inserts it at run time; the Chatbot Safety Test puts its attack probes here.
meeting-notes-assistant-system-prompt — System prompt for a meeting-notes assistant
Your app turns meeting transcripts into notes, and they must record decisions and action items accurately, never inventing an owner or a deadline.
- team_description
- Who uses the notes, for example "a product team's weekly planning meetings".
- house_rules
- One extra rule for your team, for example "Write dates as YYYY-MM-DD." Write "No extra rules." if you have none.
- input
- The meeting transcript, with speaker labels if you have them. Your app inserts it at run time; the Chatbot Safety Test puts its probes here.
document-extraction-to-json — System prompt to extract fields from documents into JSON
Your app needs the same fields pulled from invoices, forms, contracts or emails into JSON, with nothing made up when a field is missing.
- document_type
- What the documents are, for example "supplier invoices" or "job application forms".
- downstream_system
- What uses the data, for example "our accounts payable import".
- field_definitions
- Each field on its own line: name, type, meaning and any format rule, for example "due_date: date, the payment due date, as YYYY-MM-DD".
- input
- The document text, inserted by your app at run time; the Chatbot Safety Test puts its probes here.
product-photo-background-edit — Edit a product photo: new background, product unchanged
You have a real photo of a product and need it on a clean or styled background for a listing or a slide, without the product itself being altered.
- product
- What the product is, for example "a glass bottle of olive oil with a paper label".
- use
- Where the image will be used, for example "the main image of a marketplace listing" or "a sales slide".
- new_background
- The new background, described concretely, for example "a plain warm-white studio backdrop" or "a pale marble counter by a window".
- light_direction
- Where the light on the product comes from in your photo, for example "the upper left".
- aspect_ratio
- The shape you need, for example 1:1 for a listing or 16:9 for a slide. Set the same ratio in the tool's size setting if it has one.
training-video-task-shot — Training video shot of a workplace task
You need a short clip showing one step of a real task, such as lifting a box safely or scanning an item at a checkout counter, for a training module, from a text-to-video model.
- person_description
- A specific but fictional person, for example "a warehouse worker in a high-visibility vest and work gloves". Do not describe a real, recognizable person.
- setting
- Where it happens, for example "a warehouse aisle with metal shelving".
- action
- The step to show, precisely, for example "bending at the knees to lift a cardboard box, keeping it close to the body".
- training_topic
- What the module teaches, for example "manual handling".
- key_object
- The object being handled, for example "the box".
- final_detail
- Where the camera ends, for example "the gloved hands gripping the box".
- duration_seconds
- A clip length your video model supports; check its settings.
- action_sound
- The sound of the action, for example "the scrape of the box sliding off the shelf".
professional-email-from-bullets — Write a professional email from rough bullet points
You need to send a clear, polite email and only have a few points jotted down.
- recipient
- Who it goes to and your relationship, for example "a client I have worked with for two years" or "my manager".
- goal
- What the reader should know or do after reading, for example "agree to move the review to next week".
- points
- Your notes, however rough: facts, dates, requests, anything you want to say.
- sign_off
- How to sign it, for example your first name or "Thanks," and your name.
change-email-tone — Change the tone of an email before you send it
You need a blunt, frustrated or rambling email made calmer, warmer or firmer without changing what it says.
- tone_wanted
- How you want it to read, for example "calmer and less frustrated", "firmer" or "warmer but still clear".
- recipient
- Who reads it and your relationship, for example "a supplier who missed a delivery".
- draft
- Your email as you wrote it.
- must_keep
- Points that must not be softened or lost, for example "the June 30 deadline and that we will not pay the second invoice". "None" is fine.
reply-to-multi-question-email — Reply to an email that asks several things
You need a reply that answers every question and request in a long email, in order, without missing one.
- sender
- Who sent it and your relationship, for example "a new client" or "the finance team".
- incoming_email
- The email you are replying to, in full.
- my_answers
- What you know for each question, including "no" or "don't know yet". Fragments are fine.
presentation-outline-from-goal — Outline a presentation from your goal and audience
You need a slide-by-slide outline with one message per slide before you open PowerPoint or Slides.
- topic
- What the presentation is about.
- audience
- Who will be there, what they already know and what they care about.
- goal
- What should change after the talk, for example "approve the pilot budget".
- time_available
- For example "20 minutes including questions".
- setting
- For example "in person with a projector", "video call" or "sent as a read-ahead".
- material
- The facts, figures and notes the talk should draw on.
document-to-slides — Turn a report or document into slides
You need a long document condensed into slide headlines, a few bullets each, and speaker notes.
- audience
- Who will see the slides, for example "the leadership team" or "new starters in the department".
- deck_size
- How many slides or how long the talk is, for example "10 slides" or "a 15-minute slot".
- purpose
- What the deck is for, for example "to get approval for phase two" or "to brief the new team".
- document
- The report or document, in full.
meeting-follow-up-email — Send a follow-up email after an internal meeting
You need to tell attendees what was agreed, who owns what, and by when, while the meeting is fresh.
- meeting_name
- The meeting's name or topic.
- meeting_date
- When it took place.
- attendees
- Who was there, by name or role.
- also_send_to
- Anyone else who gets the email, or "nobody else".
- next_check_in
- The date of the next meeting or check-in, or "none set".
- notes
- Your notes from the meeting, however rough.
- correction_deadline
- When people should flag corrections, for example "end of day Thursday".
formal-minutes-from-transcript — Write formal meeting minutes from a transcript
You need minutes for a board, committee or governance meeting with attendees, motions, decisions and votes.
- body_name
- The board or committee, for example "Board of Trustees" or "Audit Committee".
- meeting_details
- Regular or special meeting, date, start and end time, and place or platform.
- attendance
- Who was present, who sent apologies, and guests or staff in attendance.
- agenda
- The agenda as circulated.
- transcript
- The transcript or recording notes, with speaker names if you have them.
- past_minutes
- A previous set of approved minutes or your style rules, so the draft matches. "None" is fine.
speaker-notes-for-slides — Write speaker notes for a deck you already have
You need what to say on each slide in your own words so the talk fits your time slot.
- talk_length
- For example "15 minutes, then 5 minutes of questions".
- audience
- Who will be listening and what they already know.
- speaking_style
- For example "informal, I like to ask the room questions" or "formal, I stick close to a script".
- slides
- The text of each slide in order, with any points you want to make. Mark where each slide starts.
slide-titles-that-state-the-point — Rewrite slide titles so each one states the point
You need topic labels like "Q3 update" turned into headlines that tell the audience the takeaway.
- audience
- Who will see the deck, for example "the regional managers".
- deck_message
- The one thing the deck should leave people believing or deciding.
- slides
- Each slide's current title followed by its text or a short description of its chart. Mark where each slide starts.
email-for-senior-executive — Rewrite a message for a senior executive
You need a message cut down so a busy leader sees the ask, the reason and the deadline in the first lines.
- executive
- Their role and what they care about most, for example "our COO, focused on cost and delivery dates".
- ask
- The decision, approval or input you need, and the date you need it by.
- what_they_know
- For example "nothing yet" or "they approved phase 1 last month".
- draft
- Your message as it stands.
meeting-prep-briefing — Prepare a one-page brief before an important meeting
You need a quick brief on who you are meeting, the history, open issues and what you want from the meeting.
- meeting
- What, when, how long and where, for example "45-minute renewal call with a key client on Tuesday".
- attendees
- Names and roles on both sides, one per line.
- my_goal
- What a good outcome looks like for you, for example "agree the renewal at current terms".
- background
- Emails, notes, documents and anything else relevant, oldest first if you can.
follow-up-nudge-email — Nudge someone who has not replied
You need a polite chaser that gets an answer without sounding passive-aggressive.
- recipient
- Who they are and your relationship, for example "a supplier's account manager".
- waiting
- For example "one week, no follow-up yet" or "three weeks, followed up once".
- what_i_need
- The exact answer or action you need, and any default you will go ahead with if they stay silent.
- why_it_matters
- The real reason for the timing, for example "the order must be placed by the 20th".
- original_message
- The message they have not answered.
escalate-a-problem-upward — Escalate a problem to your manager or leadership
You need to raise a blocked or risky issue with facts, impact, options and a clear ask.
- recipient
- Who you are escalating to, for example "my manager" or "the program director".
- problem
- What is happening, since when and what it blocks, with the facts you have.
- impact
- What happens if nothing changes, with dates or amounts if you know them.
- already_tried
- What you have done so far and what happened, or "nothing yet".
- options
- Possible ways forward you can see, or "none yet".
- ask
- The decision, resource or help you need, and by when.
weekly-plan-from-task-list — Plan your week from a messy task list
You need a long, mixed task list turned into a realistic weekly plan with priorities and what can wait.
- week_of
- The week you are planning, for example "the week of March 9".
- task_list
- Everything on your plate, with deadlines where you know them. Messy is fine.
- commitments
- Meetings and fixed appointments for the week, with days and times.
- working_hours
- For example "9 to 5:30, best focus before lunch, no work Friday afternoon".
- priorities
- The one to three things that matter most this week, for example "ship the client proposal".
ask-for-deadline-extension — Ask for more time on a deadline
You need to request an extension honestly, with a new date and what you will deliver in the meantime.
- recipient
- Who you are asking and your relationship, for example "a client" or "my manager".
- deliverable
- What is due and the current deadline.
- new_date
- The date you are asking for. Pick one you are confident you can meet.
- reason
- The real reason, marking which parts you are happy to share.
- interim
- For example "a first draft of sections 1 to 3", or "nothing".
- downstream
- Who depends on it, for example "the design team starts on the 15th", or "not sure".
handover-note-before-leave — Write a handover note and out-of-office reply before leave
You need colleagues covering for you to know what is in flight, who to contact and what can wait.
- leave_dates
- Your first day away and the day you are back.
- contact_rule
- For example "do not contact" or "text me only if a client deadline is at risk".
- cover
- Who covers which area, one per line, and any limits on what they can decide.
- work_in_flight
- Each project or task: where it stands, what is next, deadlines, contacts and where the files live.
- recurring_tasks
- For example "monthly report due on the 3rd", or "none".
procedure-to-checklist — Turn a long procedure or policy into a checklist
You need a dense document turned into a step-by-step checklist people will actually follow.
- who_uses_it
- Who will use it, for example "a new warehouse supervisor" or "anyone approving a new supplier".
- when_used
- When it is used, for example "at the start of every shift" or "each time a supplier is onboarded".
- where_used
- For example "printed on one page" or "as a form on a tablet".
- document
- The procedure or policy, in full, with its section numbers.
travel-itinerary-from-confirmations — Build a travel itinerary from booking confirmations
You need flights, hotels and meetings from several emails combined into one clear itinerary.
- traveler
- Who is traveling, for example "me" or "our CEO, who prefers 24-hour times".
- home_time_zone
- The traveler's home time zone, for example "US Eastern".
- confirmations
- Every booking email or confirmation for the trip, pasted in full.
- meetings
- Meetings and events during the trip, with times and addresses, or "none".
introduce-two-contacts — Introduce two people by email
You need an introduction that tells each person why the other is worth meeting and what to do next.
- person_a
- Name, role and what they do or need, marking anything that must not be shared.
- person_b
- Name, role and what they do or need, marking anything that must not be shared.
- reason
- Why they should meet, as specifically as you can put it.
- opt_in
- For example "both agreed", "only A has agreed" or "neither asked yet".
- next_step
- For example "a 20-minute call" or "B to send A their proposal".
thank-a-colleague-specifically — Thank a colleague for specific work
You need a thank-you that names exactly what someone did and the difference it made.
- colleague
- Their name or role, and how you work together.
- what_they_did
- The specific actions, with dates or details if you have them.
- impact
- What it made possible or prevented, for example "we hit the client deadline". "Not sure" is fine.
- channel
- For example email, a chat message or a handwritten card.
- wider_audience
- Who else should see it, for example "their manager" or "the team channel".
internal-newsletter-from-updates — Compile an internal newsletter from team updates
You need several teams' updates turned into a short internal newsletter people will read.
- newsletter_name
- Its name, or "the team update" if it has none.
- audience
- Who reads it, for example "everyone in the operations division".
- updates
- Each team's update as they sent it, with the team name at the top of each.
- upcoming_dates
- Events and deadlines to list, or "none".
- past_issue
- A previous issue to match for tone. Leave it empty if this is the first.
work-event-planning-checklist — Plan a work event, offsite or team celebration
You need a timeline, task checklist and budget lines for an event so nothing is forgotten.
- event
- What it is, for example "a one-day team offsite" or "an end-of-year celebration".
- purpose
- What it should achieve, for example "plan next year and help the new team get to know each other".
- date_and_place
- The date and venue, or "not booked yet".
- attendees
- How many, who, and any needs you already know about.
- budget
- The total and what it must pay for, or "not set".
- already_arranged
- What is booked or decided, or "nothing yet".
- rules
- For example "no alcohol on expenses" or "events above a set cost need director approval". "None known" is fine.
custom-assistant-instructions — Write instructions for a Custom GPT, Claude Project or Gem
You need a reusable assistant for a repeated task and want clear instructions and a list of files to attach.
- platform
- Where you are building it, for example "a Custom GPT in ChatGPT", "a Claude Project" or "a Gemini Gem".
- task
- The job the assistant does, for example "turn rough notes into client proposals in our format".
- users
- For example "just me" or "our five-person support team".
- inputs
- What each conversation starts with, for example "a customer email" or "rough meeting notes".
- rules
- What it must always do and never do, for example "never quote prices that are not in the price list".
- available_files
- The documents you have, one per line, with a few words on each.
- good_example
- An output you were happy with, to show the standard. Remove anything confidential first.
improve-a-prompt — Improve a prompt that gives inconsistent results
You need a prompt you use often rewritten so it gives reliable, well-formatted answers.
- prompt_to_improve
- The prompt exactly as you use it now.
- purpose
- The job it does and who uses the result, for example "weekly summaries of customer feedback for the product team".
- problems
- For example "the format changes every time" or "it makes up numbers".
- model
- For example ChatGPT, Claude, Gemini or Copilot, or "not sure".
- good_output
- One answer you were happy with, to show the standard. Leave it empty if you have none.
ai-feature-test-set — Build a test set and rubric to evaluate an AI feature
You need example inputs, expected behavior and a scoring rubric before you change prompts or models.
- feature_description
- What the feature does, who uses it and where, for example "drafts replies to customer emails for our support agents".
- case_count
- How many cases you want, for example 40.
- current_prompt
- The system prompt or prompt the feature uses today.
- rules
- The policies the feature must follow, for example refund limits or topics it must not discuss.
- real_inputs
- Ten to thirty real user inputs, with names and personal details removed.
- known_problems
- Failures you have seen or users have reported, or "none yet".
reply-drafting-assistant-system-prompt — System prompt for an assistant that drafts email replies
You need an assistant that drafts replies in your voice and flags anything it should not answer.
- my_name
- Your name, as the assistant should refer to you.
- my_role
- Your role, for example "office manager at an architecture practice".
- work_context
- Who usually emails you and about what, in a line or two.
- facts
- Information replies may use: availability, prices, policies, links and your standard answers to common requests.
- voice_samples
- Two or three emails you wrote and liked, with anything confidential removed.
- flag_topics
- Topics you always handle yourself, for example "pricing negotiations, staff matters and press inquiries".
- sign_off
- How you sign your emails, for example "Thanks," followed by your first name.
- input
- The incoming email or thread. Your app inserts it at run time; the Chatbot Safety Test puts its probes here.
week-of-social-posts — Plan a week of social media posts
You need a week of posts for your channels built from your news, offers and themes.
- business
- What you sell and to whom, in a sentence, for example "a family bakery selling bread and custom cakes".
- audience
- Who follows you and what they care about.
- week_goal
- What the week should achieve, for example "fill the Saturday workshop" or "remind people we now deliver".
- week_dates
- The dates the posts cover, for example "Monday, November 2 to Sunday, November 8".
- channels
- Each channel and how many posts on it, with any length limit, for example "Instagram 4, LinkedIn 2, Facebook 3".
- themes
- Your recurring themes, for example "tips, behind the scenes, customer questions", or "none".
- material
- This week's news, offers, events, dates, prices, links and the photos you have.
- voice_sample
- Two or three of your past posts that sound right. Leave it empty for a plain default.
marketing-email-campaign — Write a marketing email with subject lines to test
You need a promotional or announcement email with several subject lines, preview text and one clear call to action.
- sender
- The sender name your subscribers recognize, for example your business name or "[your first name] at [business]".
- audience
- Who is on this list or segment, for example "customers who bought in the last year".
- email_goal
- The one action you want, for example "book a spring service" or "read the new guide".
- offer_facts
- Everything true about what you are announcing: what it is, price, dates, terms, exclusions and the link.
- voice_sample
- A past email that sounded right. Leave it empty for a plain default.
blog-post-from-outline — Write a blog post from your outline and expertise
You need a well-structured article that uses your own points and examples rather than generic filler.
- topic
- The working title or topic of the post.
- audience
- Who reads it and how much they know, for example "small landlords who manage their own properties".
- reader_outcome
- What the reader should be able to do or decide after reading.
- word_count
- The target length, for example 1,200.
- outline
- Your outline: headings and the points under each, in order.
- expertise_notes
- Your own examples, stories, numbers, steps, opinions and mistakes you have seen. The more specific, the better.
- voice_sample
- A few paragraphs you wrote before. Leave it empty for a plain default.
short-video-script — Write a script for a short video
You need a 30 to 60 second Reels, TikTok or Shorts script with a hook, beats and on-screen text.
- topic
- The one point the video makes, for example "how to tell if your tires need replacing".
- audience
- Who the video is for.
- platform
- Where it will be posted, for example Instagram Reels, TikTok or YouTube Shorts.
- length_seconds
- The target length, for example 30 or 45.
- filming_setup
- Who appears and what you can film, for example "me talking to my phone in the shop, plus close-ups of the products".
- call_to_action
- The one action, for example "book through the link in our bio".
- material
- The facts, steps, product details or offer the video should use.
monthly-content-calendar — Build a monthly content calendar
You need a month of content mapped to your goals, channels and key dates.
- business
- What you sell and to whom, in a sentence.
- audience
- Who the content is for.
- month
- The month and year, for example "March 2027".
- goals
- One to three goals for the month, for example "fill spring bookings, grow the email list".
- capacity
- Each channel and how many pieces a week you can really make, for example "blog 1, Instagram 3, email 1".
- themes
- Your content themes, for example "how-tos, behind the scenes, customer stories".
- key_dates
- Launches, events, promotions, deadlines and the holidays that matter to your business, with dates.
- existing_assets
- Content you already have and could reuse, with titles or links. Write "none" if there is none.
one-page-marketing-plan — Write a one-page marketing plan
You need a simple plan covering audience, message, channels, budget and how you will measure results.
- business
- What you sell, to whom and where, for example "a two-person bookkeeping practice serving local restaurants".
- goal
- One business goal with a number and a date, for example "10 new monthly clients by June 30".
- audience
- Who buys from you and why they choose you, as you understand it.
- budget
- Money and time available, and for how long, for example "$1,500 a month and 5 hours a week, for 3 months".
- current_marketing
- What you do now (website, listings, social, referrals, ads) and roughly what each brings in.
- customer_evidence
- Reviews, survey answers, reasons customers gave for choosing you, and questions they ask.
- plan_readers
- Who else will see the plan, for example "my business partner" or "our part-time marketer".
campaign-brief-for-agency — Write a campaign brief for an agency or designer
You need to brief a designer, agency or freelancer so the work comes back right the first time.
- deliverables
- What you need made, with sizes, formats, quantities and where each runs, for example "3 Instagram posts at 1080 by 1350, one 6-second video".
- audience
- Who the campaign is for.
- objective
- What it must achieve and how you will measure it, for example "200 sign-ups for the spring class, tracked by the booking form".
- budget_and_timeline
- The budget, the deadline for final files, and how many review rounds are included.
- approvers
- Who gives feedback and who has the final say.
- background
- About your business, the product and why this campaign is happening now.
- mandatories
- What must appear or cannot change: logo, brand guidelines, legal lines, contact details.
- references
- Work you like or dislike (links or descriptions), and what exactly about each.
- agency
- Who the brief is for, for example "our freelance designer" or the agency's name.
personas-from-customer-data — Build customer personas from real customer data
You need personas grounded in your reviews, survey answers or sales notes rather than invented ones.
- customer_data
- Reviews, survey answers, support tickets or sales notes, each with a short label such as "Review 12" or "Survey 7". Remove names and contact details first.
- data_description
- Where the data came from, how many items, the dates and how it was collected, for example "62 product reviews from our store, January to June".
- business
- What you sell and to whom, in a sentence or two.
- team
- Who will use the personas, for example "our marketing and sales team".
- decision
- What they will use them for, for example "plan the spring campaign" or "rewrite the website".
positioning-and-key-messages — Write positioning and key messages for a product
You need to state who it is for, what it does, why it is different and the proof behind each claim.
- product_facts
- What the product does, how, for whom, prices, limits, and any results you can prove.
- customer_evidence
- Customer quotes, reviews, interview notes, win and loss reasons, each with a short source label.
- alternatives
- What customers use instead (competitors, spreadsheets, an agency, doing nothing) and what you know about each from their own pages or from customers.
- product
- The product or service name.
- team
- Who will use the positioning, for example "our sales and marketing team".
- use
- What it is for, for example "rewriting the homepage" or "a new sales deck".
seo-article-brief — Plan an article around a search query
You need a brief covering search intent, outline, questions to answer and internal links before anyone writes.
- query
- The main search query, exactly as people type it.
- site
- Your site and what you offer, in a sentence.
- audience
- Who searches for this and what they need, for example "first-time buyers comparing mortgage types".
- conversion_goal
- What readers should do next, for example "download the checklist" or "book a consultation".
- length_limits
- Your title and description limits, for example "title 60 characters, description 120 to 155". Check your SEO tool's current guidance.
- search_results
- The top results for the query from your own search: each page's title, headings and a short summary, plus the questions shown in search.
- expertise
- What you know first-hand: your data, cases, examples and opinions that the top pages do not have.
- existing_pages
- Your pages that could be linked, with title and URL, one per line.
product-launch-announcement — Announce a product or feature launch
You need consistent launch copy for the blog, email and social posts from one set of facts.
- product
- The product or feature name, exactly as customers will see it.
- audience
- Who it is for, for example "existing customers on paid plans" or "independent pharmacies".
- launch_date
- The date it becomes available.
- channels
- The social channels to write for, for example "LinkedIn and Instagram".
- launch_facts
- Everything true about the launch: what it does, the problem, how it works, who gets it and when, prices, what it does not do yet, the link.
- quote
- A real quote from a named person at your company, with their title, or "none".
event-promotion-pack — Promote a webinar or event across channels
You need the invitation email, reminders, social posts and follow-up for an event.
- organizer
- Your business or team name as attendees know it.
- audience
- Who the event is for, for example "office managers at small law firms".
- channels
- The social channels to write for, for example "LinkedIn and Facebook".
- event_details
- Name, date, time and time zone, link or address, price, speakers with their real titles and short bios, agenda, registration link, capacity.
- after_event
- What people get afterward, such as a recording, slides or an offer, or "nothing".
campaign-results-readout — Report campaign results to your manager
You need a short readout of what a campaign achieved, why, and what you will change next time.
- campaign
- The campaign's name, goal, dates, channels and budget.
- targets
- What you said success would be before launch, for example "150 leads at under $40 each".
- manager
- Who reads it and what they care about most, for example "my manager, who watches cost per lead".
- next_decision
- What this should inform, for example "whether to rerun it in spring with the same budget".
- results
- The numbers by channel, with the source of each (ad platform, email tool, CRM, sales records).
- context
- What happened during the campaign: changes, problems, outside events. Write "nothing notable" if so.
brand-voice-guide — Write a brand voice guide from your best copy
You need tone rules, examples and words to avoid so every writer and AI tool sounds like your brand.
- best_copy
- Three to ten pieces of your copy that sound most like you (emails, web pages, posts), each starting with a label such as S1.
- off_brand_copy
- Copy that felt wrong for your brand, with a note on why, or "none".
- brand_context
- Who you are, who you write for, and the situations you write in, such as launches, support replies or reminders.
- writers
- Who will use the guide, for example "our two marketers and freelance writers".
youtube-script-title-description — Script a YouTube video and write its title and description
You need an outline script, title options and a description with chapters for a longer video.
- channel
- Your channel name and what it covers.
- topic
- What this video is about, as specifically as you can.
- audience
- Who it is for and what they already know, for example "beginners who have just bought a sewing machine".
- length_minutes
- The target length in minutes, for example 8.
- video_format
- How it is filmed, for example "me talking to camera with screen recordings".
- call_to_action
- The one action at the end, for example "download the free template".
- material
- Your points, steps, examples and demos, in the order you think they go.
- links
- Links for the description, each with a label, for example "Free template: [URL]".
donor-appeal — Write a fundraising appeal to donors
You need a nonprofit appeal letter or email that tells one true story and makes a clear ask.
- organization
- Your organization's name.
- mission
- What you do and for whom, in a sentence.
- audience
- Who receives it, for example "donors who gave last year but not this year".
- format
- Email or printed letter.
- signer
- Who signs it, with their title.
- ask
- The amount or amounts to ask for, and what each really pays for if you know, for example "$50 pays for [what], based on our program costs".
- why_now
- A real reason to give now, such as a matching gift with its end date, or "none".
- story
- One true story with the details, and what the person agreed you may share, including whether to change their name.
journalist-pitch-email — Pitch a story to a journalist
You need a short, specific pitch that gives a reporter a reason to cover your news.
- journalist
- Their name, outlet and beat, for example "[name], [outlet], covers local retail".
- spokesperson
- Who can talk to them, their title, and when they are free.
- assets
- What you can provide, such as data, photos or a customer who has agreed to be interviewed.
- embargo
- Whether the news is exclusive or embargoed, with the date and time, or "neither".
- recent_articles
- Two or three of their recent articles related to your news: title, date and what each covered.
- news
- Your news: what is happening, when, the facts or data behind it, and why it matters now.
flyer-and-brochure-copy — Write copy for a flyer, poster or brochure
You need short, scannable printed copy with a headline, key details and a call to action.
- piece
- What it is, its size and where it will be seen, for example "letter-size flyer for library and cafe noticeboards" or "trifold brochure for the front desk".
- audience
- Who it is for.
- call_to_action
- What the reader should do, for example "call to book a free estimate".
- facts
- Everything the piece needs: what, when, where, price, contact details, offer terms.
- must_include
- What must appear: logo, legal lines, accessibility information, sponsor credits. Write "none" if nothing.
testimonial-request-and-edit — Ask a customer for a testimonial and tidy it up
You need a request that makes saying yes easy, and a light edit the customer can approve.
- customer
- Their name, role and company, and what they bought or how you worked together.
- where_used
- Where it will appear, for example "our website's services page" or "proposals to similar clients".
- sender
- Who the request comes from, with their role.
- context
- What you did for them and anything they have said about the results, in their words where possible.
- raw_testimonial
- Their testimonial exactly as they sent it, or "none yet".
names-and-taglines — Brainstorm names and taglines against your criteria
You need options for a product, event or campaign name, checked against your rules and audience.
- thing
- What you are naming, what it does and who it is for.
- audience
- Who will see and say the name.
- names_to_avoid
- Your other brand names and competitors' names to stay clear of.
- markets
- The languages and countries where it will be used, for example "English and Spanish, US only".
- criteria
- Your rules: length, tone, describe or hint, words to avoid, anything that must be in it.
- count
- How many name options you want, for example 20.
professional-headshot-from-photo — Turn your own photo into a professional headshot
You need a clean headshot for LinkedIn or a staff page from a casual photo of yourself.
- features_to_keep
- Anything about you that must not change, for example "my glasses, my headscarf and my curly hair", or "nothing else".
- clothing
- What you should wear, described concretely, for example "a navy blazer over a plain white shirt", or "the clothes I am wearing in the photo".
- background
- A concrete background, for example "a plain light gray studio backdrop" or "a softly blurred bright office with white walls".
- aspect_ratio
- The shape you need, for example 1:1 for most profile photos or 4:5 for a staff page. If your tool has a size setting, set the same ratio there.
- purpose
- Where you will use it, for example "my LinkedIn profile" or "our company's team page".
social-graphic-with-text — Create a social media graphic with readable text
You need a post image with a short headline and your colors, sized for a specific platform.
- platform
- Where it will be posted, for example "Instagram feed" or "LinkedIn".
- topic
- What the post is about.
- audience
- Who the post is for.
- visual
- The main picture, concretely, for example "a flat illustration of three seed packets fanned out on a wooden table".
- style
- The look, for example "flat vector illustration with no outlines" or "bright, clean product photograph".
- brand_colors
- Your colors by name and hex code, for example "forest green #1F5130, cream #F4EFE6, coral #E4664A".
- headline
- The exact headline, ideally under 8 words. Shorter text renders more reliably.
- supporting_text
- One short supporting line, exactly as it should appear, or "none".
- aspect_ratio
- The shape for the platform, for example 4:5 for an Instagram feed post or 1:1 for a square post. Check the platform's current size guide.
event-flyer-image — Design an event flyer or poster
You need a printable flyer with the event name, date, place and a clear visual.
- event_name
- The event name, exactly as it should appear.
- event_type
- What kind of event it is, for example "free outdoor concert" or "half-day workshop".
- audience
- Who it is for, for example "families in the neighborhood".
- visual
- The main image, concretely, with its style, for example "a bright flat illustration of a row of market stalls with striped awnings".
- colors
- Two to four colors, for example "deep blue, warm yellow and white", or your brand colors with hex codes.
- date_time
- The date and time exactly as they should appear, for example "Saturday, May 8, 10 am to 2 pm".
- place
- The venue and address as they should appear.
- extra_line
- One more short line, such as the price, "Free entry" or a web address, or "none".
- paper_size
- The paper you will print on, for example "US Letter portrait, 8.5 by 11 inches" or "A4 portrait".
feature-prioritization — Prioritize a feature backlog with a scoring method
You need a ranked backlog with the reasoning visible to stakeholders.
- product
- The product or area the backlog is for.
- goals
- This period's product goals, most important first, for example "reduce churn in the first 30 days".
- constraints
- Team capacity, deadlines, dependencies and anything already promised to customers.
- stakeholders
- Who will read the ranking, for example "sales, support and the leadership team".
- method
- The scoring method: RICE, ICE, value versus effort, or "suggest one".
- backlog
- The items, one per line, with whatever you know: description, who asked, how many, effort or reach estimates.
roadmap-update — Write a roadmap update for stakeholders
You need what shipped, what is next, what moved and why, for people outside the product team.
- product
- The product or area the update covers.
- period
- The period covered, for example "the third quarter" or "September".
- audience
- Who reads it and what they need, for example "sales and support, who need to know what to tell customers".
- asks
- What you need from readers, for example "two customers for the beta", or "nothing".
- shipped
- What shipped in the period, with dates and links to release notes or docs.
- planned
- What is planned next, with how confident you are in each item and any committed dates.
- changes
- What moved, was added or was dropped since the last update, and why.
- previous_update
- The last update you sent, so nothing in it goes missing. Write "none" if this is the first.
pricing-tiers-draft — Design pricing tiers for a product
You need plan names, what each includes and the reasoning before you test prices.
- product
- The product and what it does, in a sentence or two.
- segments
- Your customer groups and how they differ, for example "solo consultants, agencies of 5 to 20, larger firms".
- pricing_goal
- What you want pricing to do, for example "more customers moving to the middle plan".
- usage
- How each group uses the product: which features, how often, how much. Numbers from your analytics if you have them.
- costs
- Your cost to serve a customer or unit (hosting, support time, materials, payment fees) and any margin you need.
- price_references
- Your current prices and the prices of alternatives you have seen, each with its source and date.
tailor-resume-to-job-posting — Tailor your resume to a job posting
You need your real experience matched to what a specific posting asks for, without inventing anything.
- resume
- Your current resume, pasted as plain text.
- other_experience
- Relevant experience that is not on the resume yet, such as projects, tools or volunteer work. Write "none" if there is none.
- job_posting
- The full job posting, including the requirements and responsibilities.
- country
- The country where the job is, since resume conventions differ, for example the United States or Germany.
- page_limit
- How long the resume may be, for example "one page" or "two pages".
cover-letter-from-resume — Write a cover letter from your resume and the job posting
You need a short, specific cover letter that connects your experience to the role.
- resume
- Your resume, pasted as plain text.
- job_posting
- The full job posting.
- why_this_role
- Your real reasons for wanting this job and this company, in a few rough lines.
- hiring_manager
- The hiring manager's name if you know it, or "unknown".
- context_to_explain
- A career change, relocation or gap the letter should address briefly. Write "none" if there is none.
mock-interview-practice — Practice a job interview with feedback
You need likely questions for a role, a chance to answer, and honest feedback on each answer.
- job_posting
- The full job posting.
- resume
- Your resume, pasted as plain text.
- interview_type
- For example "phone screen with a recruiter", "hiring manager interview" or "panel with future peers".
- worries
- Questions or topics you find hard, for example "explaining why I left my last job". Write "none" if there are none.
- question_count
- How many questions to practice, for example 6.
resume-bullets-with-results — Rewrite resume bullets to show results
You need duty-style bullets turned into achievement bullets using numbers you can back up.
- target_role
- The kind of job you are applying for, for example "operations manager in logistics".
- role_context
- Your job title, team and what the role covered, in a line or two.
- bullets
- The bullets you want rewritten, as they are now.
- facts
- Numbers and results you could back up if asked, with where they come from if you know. Write "none" if you have none yet.
linkedin-headline-and-about — Rewrite your LinkedIn headline and About section
You need a profile that says clearly what you do and who you help, in your own voice.
- audience
- Who you want to reach, for example "recruiters hiring product designers" or "finance teams at mid-sized companies".
- goal
- What the profile should do for you, for example "win freelance clients" or "find a new role, quietly, while I am employed".
- current_profile
- Your current headline and About section, copied from LinkedIn.
- resume
- Your resume or a summary of your experience and results.
- voice_sample
- A few paragraphs you wrote without help, such as a post or an email. Write "none" if you have none.
interview-stories-star — Turn your experience into interview stories
You need concrete STAR stories for behavioral questions built from things you actually did.
- experience_notes
- Rough notes on situations you handled: projects, problems, conflicts, mistakes, wins. A few lines each is enough.
- resume
- Your resume, pasted as plain text.
- job_posting
- The job posting for the interview.
- story_count
- How many stories you want, for example 6.
self-assessment-for-review — Write your self-assessment for a performance review
You need to summarize your year with evidence, honest gaps and goals before review season.
- review_period
- The period the review covers, for example "this year" or "the first half of the year".
- review_form
- The questions or sections on your company's form, with word limits and the rating scale. Write "none" if there is no form.
- goals
- The goals you were set for this period.
- evidence
- Your wins, projects, figures and feedback received, with dates where you have them. Rough notes are fine.
- challenges
- Misses, setbacks or things you would do differently, and what you learned. A short honest answer usually reads better than none.
- next_goals
- What you want to grow into next, for example "lead a project end to end" or "move toward a senior role".
case-for-raise-or-promotion — Make the case for a raise or promotion
You need a written case from your results and market data before you ask your manager.
- request
- What you are asking for, for example "a promotion to senior analyst" or "a raise to a figure you name".
- manager_role
- Who you will ask, for example "my manager, the head of operations".
- current_role
- Your title, how long you have held it, and your current pay if you want it used.
- results
- Your results and contributions, with dates and figures where you have them.
- next_level
- The expectations for the role you want, from a career ladder or job description. Write "none" if there is none.
- market_data
- Pay figures you found yourself, each with its source, such as salary surveys, pay ranges in job postings or your company's pay bands. Write "none" if you have none.
- context
- Anything about timing: when reviews happen, budget news, recent changes in your team.
salary-negotiation-plan — Plan a salary or job offer negotiation
You need a target, a walk-away point and the words to use when you counter an offer.
- offer
- The offer as written or as told to you: base pay, bonus, equity, benefits, start date and any deadline.
- market_data
- Pay figures you found yourself, each with its source. Write "none" if you have none.
- situation
- Your current pay, other offers or interviews in progress, and constraints such as a notice period.
- priorities
- What matters most, in order, for example "base pay, remote days, start date".
- minimum
- The lowest total package you would accept, or "help me set it".
- channel
- Phone, video call or email.
post-interview-thank-you — Write a thank-you note after an interview
You need a short note that thanks the interviewer and reinforces one point from the conversation.
- role_title
- The job title you interviewed for.
- company
- The company's name.
- interviewers
- Each interviewer's name and role, one per line.
- conversation_notes
- What you talked about with each person: topics, problems they mentioned, anything they asked you to send.
- point_to_reinforce
- One strength to remind them of, or an answer you wish you had given better. Write "none" if there is none.
- channel
- Email or LinkedIn message.
networking-message-to-stranger — Write a networking message to someone you do not know
You need a short message asking for advice or a referral that respects the other person's time.
- ask
- What you want from them, for example "a 15-minute call about moving into product management" or "a referral for an opening on their team".
- recipient
- Their name and role, and anything you know from their posts, talks or published work.
- connection
- Anything you share with them, such as a school, a former employer or a mutual contact. Write "none" if there is nothing.
- my_background
- Two or three lines about you and what you are working toward.
- channel
- Email, LinkedIn message or LinkedIn connection request.
compare-job-offers — Compare two job offers side by side
You need pay, benefits, growth, commute and risks laid out so you can decide.
- offer_a
- The first offer, as written: pay, bonus, equity, benefits, time off, location, start date, deadline.
- offer_b
- The second offer, in the same detail.
- impressions
- What you learned about each team, manager and company in interviews or from your own research.
- priorities
- What matters most to you, in order, for example "learning, then pay, then commute".
- constraints
- Anything that limits your choice, such as location, a start date, family needs, a visa or a minimum income.
resignation-letter-and-plan — Resign professionally, with a letter and a handover plan
You need a short resignation letter and a plan for telling your manager and handing over.
- my_role
- Your job title and team.
- manager_name
- Your manager's name.
- last_day
- The last day you intend to work, or "to be confirmed".
- notice_terms
- What your contract or handbook says about notice, or "not sure".
- shareable_reason
- The reason you are happy to give, for example "a role closer to home", or "nothing".
- counteroffer_stance
- For example "I will decline any counteroffer" or "I would listen to one".
- current_work
- Your projects, recurring tasks, accounts and contacts, with who might take each over if you know.
career-change-skills-map — Map your skills to a new career
You need to see which of your skills transfer to a new field and what gaps to close first.
- target_field
- The role or field you are considering, for example "UX research" or "project management in construction".
- resume
- Your resume, pasted as plain text.
- other_experience
- Side projects, volunteer work or courses that may be relevant. Write "none" if there are none.
- target_postings
- Two to five real job postings for the role you want, pasted in full.
- why_change
- Your real reason for wanting the change, in a line or two.
- constraints
- Time, money, location or other limits on how you can make the move.
make-draft-sound-human — Make a draft sound like a person wrote it
You need an AI-assisted or stiff draft rewritten in a natural, specific voice with the filler removed.
- audience
- Who will read it, for example "our customers" or "my team".
- where_it_appears
- Where it will be published or sent, for example "a LinkedIn post", "a client email" or "the company blog".
- draft
- The draft to rewrite.
- voice_sample
- A few paragraphs the writer wrote without help, such as an email or a post. Write "none" if you have none.
- real_details
- Names, numbers, examples or moments the writer can use. Write "none" if you have none yet.
critique-draft-before-sending — Get honest feedback on a draft before you send it
You need a critique of structure, argument and clarity, with the weakest parts flagged, not a rewrite.
- draft
- The draft you are about to send.
- what_and_who
- What the draft is and who receives it, for example "a proposal to our CFO" or "an email to an unhappy client".
- goal
- What you want the reader to do or think afterward, for example "approve the budget" or "agree to a call".
- reader_concerns
- What the reader cares about most, or what they are likely to object to.
- my_worries
- Parts you are unsure about, for example "the second section feels long". Write "none" if there are none.
report-from-notes-and-data — Write a report from your notes and figures
You need findings, numbers and notes organized into a clear report with headings and a summary.
- audience
- Who will read the report, for example "the leadership team" or "our board".
- report_question
- The question the report answers or the decision it supports, for example "should we keep the second warehouse open?".
- notes
- Your notes: observations, interview notes, conclusions you have reached, next steps.
- data
- Figures, tables or exports pasted as text, with units and dates where you have them.
- required_sections
- Sections your organization's template requires, in order. Write "none" if there is no template.
- length
- How long it should be, for example "two pages" or "about 800 words".
cut-to-word-limit — Cut a text to a word or character limit
You need a text to fit a form, abstract or post limit without losing the main point.
- limit
- The limit and how it is counted, for example "250 words" or "1,300 characters including spaces".
- where_used
- Where the text will go, for example "a grant application field", "a conference abstract" or "a LinkedIn post".
- text
- The text to cut.
- must_keep
- Points, names, numbers or keywords that must survive the cut. Write "none" if there are none.
formal-letter — Write a formal letter: complaint, request or notice
You need a properly structured letter to a company, landlord, agency or supplier that states facts and asks for something specific.
- letter_type
- Complaint, request or notice, for example "complaint" or "notice of intent to end the lease".
- sender_details
- Your name, address, and any account or customer number.
- recipient
- The person or department, organization and address the letter goes to.
- facts
- What happened, in your own words, with dates, amounts, reference numbers and earlier calls or emails.
- relevant_terms
- The contract clause, policy or warranty wording that applies, copied exactly. Write "none" if you have none.
- desired_outcome
- Exactly what you want, for example "a refund of the full amount" or "repair of the heating within 14 days".
- response_deadline
- The date you want a reply by.
- next_step
- What you will do if there is no reply, for example "escalate to the ombudsman", or "nothing stated".
- enclosures
- Copies of documents you are including, such as receipts or photos. Write "none" if there are none.
grant-proposal-section — Draft a grant proposal section from your program facts
You need a need statement, goals, methods or evaluation section written from your real data and the funder's criteria.
- funder_guidelines
- The funder's instructions for this section: questions, scoring criteria, priorities and limits.
- program_facts
- What the program does, for whom, staff, partners who have agreed, timeline, budget figures and targets.
- program_data
- Figures on need and past results, each with its source, such as your own records or published statistics you have checked.
- other_sections
- Sections already drafted, so names and numbers stay consistent. Write "none" if there are none.
- section
- Which section to draft, for example "need statement", "goals and objectives", "methods" or "evaluation plan".
- funder
- The funder's name and the grant program.
- length_limit
- The limit for this section, for example "500 words" or "4,000 characters with spaces". Write "none" if there is none.
short-speech-for-work — Write a short speech for a work occasion
You need remarks for a farewell, award, launch or all-hands that sound like you and fit the time.
- occasion
- The event, for example "a farewell for a long-serving colleague", "a team award" or "a product launch".
- speaker_role
- Your role and your relationship to the audience or to the person being honored.
- audience
- Who will be there and roughly how many, for example "about 40 people from the sales team".
- duration
- How long you have, for example "three minutes".
- material
- Real stories, achievements, names and details you are happy to use, in rough notes.
- my_style
- How you usually talk, for example "dry humor, short sentences" or "warm and earnest".
- avoid
- Topics, people or details to keep out. Write "none" if there are none.
professional-bio-three-lengths — Write a professional bio in three lengths
You need a short, medium and long bio for a website, speaker page or proposal.
- person
- The person's name, and the pronouns to use if you want them used.
- uses
- Where the bios will appear, for example "our website, conference programs and client proposals".
- facts
- Their resume, LinkedIn profile or notes: roles, employers, achievements, credentials, education.
- emphasis
- What these readers should notice first, for example "her work on supply chain software".
- point_of_view
- Third person for speaker pages and proposals, first person for your own website or profile.
- personal_detail
- One human detail the person is happy to share, such as a hobby or where they live. Write "none" if there is none.
internal-how-to-article — Write an internal how-to article for colleagues
You need a wiki or intranet page that walks colleagues through a task step by step.
- task
- The task the article covers, for example "submit a purchase request over the approval limit".
- audience
- Who will use it and how familiar they are with the system, for example "new finance staff who have never used the billing system".
- steps_notes
- Your notes on how the task is done, as rough as they are, or a transcript of someone walking through it.
- access_needed
- The systems, permissions or tools someone needs before starting.
- common_problems
- Problems people hit and how they are fixed. Write "none" if you do not know of any.
- owner
- The person or team who maintains the page and answers questions.
summary-for-three-audiences — Summarize one document for different audiences
You need the same content summarized separately for leadership, your team and customers.
- document
- The document to summarize: a plan, report, announcement or decision record.
- leadership_needs
- What leadership needs from it, for example "whether to approve the budget" or "the risk to the launch date".
- team_needs
- What your team has to know or do as a result.
- customer_context
- Who the customers are and what you are allowed to tell them.
- confidential
- Anything that must stay internal, such as prices, partner names or unreleased plans. Write "none" if there is nothing.
restructure-long-document — Restructure a long document that does not flow
You need a rambling draft reorganized with a new outline and order before you polish the sentences.
- document
- The full draft to restructure.
- document_type
- What it is, for example "a strategy memo", "a research report" or "a policy document".
- audience
- Who will read it.
- reader_goal
- What the reader should understand, decide or do after reading.
- required_sections
- Sections your organization requires, in order. Write "none" if there are none.
award-nomination — Write an award nomination or submission
You need a persuasive, evidence-based nomination for a colleague, team or project.
- nominee
- Who you are nominating (a person, team or project), with their role or a one-line description.
- relationship
- Your relationship to the nominee, for example "their manager" or "a colleague on another team".
- award_criteria
- The award's criteria or questions and any word limits, copied from the nomination form.
- evidence
- Achievements, figures, dates and approved quotes, with who said each quote.
- word_limit
- The overall limit, for example "800 words", or "per question" if each question has its own.
objection-responses — Prepare honest answers to common sales objections
You need specific responses to the objections you keep hearing on price, timing or competitors.
- buyer_type
- Who you sell to, for example "operations managers at mid-sized manufacturers".
- product
- What you sell, in a sentence.
- objections
- The objections you hear, one per line, in the buyer's own words where you can.
- approved_facts
- Prices, terms, results and customer names you are allowed to use. Write "none" for anything you do not have.
- competitor_notes
- What you know about the competitors buyers mention, with where each fact came from. Write "none" if it does not apply.
proposal-from-call-notes — Write a sales proposal from discovery call notes
You need a proposal that uses the client's own words for the problem, scope, price and next steps.
- client_name
- The client company's name.
- call_notes
- Your notes or the transcript from the discovery call. Mark anything internal.
- offer_and_pricing
- What you are proposing: deliverables, options, prices and payment terms, exactly as approved.
- about_us
- Two or three facts about your company that matter to this client.
score-call-transcript — Score a sales call transcript against your qualification method
You need a call graded against MEDDICC, BANT or your own checklist, with the questions you missed.
- method_name
- The method you use, for example MEDDICC, BANT or your team's own checklist.
- method_criteria
- Each criterion with a one-line definition of what counts as covered, as your team uses it.
- deal_stage
- Where the deal was when the call happened, for example "first discovery call".
- prior_knowledge
- What you already knew about the deal before this call, or "nothing".
- transcript
- The call transcript, with speakers labeled if possible.
- reviewer
- Who uses the review, for example "me, before my next call" or "my manager for weekly coaching".
sales-call-role-play — Rehearse a sales call with AI playing the buyer
You need to practice discovery, objections or a negotiation with a realistic buyer before the real call.
- call_type
- The call you are preparing for, for example "first discovery call", "pricing negotiation" or "renewal with an unhappy customer".
- buyer_role
- The buyer's job title and the kind of company they work for.
- buyer_situation
- What is going on for them: the problem, any current supplier, pressures and deadlines.
- hidden_concerns
- Worries or objections the buyer has but will only reveal if asked well, for example "burned by a failed rollout last year".
- difficulty
- How hard to make it: "friendly", "realistic" or "tough and skeptical".
- what_i_sell
- Your product or service, its price range and what it does, as you would describe it on the call.
- call_goal
- What you want from the call, for example "agree a demo with their IT lead".
pipeline-review-prep — Prepare for a pipeline or forecast review
You need each deal's risk, next step and honest forecast category before your manager asks.
- reviewer
- Who runs the review, for example "my sales manager".
- review_date
- The date of the review.
- period_end
- The last day of the period being forecast, for example the end of the quarter.
- forecast_categories
- Your team's categories with what each requires, for example "Commit: verbal yes and paperwork started".
- deals
- One row per open deal, exported from your CRM, with name, amount, stage, close date, last activity, next step and notes.
- stale_days
- How many days without activity counts as stale for your sales cycle, for example 14.
elevator-pitch-three-lengths — Write a pitch in three lengths for one buyer type
You need a 10-second, 30-second and 2-minute pitch aimed at a specific buyer.
- buyer_type
- The one buyer you are pitching to, for example "practice managers at dental clinics".
- setting
- Where you will use it, written to follow "to use", for example "at networking events" or "at the start of cold calls".
- offer
- What you sell, how it works and what it costs, in a few sentences.
- buyer_problem
- The problem this buyer has, ideally in words they have used.
- differentiator
- What is genuinely different about you, as a fact a buyer could check.
- proof
- Results or customers you may mention, or "none".
- next_step
- What you want the listener to do, for example "agree to a 15-minute call".
key-account-plan — Build an account plan for a key customer
You need stakeholders, goals, risks and growth opportunities for an important account on one page.
- account_name
- The customer's name.
- audience
- Who reads the plan, for example "my manager and the account team".
- account_facts
- What they buy, contract value, renewal date, usage and support history.
- stakeholders
- Each person you know there: name, role, what they care about, and how strong your relationship is.
- customer_goals
- Their goals and priorities, from meetings, their plans or public statements, with where each came from.
- our_offerings
- Other products, services or plans you could offer this customer.
- plan_period
- The period the plan covers, for example "the next two quarters".
re-engage-quiet-prospect — Re-engage a prospect who went quiet
You need a message that restarts a stalled deal honestly, without guilt-tripping.
- prospect_name_and_role
- The prospect's name and job title.
- deal_history
- What happened so far: calls, demos, proposals, the last agreed next step and when you last heard from them.
- their_priorities
- What they said mattered to them, in their words if you have them.
- new_reason
- Something new and true you can mention, such as a feature they asked about or a useful article. Write "none" if there is nothing.
- short_channel
- Where the short version goes, for example "LinkedIn" or "a text message".
- sender_name
- Your name as you sign messages.
linkedin-connection-message — Write a LinkedIn connection request and first message
You need a short, personal note that gives a prospect a reason to connect and reply.
- prospect_name_and_role
- The person's name, job title and company.
- my_role
- Your role and company, for example "an account executive at a payroll software company".
- prospect_notes
- What you actually know: a post they wrote, a talk, a job change, a shared group. Include where you saw it.
- reason_to_connect
- Your honest reason for wanting to connect with this person.
- offer
- What you sell, in a sentence.
- note_limit
- The character limit for connection notes on your account, for example 200 or 300. Check LinkedIn's current rules.
competitor-battlecard — Build a competitor battlecard for your sales team
You need a one-page guide to where a rival wins, where you win, and how to answer their claims.
- our_product
- Your product or service name.
- competitor
- The competitor's name.
- our_facts
- Your features, pricing, limits and the proof you are allowed to share.
- competitor_info
- What you know about the competitor, each item with its source and date: their website, pricing page, reviews, analyst notes.
- deal_notes
- Notes from deals won or lost against them, or "none".
- today
- Today's date, so readers know how current the card is.
- stale_after
- How old a competitor fact can be before it needs rechecking, for example "six months".
expansion-offer-email — Propose an upgrade or expansion to an existing customer
You need to suggest more seats, a higher plan or a new product, tied to results the customer already has.
- customer_contact
- The person you are writing to, with their role.
- expansion_offer
- What you are proposing, for example "10 more seats" or "moving to the Business plan".
- account_facts
- What your records show: current plan, usage trends, results they have had, renewal date and any open issues.
- reason_now
- Why this makes sense now, for example "they are at 48 of 50 seats" or "they asked about reporting last month".
- price_and_terms
- The exact price and terms you are approved to offer.
- sender_name
- Your name as you sign emails.
win-loss-patterns — Find patterns in won and lost deals
You need to know why you win and lose from your deal notes and lost-reason fields.
- deal_export
- One row per closed deal with ID, outcome, amount, segment, lead source, competitor, lost reason and notes, exported from your CRM. Remove contact details first.
- period
- The dates the deals closed in.
- business_context
- What you sell and to whom, in a sentence or two.
- main_question
- The one thing you most want to know, for example "why we lose mid-size deals", or "none".
- audience
- Who reads it, for example "the sales leadership team".
annual-report-talking-points — Turn a company's annual report into talking points
You need a public company's stated priorities and risks mapped to what you sell before an executive meeting.
- report_text
- The parts of the annual report that matter most: the letter to shareholders, strategy, risk factors and management's discussion. Paste text, not images.
- our_offer
- What you sell and the problems it solves, in a short paragraph.
- company_name
- The company you are meeting.
- report_name
- Which report it is, for example "2025 annual report" or "10-K for fiscal 2025".
- attendees
- Who you are meeting, with their roles.
- meeting_purpose
- Why the meeting is happening and what you hope to agree.
answer-from-help-docs — Answer a customer question from your help docs and policy
You need an accurate, friendly reply that only uses what your documentation actually says.
- company
- Your company or product name.
- help_docs
- The help articles that relate to the question, with their links.
- policy
- Any policy that applies, such as refunds or account changes. Write "none" if no policy applies.
- customer_details
- What you know about the customer that matters here: plan, device, app version, account status.
- customer_message
- The customer's message, exactly as received.
- agent_name
- The name the reply is signed with.
order-delay-reply — Tell a customer their order or service is delayed
You need to explain a delay, give a realistic new date and offer what you can.
- customer_name
- The customer's first name.
- channel
- How it will be sent, for example "email" or "text message".
- order_details
- What they ordered, the order number and the original delivery or service date.
- delay_facts
- What you know: the cause you can share, the new date or range, how sure it is, and when you will know more.
- allowed_options
- What policy allows for this delay, for example "cancel for a full refund, or switch to an in-stock item". Write "none" if nothing extra applies.
- agent_name
- The name the message is signed with.
customer-onboarding-plan — Plan a new customer's onboarding
You need milestones, training and check-ins that get a new customer to first value quickly.
- customer_name
- The customer's company name.
- purchase_details
- What they bought: product, plan, number of users, add-ons and contract start date.
- customer_goals
- What they want to achieve, from the sales handoff or their own words.
- customer_team
- The people involved on their side and their roles, for example "Ops lead (sponsor), two admins, 40 end users".
- constraints
- Deadlines and limits: a go-live date, approvals needed, holidays, other projects.
- our_onboarding
- What your onboarding includes: number of sessions, hours, resources and who runs them.
- plan_length
- How long the plan covers, for example "30 days" or "90 days".
quarterly-business-review — Prepare a quarterly business review for a customer
You need results, usage, wins, issues and next-quarter goals for a customer review meeting.
- customer_name
- The customer's company name.
- meeting_length
- How long the meeting is, written to fit "a ___ meeting", for example "45-minute".
- attendees
- Who will be there from their side and yours, with roles.
- last_quarter_goals
- The goals you agreed with the customer for the quarter, with any targets.
- usage_data
- Usage and results for the quarter, ideally with the previous quarter for comparison.
- support_history
- Tickets, incidents and escalations this quarter, with how each was resolved.
- approved_updates
- Product updates you are allowed to share with this customer, or "none".
- next_quarter_ideas
- Goals or changes you want to propose for next quarter.
churn-risk-review — Spot churn risk in an account and plan a save
You need risk signals from usage, tickets and notes turned into a plan to keep the customer.
- account_name
- The customer's name.
- renewal_date
- When their contract renews or can be cancelled.
- today
- Today's date, so the timing of signals and actions is right.
- usage_data
- Usage over the last few months: logins, active users, key features used, seats.
- tickets
- Recent support tickets with dates, subjects and status.
- account_notes
- Your CRM notes, emails and meeting notes, with dates.
- approved_levers
- What you may offer to keep them, for example extra training or an executive call. Write "none" if nothing is approved.
bug-report-from-ticket — Turn a customer complaint into a bug report for engineering
You need steps to reproduce, expected and actual behavior, and impact written from a messy ticket.
- ticket
- The customer's ticket and the replies so far, exactly as written.
- support_notes
- What support checked, tried or reproduced, and the results.
- technical_details
- Plan, browser or device, app version and account ID, as far as you know them.
- severity_levels
- Your team's severity definitions, or "none" to leave severity out.
support-reply-quality-review — Score support replies against a quality checklist
You need agents' replies reviewed for accuracy, tone and policy with specific coaching notes.
- review_purpose
- What the review is for, for example "weekly one-to-one coaching" or "a monthly calibration session".
- checklist
- Your quality checklist: each item, what it means and how it is scored.
- policy_and_docs
- The policies and help content the replies should follow.
- conversations
- The conversations to review, each with an ID, the customer's message and the agent's reply. Remove customer names and contact details first.
quiet-customer-check-in — Check in with a customer who has gone quiet
You need a useful, low-pressure message to an account that stopped engaging.
- customer_contact
- The person you are writing to, with their role and company.
- my_role
- Your role for this customer, for example "customer success manager" or "account manager".
- account_context
- What they use the product for, when you last spoke, how usage has changed, open issues and past requests.
- useful_item
- Something genuinely useful to share: a tip for how they use it, a feature they asked for, a guide or an event. Write "none" if there is nothing.
- sender_name
- Your name as you sign emails.
customer-call-script — Write a call script for a common customer call
You need a short script with branches for calls like renewals, reminders or payment follow-ups.
- call_type
- The kind of call, for example "renewal reminder", "overdue payment follow-up" or "appointment confirmation".
- caller_role
- Who makes the calls, for example "account managers" or "front desk staff".
- company
- Your company or organization name.
- call_goal
- Why you are calling and what a good outcome is, for example "confirm the renewal or book a review call".
- call_facts
- The facts and options callers can offer: terms, dates, amounts and choices.
- call_rules
- Identity checks, required disclosures and anything callers must never say. Check these with whoever handles compliance, or write "none".
- common_responses
- What customers usually say on these calls, for example "not a good time", "I already paid", "I want to cancel".
known-issue-team-brief — Brief the support team on a known issue
You need agents to know the symptoms, workaround, what to say and when to escalate.
- issue_notes
- What engineering or the incident lead has shared: symptoms, affected areas, cause if known, workaround, status.
- approved_messaging
- What has been cleared to tell customers. Write "symptoms only" if nothing else is cleared.
- ticket_tagging
- The tag, macro or parent ticket agents should use, for example "tag known-issue-export and link to the parent ticket".
- escalation_path
- When to escalate and to whom, for example "cases with data loss go to the on-call engineer via the escalation form".
- allowed_offers
- Any credit or other remedy policy allows for this issue, or "none".
- next_update
- When the brief will next be updated, for example "4 p.m. today".
patient-billing-question-reply — Reply to a patient's billing question
You work in a medical office and need a clear, kind explanation of a bill, insurance and next steps.
- practice_name
- The name of your practice, clinic or office.
- channel
- How the reply will be sent, for example "the patient portal" or "a letter". Use a secure channel for anything with health details.
- patient_message
- The patient's question, exactly as received.
- bill_details
- The statement lines: dates of service, services, charges, insurance payments, adjustments and the balance due.
- insurance_details
- What the insurer reported, such as the explanation of benefits, or "not available".
- billing_policy
- Your payment options, payment plans, financial assistance and due dates, as written in your policy.
- contacts
- Who handles what, for example your billing office phone number and hours, and where patients find their insurer's number.
- staff_name
- The name the reply is signed with.
quick-topic-briefing — Get up to speed on an unfamiliar topic
You need the key ideas, terms, debates and what to read next on a work topic you know little about.
- topic
- The topic, named as specifically as you can, for example "carbon accounting for small manufacturers".
- role_and_reason
- Your job and why you need this now, for example "operations manager; we are choosing a supplier".
- current_knowledge
- What you already know or have read. Write "nothing yet" if you are starting from scratch.
- use_context
- Where you will use it, for example "a vendor call on Thursday" or "a project I join next month".
questions-from-long-document — Get answers from a long document with page references
You need specific answers from a long report, PDF or contract, each pointing to where it appears.
- document
- The full text of the document. If you copy from a PDF, keep the page numbers, or add a line such as "Page 12" at each page break.
- questions
- Your questions, numbered, one per line.
- document_description
- What the document is, for example "our supplier's master services agreement" or "the annual report of a company we are assessing".
- purpose
- What you will do with the answers, for example "prepare for a contract renewal meeting".
explain-concept-with-examples — Explain a work concept with examples from your field
You need a term or idea you keep hearing explained plainly with examples that fit your job.
- concept
- The term or idea, for example "working capital", "statistical significance" or "zero trust".
- where_heard
- Where it comes up, for example "in budget meetings" or "in our vendor's sales pitch".
- role_and_field
- Your job and industry, for example "office manager at a dental practice".
- current_understanding
- What you think it means, or the part that confuses you. Write "no idea yet" if you are starting from zero.
deep-research-request — Write a request for a deep research tool
You need a scoped research request with the questions, preferred sources and output format before you run it.
- research_topic
- The subject, in a sentence or two.
- decision
- What you will use the result for, for example "whether to enter a new regional market next year".
- what_i_know
- What you already know, believe or have read. Write "nothing yet" if you are starting fresh.
- scope_limits
- For example "EU only, sources from 2023 onward, companies under 500 staff". Write "none" if it is open.
- preferred_sources
- For example "government statistics and trade association reports". Write "none" if you have no preference.
- sources_to_avoid
- For example "vendor blogs". Write "none" if there are none.
- output_wanted
- The format and length you want back, for example "a two-page memo with a table of options".
market-overview-from-sources — Write a market overview from sources you provide
You need segments, main players, trends and gaps summarized from the reports and pages you paste.
- sources
- The reports, articles and web pages to work from, each starting with a label such as [S1], the publisher or title, and the date.
- market_definition
- The market you mean, for example "commercial cleaning services for offices in the UK".
- our_context
- What your organization does and why you are looking at this market. Write "none" for a neutral overview.
- audience
- Who will read it, for example "the leadership team".
- purpose
- What they will use it for, for example "decide whether to build a product for this market".
software-tool-shortlist — Shortlist software tools for your team
You need to compare tools against your must-haves, budget and integrations before booking demos.
- job_to_be_done
- The problem the tool should solve, for example "tracking client projects and billable hours".
- team
- Who will use it and how many, for example "12 people in two offices, mostly not technical".
- must_haves
- The requirements a tool has to meet to be considered, one per line.
- nice_to_haves
- Features that would help but are not essential, one per line. Write "none" if there are none.
- budget
- For example "under $15 per user per month" or "$5,000 a year".
- current_tools
- Systems it must connect to, such as your email, calendar, accounting software or single sign-on.
- requirements
- For example data stored in the EU, single sign-on or a security review. Write "none" if there are none.
- candidates
- Tools you already have in mind. Write "none" if you are starting fresh.
- vendor_info
- Text copied from vendors' pricing and feature pages, with the date you copied it. Write "none" if you have not collected any yet.
evidence-from-studies — Summarize what several studies say about a question
You need where the studies agree, where they differ and how strong the evidence is, before a decision.
- question
- The question you need answered, as specifically as possible, for example "Does a four-day week reduce staff turnover in customer service teams?".
- studies
- The studies: the full text, or at least the abstract, methods and results of each, with authors and year.
- decision_context
- The decision this informs and your setting, for example the size and type of your organization.
- audience
- Who reads the summary, for example "the leadership team".
industry-trends-briefing — Write a briefing on trends in your industry
You need a short update on what is changing in your industry for your team or leadership.
- industry
- Your industry, as narrowly as makes sense, for example "independent veterinary clinics".
- our_context
- What your organization does and what it is focused on this year, in a sentence or two.
- audience
- For example "my team" or "the leadership team at the quarterly review".
- period
- For example "the last quarter" or "since our last briefing in June".
- sources
- The articles, reports and notes to work from, each starting with a label such as [S1], the publisher and the date.
- word_limit
- For example 600.
customer-survey-design — Write a survey that gets honest, usable answers
You need short, unbiased survey questions for customer feedback, staff input or market research.
- survey_goal
- What you want to learn, in a sentence or two.
- decisions
- Each decision the results will feed, one per line, for example "whether to keep weekend opening hours".
- respondents
- For example "customers who bought in the last six months" or "all staff at two sites".
- channel
- For example an email link, a QR code in store, or a pop-up in the app.
- time_limit
- For example "5 minutes".
- draft_questions
- Questions you already have. Write "none" to start from scratch.
research-interview-guide — Write a guide for research interviews
You need open, non-leading questions for interviews with customers, staff or experts.
- research_goal
- What you need to learn, ideally as two or three questions.
- participants
- Who they are, for example "small business owners who cancelled in the last three months".
- interview_length
- For example 45 minutes.
- interview_format
- For example video call, phone or in person.
- assumptions
- What your team believes and wants to check, one per line. Write "none" if you are exploring.
articles-to-digest — Turn a pile of articles into a short digest
You need several articles or newsletters reduced to what matters for your work and why.
- work_context
- Your role and the topics you care about, for example "buyer for a regional grocery chain; prices, suppliers, regulation".
- reader
- For example "me" or "the sales team".
- articles
- The full text of each article or newsletter, each starting with its title, publication and date.
- word_limit
- For example 400.
learning-plan-for-work-skill — Make a learning plan for a new work skill
You need to get competent at a tool or skill in a few weeks with practice tasks and checkpoints.
- skill
- For example "Power BI", "running workshops" or "basic SQL".
- goal
- What you need to do with it, and the date, for example "build our weekly sales dashboard by the end of next month".
- current_level
- What you can already do, for example "comfortable with Excel formulas, never used pivot tables".
- time_available
- For example "4 weeks, 3 hours a week".
- resources
- What you can use, for example a company training license, a test account or a colleague. Write "none" if there is nothing.
project-plan-from-goal — Turn a project goal into a plan with milestones
You need phases, tasks, owners, dependencies and milestones from a goal and a deadline.
- project_goal
- What the project will achieve, in a sentence or two.
- definition_of_done
- For example "new booking system live at all three clinics and the old one switched off".
- start_date
- When work can start.
- deadline
- The date, and whether it is fixed or can move.
- constraints
- Budget, fixed dates, approvals and outside dependencies. Write "none" if there are none.
- team
- Each person or role and how much time they can give, for example "analyst, two days a week".
- notes
- Tasks you know about, any estimates, and decisions already made. Rough notes are fine.
steering-committee-update — Write a project update with status for sponsors
You need a red, amber or green status with progress, risks, decisions needed and next steps for sponsors.
- project_name
- The project's name.
- reporting_period
- For example "March 1 to 14".
- audience
- For example "the steering committee: COO, finance director, head of operations".
- previous_status
- Last report's overall color and its main point, or "first report".
- rag_definitions
- Your organization's definitions of red, amber and green, or "default".
- baseline
- The agreed milestones and dates, budget and scope that progress is measured against.
- status_notes
- This period's notes: what was done, what slipped, spend to date, new risks, anything waiting on a decision.
risk-register — Build a risk register for a project
You need risks listed with likelihood, impact, owner and what you will do about each one.
- project_summary
- What the project is, its goal and deadline, in two or three sentences.
- roles
- For example "project manager, IT lead, finance partner, supplier account manager".
- scales
- Your organization's likelihood and impact scales, or "default".
- project_notes
- The plan, meeting notes and any worries people have raised.
project-charter — Write a project charter and scope statement
You need goals, scope, out-of-scope items, success measures and roles agreed before work starts.
- project_name
- The project's name.
- sponsor
- Name or role of the person who owns the outcome.
- project_manager
- Name or role of whoever runs the project day to day.
- budget_and_dates
- Budget, deadline and any fixed dates. Write "not set" for anything undecided.
- stakeholders
- Teams and roles involved in or affected by the project.
- project_notes
- Why the project exists, what it should achieve, decisions already made, and what is in and out as far as you know.
kickoff-meeting-plan — Plan a project kickoff meeting
You need the kickoff agenda, roles, ground rules and first actions for a new project.
- project_summary
- The charter, or a summary of the goal, scope, timeline and team.
- attendees
- Who will be there and their roles, for example "sponsor, project manager, two developers, finance analyst".
- meeting_length
- For example 90 minutes.
- meeting_format
- In person, remote or mixed.
- kickoff_goals
- For example "agreement on scope and the first month's priorities".
- concerns
- Anything sensitive, for example two teams with competing priorities. Write "none" if there are none.
change-request — Write a change request when scope changes
You need to document a new request and its effect on time, cost and scope so someone can approve it.
- project_name
- The project's name.
- change_description
- What is being asked for, in a few sentences.
- requested_by
- Who asked, and the date.
- reason
- Why they want it, in their words if you have them.
- approver
- Who decides, for example "the project sponsor" or "the change board".
- recommendation
- Your recommendation and the reason, or "none" to leave the decision open.
- baseline
- The agreed scope, key dates, budget and the contingency left.
- impact_notes
- The team's estimates of extra work, cost and delay. Write "none yet" if nothing has been estimated.
lessons-learned-review — Run a lessons-learned review after a project
You need to collect what went well, what did not and what to change next time, without blame.
- project_summary
- What the project was and what it delivered, in two or three sentences.
- planned_vs_actual
- For example "planned to finish in March, finished in May; budget 10% over; reporting module dropped".
- audience
- For example "the project team and the project office".
- team_input
- Everything the team said: retrospective notes, survey answers, comments. Remove names from criticism first.
pre-mortem — Run a pre-mortem on a plan
You need to imagine the project has failed and list the likely causes while there is still time to act.
- project_context
- What the project is and what success looks like.
- key_dates
- The deadline and any milestones that matter.
- known_concerns
- Worries the team has already mentioned. Write "none" if there are none.
- plan
- The plan: phases, tasks, owners, dates, budget, whatever you have.
go-live-checklist — Build a launch or go-live checklist
You need every step, owner, check and rollback point for a launch or switchover.
- launch_description
- For example "new payroll system replacing the old one for all staff".
- go_live_window
- For example "Saturday, 8 a.m. to 2 p.m.".
- affected_users
- Who will notice the change, and roughly how many people.
- teams
- Teams and roles taking part, for example "IT, payroll, the vendor's support team".
- rollback_options
- How you could return to the old state, or "not worked out yet".
- plan_notes
- Your launch plan, test status, dependencies and anything already agreed.
stakeholder-communication-plan — Map stakeholders and plan project communications
You need who cares about the project, what each needs to hear, and how often.
- project_summary
- What the project is and what it will change, in two or three sentences.
- timeline
- Key dates such as approval, pilot and go-live.
- channels
- For example team meetings, email, the intranet, all-hands meetings, chat channels.
- stakeholders
- Each group or role, with what you know about their interest and how they feel about the project.
change-rollout-plan — Plan how to roll out a new system or process to people
You need training, communication and support steps so people actually adopt a change.
- change_description
- For example "moving expense claims from spreadsheets to a shared expense system".
- reason
- Why the change is happening, as plainly as you can put it.
- affected_groups
- For example "finance team (6), managers (40), all staff who claim expenses (300)".
- timeline
- Key dates such as pilot, go-live and when the old way ends.
- support
- Trainers, champions, help desk hours or budget you can use. Write "none" if there is nothing extra.
- concerns
- What people have said or are likely to say. Write "none known" if you have not heard any yet.
- success_measures
- For example "90% of expense claims submitted in the new system by the end of the quarter".
reschedule-after-date-change — Rework a schedule when one date moves
You need to see which tasks and deadlines shift when one date changes and where slack can absorb it.
- date_change
- Which task or date moved, from when to when, and why, for example "supplier delivery moved from May 6 to May 20".
- fixed_dates
- Deadlines that cannot change, such as a launch or contract date. Write "none" if everything can move.
- working_calendar
- For example "Monday to Friday; office closed May 26".
- schedule
- The task list from your plan or spreadsheet, with start and finish dates, durations and dependencies.
one-page-business-plan — Write a one-page business plan
You need your customer, offer, pricing, costs and first steps on a page before you start or grow a business.
- plan_reader
- Who will read it, for example "just me", "a business partner" or "a small business adviser at my bank".
- plan_use
- What it is for, for example "decide whether to go full time" or "apply for a small loan".
- business_summary
- The business in a sentence, for example "a mobile dog grooming van serving one town".
- stage
- For example "idea only", "selling part time for six months" or "three years in, adding a second location".
- notes
- Everything you know: who buys, what you sell, your prices, start-up and monthly costs, money available, and what you have tried so far.
test-business-idea — Pressure-test a business idea before you spend money
You need the riskiest assumptions in your idea and cheap ways to test them.
- idea
- The idea in a few sentences: what you would sell, to whom, and how.
- target_customer
- Who you think will buy, as specifically as you can, for example "owners of older homes who rent them out".
- price
- What you would charge, or a range if you are unsure.
- evidence_so_far
- Conversations, pre-orders, sales or research so far. "Nothing yet" is fine.
- test_budget
- For example "$300 and four weekends".
price-your-services — Set prices for your products or services
You need prices that cover costs, fit the market, and that you can explain to customers.
- what_i_sell
- Your products or services, for example "bookkeeping for sole traders" or "handmade candles in three sizes".
- costs
- Direct costs per sale or job (materials, supplies, subcontractors) and monthly overhead (rent, software, insurance, phone, vehicle).
- income_goal
- What you want to pay yourself, per month or per year, before tax.
- capacity
- How many billable hours, jobs or units you can actually handle in a month.
- market_prices
- Prices you have actually seen, with where you saw them. Write "none" if you have not checked.
- customers_and_value
- Who buys from you and what they value, for example speed, specialist skill or convenience.
- current_prices
- What you charge now, or "none" if you are just starting.
review-request-message — Ask customers for a review
You need a short, well-timed message that makes leaving a review easy.
- business_name
- Your business name.
- platform
- Where you want the review, for example Google, Facebook, Etsy or Trustpilot.
- what_we_do
- What you did for the customer in a few words, for example "house cleaning" or "bike repairs".
- timing
- For example "the day after the job is finished" or "a week after delivery".
- channel
- Text message, email, or both.
- review_link
- The direct link to your review page, from your account on that platform.
- signer
- Who signs it, for example "Dana at the shop".
- personal_detail
- A detail about this customer's job or order, or "none" for a standard message.
google-business-profile — Write your Google Business Profile description and updates
You need a local business profile and short posts that help nearby customers find and choose you.
- business_facts
- What you do, your services, hours, how to book, how long you have run, and any awards or licenses you can show.
- service_area
- The town, neighborhoods or radius you serve.
- customer_themes
- What customers ask before buying or mention in reviews, for example "parking" or "how fast we respond".
- post_topics
- Upcoming news, offers, events or seasonal reminders, one per line.
- description_limit
- The current character limit for the description, for example "750 characters". Check it in your profile editor.
about-and-services-pages — Write your website's About and Services pages
You need clear pages that say what you do, who you do it for and how to hire you.
- business_name
- Your business name.
- what_we_do
- What you do in a phrase, for example "garden design for small urban yards".
- ideal_customers
- Who you do your best work for, for example "first-time homeowners with a budget under $10,000".
- background
- How you started, your experience and training, how you work, and the area you serve.
- services
- Each service you offer, with what is included, who it suits, price if you show it, and typical timing.
- how_to_hire
- The next step for a visitor, for example "book a free 15-minute call" with the link, or a phone number.
- voice
- A few words, for example "warm and plain-spoken", or a paragraph you wrote that sounds like you.
real-estate-lead-follow-up — Follow up with a new real estate lead
You need a fast, personal reply to a buyer or seller inquiry and a few follow-ups that do not feel automated.
- lead_message
- The inquiry exactly as it arrived, including the property address or ID if there is one.
- lead_source
- For example a listing portal, your website, an open house sign-in or a referral.
- lead_type
- Buyer, seller, renter, or not yet clear.
- property_or_service_facts
- Verified facts about the listing they asked about, or about how you work with sellers. Write "none" if they did not ask about a property.
- contact_preference
- For example "email only" or "gave a mobile number and asked for a text".
- agent_details
- Your name, brokerage, phone and any license line your brokerage requires.
real-estate-client-update — Update a buyer or seller on their transaction
You need to explain offers, inspection results or closing steps to a client in plain terms.
- client_role
- Buyer or seller.
- update_facts
- What happened, as you know it: offer terms, inspection items, appraisal value, lender news. Paste report excerpts where useful.
- deadlines
- Dates such as the inspection response, financing and closing, exactly as they appear in the contract.
- my_recommendation
- What you would advise, or "none" to set out the options without a recommendation.
- client_actions
- Documents, signatures, decisions or payments you need from them, with dates.
- channel
- Email or text.
explain-comps-to-seller — Explain a comparative market analysis to a seller
You need to walk a seller through comparable sales and a recommended price honestly.
- subject_property
- The seller's home with the features you verified: bedrooms, bathrooms, size, condition, updates, lot.
- comps
- Each comparable sale: address or ID, sale date, sale price, main differences, and your adjustment with the reason.
- competition
- Active and pending listings buyers will compare it to, with list prices. Write "none" if you are not including them.
- price_recommendation
- Your range and the list price you recommend.
- seller_expectation
- The price the seller hopes for, or what they have said, for example "a neighbor sold for more last year".
- format_use
- For example "talking points for the listing appointment" or "an email to send with the CMA".
client-welcome-packet — Write a welcome packet for new clients
You need new clients to know what happens next, what you need from them and how to reach you.
- business_name
- Your business name.
- service
- What you provide, for example "brand identity design" or "monthly bookkeeping".
- process
- The steps from signed agreement to finished work, with typical timing.
- client_inputs
- Everything you need from a new client (files, access, decisions, approvals) and when you need it.
- communication
- Channels, your hours, how quickly you reply, and what to do if something is urgent.
- payment_terms
- Deposit, invoice timing, due dates and how clients pay.
- change_policy
- For example "anything outside the proposal is quoted separately before I start it".
- common_questions
- Questions new clients usually ask, with your answers if you have them.
- voice
- A few words on how you sound, for example "friendly and organized".
- signer
- Who signs the welcome, for example your first name and role.
scope-creep-reply — Reply when a client asks for work outside the agreed scope
You need to say yes, no or "for an extra fee" while keeping the client relationship good.
- client_request
- The client's message asking for the extra work.
- agreed_scope
- The scope section of your proposal or contract, pasted as written.
- my_answer
- Yes as part of the current work, yes for an extra fee, later, or no.
- extra_terms
- The price and the effect on the timeline, or "I'll quote it".
- relationship_notes
- For example "new client with more work likely" or "third extra request this month".
seasonal-promotion-plan — Plan a seasonal sale or promotion
You need the offer, timing and messages for a holiday or seasonal promotion that protects your margin.
- business_name
- Your business name.
- occasion
- For example Black Friday, back to school, Mother's Day or the start of summer.
- products_and_costs
- The items you might promote, each with its price and what it costs you.
- past_results
- What happened last time: the offer, the sales, what you would change. "None" is fine.
- goal
- For example "clear winter stock", "bring back lapsed customers" or "sell 50 gift sets".
- dates
- When the promotion could start and end.
- channels
- For example an email list, Instagram, the shop window or a marketplace.
- budget
- What you can spend on ads, printing or extra stock. "Nothing" is fine.
specific-feedback-for-report — Give specific feedback to someone on your team
You need praise or correction that names the behavior, its impact and what to do next.
- person
- Their first name or role, for example "Priya, a support specialist on my team".
- feedback_type
- Praise, correction, or both.
- observations
- What you saw or heard yourself, with dates and the effect it had. Mark anything second-hand.
- desired_behavior
- What you want them to keep doing, or to do instead, in a sentence.
- context
- Anything that matters: how long they have been in the role, workload, earlier conversations. "None" is fine.
- setting
- For example "our weekly 1:1" or "a quick chat after the client meeting".
performance-improvement-plan — Write a performance improvement plan
You need clear expectations, support, check-ins and timelines for someone who is underperforming.
- employee_role
- Their role, and first name if you like, for example "Jordan, account coordinator".
- hr_contact
- Who in HR will review it, for example "our HR business partner".
- role_expectations
- The expectations from the job description, goals or level guide that apply here.
- documented_gaps
- Each gap with dated, specific examples from your records.
- previous_conversations
- When the gaps were raised before and what was said, for example "raised in 1:1s on March 3 and March 17".
- support_offered
- Training, coaching, changed workload, tools or time you can provide.
- plan_length
- For example 60 days. Follow your company's policy.
- policy_outcome
- What your policy says happens if the plan is or is not met, as HR has given it to you.
leadership-monthly-update — Write a monthly update for leadership or the board
You need results, risks and decisions needed in a short update senior people will read.
- audience
- Who reads it, for example "the leadership team" or "the board".
- team_or_area
- The team, function or project the update covers.
- results
- This month's numbers and outcomes, with notes on why they moved where you know.
- targets
- The targets or plan for the month, so results can be compared.
- risks
- Current risks and issues, with what you are doing about each.
- asks
- Decisions or help you need, with your recommendation and deadline. "None" is fine.
- next_month
- Your priorities for next month.
- last_update
- Last month's update, or "none".
mediate-team-conflict — Plan how to mediate a conflict between two team members
You need a fair way to hear both sides, find the real issue and agree on next steps.
- conflict_summary
- What has happened, from what you have seen and been told. Mark what you saw yourself and what is second-hand.
- people_roles
- For example "two senior designers" or "a team lead and an analyst on another team".
- impact
- How it shows up in the work, for example missed handoffs or tension in meetings.
- tried
- Conversations or changes already tried. "Nothing yet" is fine.
- my_relationship
- For example "I manage both" or "I manage one; the other reports to a peer".
- hr_contact
- Who to involve if it turns out to be a formal matter, for example "our HR business partner".
anticipate-team-questions — Prepare answers to the questions your team will ask
You need honest answers ready before you share news your team will push back on.
- news
- What you will announce, in your own words.
- decided_vs_open
- Which parts are final and which are still being worked out.
- confidential
- Anything you must not share yet. Write "none" if everything can be shared.
- team_impact
- Who is on the team and how the news affects their work, roles or plans.
- setting
- For example "team meeting, then 1:1s" or "an all-hands with open Q&A".
promotion-case-for-report — Write a promotion case for someone on your team
You need an evidence-based case that shows a direct report already works at the next level.
- employee_role
- Their role and first name, for example "Alex, software engineer".
- current_level
- Their current level or title.
- target_level
- The level or title you are proposing.
- audience
- Who decides, for example "the calibration committee" or "my director".
- level_expectations
- The expectations for the target level, from your career framework or level guide.
- evidence
- Projects and results with dates, scope and impact, from your notes, reviews and their work.
- peer_feedback
- Feedback from peers and stakeholders, quoted exactly. Write "none" if you have none.
- growth_areas
- Where they are still developing, honestly stated.
- format_rules
- Your company's template, sections or word limit. Write "none" if there is no set format.
headcount-request — Request headcount for a new role
You need to justify a new hire with workload data, cost and what happens if you do not hire.
- role_title
- The role you want to hire, with level if known, for example "senior support specialist".
- approver
- Who approves it, for example "my director and the finance partner".
- team_today
- Who is on the team now and what they cover, in a sentence or two.
- workload_data
- Numbers that show the load: volumes, backlog, overtime, response times, trends over recent months.
- role_scope
- The main work the new person would take on.
- cost_figures
- The salary band and any other costs you know. Write "ask finance" if you have none.
- impact_without_hire
- What slips, breaks or costs more if the role is not filled.
- alternatives
- Other options you looked at, such as a contractor or automation, and what you found.
- timing
- The start date you need and the reason, for example a seasonal peak or a launch.
team-strategy-one-pager — Write a one-page strategy for your team
You need to explain where your team is going, why, what you will do and what you will stop doing.
- team_name
- Your team's name.
- company_priorities
- The company's goals or priorities for the period, as leadership wrote them.
- current_state
- What your team owns, how it is performing, and what people say about it.
- challenges
- The main problems or opportunities you see.
- focus_ideas
- What you think the team should focus on, as a rough list.
- stop_ideas
- Work you think the team should stop, pause or do less of.
- constraints
- People, budget, skills or other teams you depend on.
- time_frame
- For example "the next 12 months" or "this fiscal year".
team-working-agreement — Write a team working agreement
You need shared norms for meetings, response times, decisions and focus time that your team agrees to.
- team_name
- Your team's name.
- team_facts
- Size, locations and time zones, and the main tools you use, for example "eight people in three time zones, using Slack and Zoom".
- team_input
- What people said about how they want to work: survey answers, retrospective notes or meeting notes.
- problems
- What is not working now, for example "too many meetings" or "decisions get reopened".
- company_policies
- Policies on hours, remote work or availability the agreement must respect. Write "none" if there are none.
team-planning-workshop — Plan a team planning workshop or offsite agenda
You need a facilitated agenda with exercises that ends in decisions, not just discussion.
- duration
- For example "half-day", "full-day" or "two-day offsite".
- team_name
- The team or group attending.
- decisions_needed
- The decisions the workshop must produce, for example next half's priorities or who owns a new area.
- context
- Results, company priorities, constraints and anything the team should know before deciding.
- attendees
- Who is coming and anything about the group, for example "ten people, two new, one strong voice who tends to dominate".
- setting
- In person, remote or hybrid, and the room or tools you have.
- prework_possible
- How much preparation you can ask for, for example "about an hour of reading" or "none".
recurring-meeting-audit — Audit your team's recurring meetings
You need to decide which meetings to cut, shorten, merge or replace with a written update.
- meetings
- Each recurring meeting: name, frequency, length, attendees, stated purpose, and what really happens in it.
- team_context
- Team size, time zones, and whether people work remotely, in the office or both.
- team_feedback
- Comments from a survey, retrospective or 1:1s. Write "none" if you have not asked yet.
- fixed_meetings
- Meetings you cannot change. Write "none" if you control them all.
coding-agent-refactor — Brief a coding agent to refactor without changing behavior
You need a coding agent to clean up code while tests keep passing and behavior stays the same.
- target_files
- The files, folder or module to refactor, for example src/billing/invoice.ts.
- problems
- What makes it hard to work with, for example "one 300-line function" or "the same logic copied in three places".
- public_interface
- Functions, classes, endpoints or exports that other code depends on and that must keep working exactly as now.
- pattern_files
- An existing file or module structured the way you want this one to be. Write "none" if there is none.
- refactor_aim
- What the refactor should achieve, for example "each pricing rule lives in its own function with a name that says what it does".
- test_command
- The command that runs the tests, for example npm test or pytest.
- coverage_notes
- For example "good tests for the main path, none for errors" or "not sure".
- off_limits
- Files, folders or systems that must not change, for example migrations or generated code.
- max_files
- The number of files above which the agent must check with you first, for example 5.
technical-design-doc — Write a short technical design document
You need the problem, approach, alternatives and risks written up before the team builds.
- reviewers
- Who reviews it, for example "the platform team and our staff engineer".
- problem
- What is wrong or missing, who it affects, and why it needs solving now.
- approach_notes
- Your notes on the approach you favor: components, data, interfaces, sketches in words.
- current_system
- The parts of today's system the change touches: services, data stores, interfaces.
- alternatives
- Other approaches and why you leaned away from them. Write "none yet" if you have not compared any.
- constraints
- Deadlines, required technologies, compliance, performance or budget limits.
- known_questions
- Questions you already know are open. "None" is fine.
offer-letter-from-terms — Draft an offer letter from agreed terms
You need a clear offer letter from the agreed role, pay, start date and conditions, ready for HR or legal review.
- candidate_name
- The candidate's full name, as it should appear on the letter.
- role_title
- The job title, as agreed.
- company
- Your company's legal or trading name, as HR uses it on letters.
- agreed_terms
- Everything agreed: title, manager, pay and pay frequency, start date, location, hours, employment type, benefits and conditions such as a background check.
- approved_wording
- Standard clauses your HR or legal team has approved for offer letters. Write "none" if you have none.
- acceptance_details
- How to accept and by when, for example "sign and return by replying to this email within five working days".
- signer
- Who signs the letter, with their title.
passive-candidate-outreach — Write a recruiting message to a passive candidate
You need a short, specific message that gives someone who is not job hunting a reason to talk.
- candidate_first_name
- The person's first name.
- channel
- How you will send it, for example a LinkedIn message or email.
- candidate_background
- What you know about their work from public sources: projects, talks, articles, roles. Work facts only.
- role_details
- The role, why it exists, what is interesting about it, and the pay range if you can share it.
- connection
- How you found them or who referred them, or "none".
- sender
- Your name and role, as they should appear in the signature.
workplace-policy-from-decisions — Draft a workplace policy from your decisions
You need a policy on remote work, leave or conduct written from decisions you have made, with gaps flagged for legal review.
- policy_topic
- What the policy covers, for example remote and hybrid work, parental leave or a code of conduct.
- organization
- Your organization's name.
- decisions
- What you have decided, in any form: bullet notes, an email thread or meeting notes.
- scope
- Who the policy covers and where they work, for example "all employees in the US and Canada".
- related_policies
- Names of policies this one should refer to, such as an expense or leave policy. Write "none" if there are none.
- policy_owner
- Who owns the policy, for example "the head of people".
reply-to-employee-hr-question — Answer an employee's HR question kindly and accurately
You need a clear reply about leave, pay or benefits that quotes the relevant policy.
- sender
- Your name and role.
- employee_message
- The employee's question, as they sent it.
- policy_text
- The policy sections that apply, pasted with their section numbers.
- employee_facts
- Relevant facts from HR records, such as start date, hours or the plan they are enrolled in. Write "none" if not needed.
- contact
- Who to contact for anything else, for example "the HR inbox" or your own name.
summarize-written-grievance — Summarize a long written grievance neutrally
You need the specific allegations, dates, people and requests pulled out of a long complaint letter.
- grievance_text
- The grievance letter or email, in full.
- procedure
- Your grievance procedure, or its key steps and deadlines.
- handler
- Who handles the grievance, for example "the HR business partner for operations".
engagement-survey-action-plan — Turn engagement survey results into an action plan
You need a few priorities, owners and actions from survey results that managers can actually carry out.
- audience
- Who uses the plan, for example "the leadership team and 12 people managers".
- timeframe
- The period the plan covers, for example "the next two quarters".
- survey_results
- Scores by question or theme, changes since last time, the response rate and comment themes with counts. Remove anything that identifies a person.
- constraints
- Work already under way and limits on budget, time or people. Write "none" if there are none.
- min_group_size
- The smallest group you report on, to protect anonymity, for example 5.
written-warning-record — Document a disciplinary conversation or written warning
You need factual, neutral documentation of a conduct or performance issue and what happens next.
- document_type
- What your process calls it, for example "record of a conversation" or "first written warning".
- employee_role
- The employee's role and team. Their name can be added after review.
- expectation
- The policy, standard or target the employee was expected to meet, and when it was communicated.
- incidents
- What happened, with dates, as you or others observed it.
- earlier_steps
- Earlier conversations, coaching or warnings, with dates. Write "none" if there were none.
- meeting_notes
- Your notes from the meeting, including the employee's response in their words.
- next_steps
- What was decided: the changes expected, support offered, review date and any consequences HR has approved.
benefits-enrollment-explainer — Explain benefits or open enrollment to employees
You need plan options, deadlines and next steps explained so employees can choose.
- enrollment_event
- What this is about, for example "open enrollment for next year's health plans" or "the new dental plan".
- audience
- Who is eligible, for example "all full-time US employees".
- plan_details
- Each plan's name, what it covers and its costs, copied from the official plan summaries.
- key_dates
- When enrollment opens and closes, and when coverage starts.
- how_to_enroll
- The steps, the portal or form, and any documents employees need.
- changes
- What is new or different from last year, or "none".
- contact
- Who answers questions, for example "the benefits team at the HR inbox".
pay-increase-scenarios — Plan pay increases within a fixed budget
You need options for distributing a raise budget fairly using performance and pay position.
- decision_makers
- Who decides, for example "the department head and the HR business partner".
- budget
- The total increase budget, as an amount or a percentage of current payroll.
- guidelines
- Your rules for increases, such as minimum and maximum percentages, who is eligible and the effective date. Write "none" if you have none.
- employee_data
- One row per person: an ID instead of a name, role, current pay, range minimum, midpoint and maximum, and latest rating. Works best with up to 30 rows.
- currency
- The currency of the pay figures, for example US dollars.
succession-plan-nine-box — Build a succession plan with a nine-box grid
You need key roles, possible successors, readiness and development steps in one view.
- audience
- Who will discuss the plan, for example "the leadership team and the HR director".
- key_roles
- The roles that matter most for continuity, why each matters, and whether the holder may leave or move soon.
- talent_notes
- One block per possible successor, using initials or IDs, with evidence of performance and potential and any career interests they have told you about.
- horizon
- How far ahead you are planning, for example "the next three years".
termination-meeting-plan — Prepare for a termination meeting
You need a short, respectful script and logistics checklist for letting someone go.
- employee_role
- The person's role and team.
- attendees
- Who will be in the meeting, for example "the manager, who leads, and an HR partner".
- approved_reason
- The reason HR or counsel has approved, in the words that may be used in the meeting.
- approved_terms
- The approved terms: last day, final pay timing, any severance, benefits, equipment return, references and what the team will be told.
- logistics
- Date, time, place or video link, and when system access will change.
- hr_contact
- Who handles questions and concerns afterward, for example "our HR business partner".
lesson-plan-from-objective — Plan a lesson from a learning objective
You need a lesson with timing, activities, checks for understanding and materials.
- lesson_length
- How long the lesson is, for example 50 minutes.
- learners
- Grade or age and subject, for example "7th grade science".
- objective
- What students should be able to do by the end, for example "explain why the moon has phases".
- class_context
- Class size, what students already know, materials and technology available, and supports some students need, described without names.
- source_material
- Textbook pages, notes or a standard to teach from. Write "none" if you have none.
adapt-material-reading-levels — Adapt a text or worksheet for different levels
You need the same material at several reading levels or with supports for different learners.
- versions
- Which versions you need, for example "three reading levels: grade 3, grade 5 and grade 7" or "an on-level version and one for English learners".
- learners
- Who the material is for, for example "a 6th grade social studies class".
- original_material
- The text, worksheet or questions to adapt.
- must_keep
- The key ideas and terms every student must meet, for example "evaporation, condensation, the water cycle".
- supports
- Supports you want, such as a glossary, sentence starters or visuals described in words. Write "any" to let the model choose.
report-card-comments — Write report card comments from your notes
You need specific, kind and varied comments built from your own notes on each student.
- grading_period
- For example "the first semester" or "term 2".
- subject_and_grade
- The subject and grade, for example "4th grade math".
- student_notes
- Your notes on each student: strengths, specific work, areas to grow and next steps. Paste up to 10 students at a time.
- guidelines
- Your school's rules for comments: required elements, words to avoid, length. Write "none" if there are none.
- comment_length
- The length of each comment, for example "60 to 80 words".
reply-to-parent-email — Reply to a parent's email
You need a calm, clear reply to a parent's question or concern that keeps the relationship good.
- teacher_name
- Your name as you sign emails to families.
- parent_email
- The parent's email, as received.
- relevant_facts
- What your records show: grades, dates, assignments, what you observed and what you have already done.
- school_policy
- Any policy that applies, such as late work or retakes. Write "none" if none applies.
- what_i_can_offer
- Next steps you can offer, for example "a phone call this week after 3:30 pm" or "a retake on Tuesday".
unit-plan — Plan a unit across several weeks
You need lessons sequenced toward the end goal with assessments along the way.
- unit_topic
- What the unit covers, for example "ratios and proportional reasoning".
- learners
- Grade or age and subject, for example "6th grade math".
- unit_length
- How long the unit runs, for example "four weeks, five 50-minute lessons a week".
- end_goal
- What students should know and do by the end, and any standards that apply.
- final_assessment
- The test, project or task at the end, or "not decided".
- resources
- Textbooks, materials, technology and anything else available.
- calendar
- Days with no lesson or a shortened lesson, or "none".
feedback-on-student-writing — Give feedback on student writing against a rubric
You need specific, encouraging feedback tied to rubric criteria for a piece of student work.
- learners
- The student's grade or level, for example "9th grade English".
- assignment
- The assignment as students received it.
- rubric
- The rubric with its criteria and level descriptions.
- teacher_notes
- What you noticed or want the feedback to focus on. Write "none" if you have nothing to add.
- student_work
- The student's writing, with their name removed.
substitute-teacher-plans — Write plans for a substitute teacher
You need a day's plans a substitute can follow without you there.
- date
- The day or days the substitute covers.
- schedule
- Each period or block with its time, class and room.
- lesson_content
- What each class should do, and where the materials, copies and answer keys are.
- routines
- How you take attendance, handle passes and devices, and dismiss students.
- student_support
- Only what the substitute must act on, such as medical plans or seating needs, with first names. Write "none" if there is nothing.
- emergency_info
- Emergency procedures, the nearest teacher to ask, and how to reach the office.
course-outline-from-materials — Turn your materials into a course outline
You need modules, objectives and sessions organized from the content you already have.
- audience
- Who the course is for and what they already know.
- course_format
- How the course runs, for example "six weekly 2-hour sessions online" or "a two-day workshop".
- course_goal
- What learners should be able to do afterward, for example "build and maintain a monthly sales dashboard".
- materials
- Your slides, documents and notes, or their titles and contents lists.
- constraints
- Must-cover topics, prerequisites or other limits. Write "none" if there are none.
discussion-questions — Write discussion questions for a class or workshop
You need questions that move from recall to real discussion on a reading or topic.
- participants
- Who will discuss, for example "a 10th grade English class" or "a team of 12 new managers".
- session_length
- How long the discussion lasts, for example 40 minutes.
- discussion_goal
- What you want the discussion to achieve, for example "to weigh the author's argument against their own experience".
- material
- The reading, an excerpt, or a short description of the topic.
one-page-job-aid — Make a one-page job aid or quick-reference card
You need a single page people can keep beside them while doing a task at work.
- users
- Who uses it and where, for example "warehouse staff at the packing bench".
- task_name
- The task, phrased as an action, for example "process a customer return".
- source_procedure
- The procedure, standard operating procedure or your own notes on the steps.
- common_mistakes
- Errors people make with this task. Write "none" if you do not know of any.
- format_details
- How the page will be used, for example "printed on letter paper and laminated" or "pinned on a second screen".
- help_contact
- Who to ask, for example "the shift lead" or a help channel.
thirteen-week-cash-flow — Build a simple 13-week cash flow forecast
You need to see whether cash covers bills and payroll over the coming weeks.
- opening_cash
- Cash in the bank at the start of week 1, with the date of that balance and the currency.
- start_date
- The first day of week 1, for example "Monday, November 2".
- minimum_cash
- The lowest balance you are comfortable holding, as an amount, for example the cost of two weeks of payroll.
- receivables
- Money owed to you: customer, amount, due date, and how many days late each customer usually pays.
- payables
- Bills and supplier invoices to pay: supplier, amount and due date.
- regular_payments
- Payroll with pay dates, rent, loan repayments, subscriptions and scheduled tax payments, with amounts.
- one_offs
- Expected one-off receipts or payments, such as an equipment purchase or a tax refund. Write "none" if there are none.
- audience
- Who will use the forecast, for example "me and my business partner" or "our finance manager".
expense-report-from-receipts — Prepare an expense report from receipts
You need receipts sorted into categories, totals and notes that match your expense policy.
- policy
- Your expense policy, or at least its categories, spending limits and receipt rules.
- receipts
- The receipt text, or attach the photos and list them here. Mark which were paid on a company card, and remove full card numbers.
- purpose
- The trip or reason for the expenses, for example "client visit, May 4 to 6".
- home_currency
- The currency you are reimbursed in.
- exchange_rates
- The rates to use, from your card statement or the rate your policy names. Write "none" if every receipt is in your currency.
- approver
- Who approves the report, for example "my manager".
department-or-project-budget — Build a budget for a project or department
You need cost lines, assumptions and a contingency for a budget you have to submit.
- what_it_funds
- What the project or department will do in the period: the scope, people and activities the budget must cover.
- cost_inputs
- Every cost figure you have: salaries or day rates, quotes, license prices, quantities, with where each came from.
- last_year
- Last year's actual spend or a previous budget, by line. Write "none" for a new project.
- budget_format
- The categories or template finance asks for, or "none".
- period
- The budget period and how to split it, for example "fiscal year 2027, by quarter".
- contingency_rule
- How your organization sets contingency, for example "10 percent of non-salary costs", or "none".
- budget_name
- The project or department, for example "the customer portal rebuild".
- approver
- Who approves the budget, for example "the finance director".
find-reconciliation-differences — Find why two reports do not reconcile
You need likely causes and checks when a bank statement and ledger, or two reports, do not match.
- report_a
- The first report's lines for the period, for example the bank statement, pasted as text or CSV.
- report_b
- The second report's lines for the same period, for example the cash account in your ledger.
- period
- The period being reconciled, for example "September 1 to 30".
- report_a_name
- What the first report is, for example "bank statement, operating account".
- report_b_name
- What the second report is, for example "general ledger, cash account".
- balances
- The ending balance each report shows, with the currency.
- known_items
- Differences you already know about, such as checks not yet cashed. Write "none" if there are none.
- reviewer
- Who signs off the reconciliation, for example "our controller".
invoice-with-payment-terms — Write an invoice and payment terms from work done
You need a clear invoice description, line items and payment terms that reduce late payment.
- my_business
- Your business name and address, and any tax registration number your accountant says to show.
- customer
- The customer's legal name, billing address, billing contact and purchase order number, if any.
- invoice_number
- Your next invoice number.
- invoice_date
- The date of the invoice.
- tax_info
- The tax rate to apply and its name, as your accountant set it, or "none".
- payment_methods
- How the customer can pay, for example bank transfer or a payment link. You can add account numbers yourself afterward.
- agreed_terms
- The quote, contract or email that set the rates and payment terms, including any late fee clause.
- work_done
- What you delivered, with dates and hours or quantities.
month-end-close-checklist — Build a month-end close checklist
You need close tasks in order with owners, deadlines and review steps.
- business_context
- Your size, number of entities, accounting system and anything unusual, for example "one entity, QuickBooks Online, inventory held".
- close_target
- When the books should be closed, for example "within 5 business days of month end".
- team
- The people who take part in the close, with their roles and any days they are not available.
- current_tasks
- Everything you do at month end now, as a rough list or notes.
- known_problems
- What runs late or goes wrong, for example "supplier invoices arrive after Day 3". Write "none" if nothing does.
accounting-treatment-explainer — Explain an accounting entry or treatment in plain terms
You need to understand or explain how a transaction is recorded and why, before checking with your accountant.
- transaction
- What happened, with amounts, dates and any contract terms, for example a prepaid annual license or a customer deposit.
- current_entry
- How it has been recorded so far, if you know, or "not recorded yet".
- framework
- The rules your books follow, for example US GAAP, IFRS, a local standard, cash basis, or "not sure".
- question
- What you want to understand, for example "why isn't the full payment an expense this month?"
- reader
- Who the explanation is for, for example "me, a founder without accounting training" or "a department head".
revenue-forecast-assumptions — Set out the assumptions behind a revenue forecast
You need drivers, assumptions and scenarios for a simple forecast in a spreadsheet.
- business_model
- How you earn revenue, for example "monthly subscriptions in three plans" or "project fees from about 20 clients a year".
- history
- Past revenue by month, with any drivers you track, such as customers, orders, prices or leads. Two years is ideal.
- known_future
- What you already know about the forecast period: signed contracts, pipeline, planned price changes, customers leaving. Write "none" if nothing.
- horizon
- The period to forecast, for example "the next 12 months, by month".
- forecast_use
- What the forecast is for, for example "next year's budget" or "a bank loan application".
- spreadsheet_app
- Where you will build it, for example Excel or Google Sheets.
audit-request-response — Organize responses to an auditor's request list
You need each audit request matched to an owner, a document and a due date.
- request_list
- The auditor's request list (often called a PBC list), copied exactly with their numbering.
- team
- The people who can supply documents, with what each one handles, for example "payables and supplier contracts".
- audit_type
- For example "annual financial statement audit for 2026" or "sales tax audit, last three years".
- deadline
- The auditor's due date and any fieldwork dates.
- systems
- Where records are kept, for example your accounting system, payroll provider and shared drive.
- known_gaps
- Anything you already know is missing or late. Write "none" if nothing.
- coordinator
- Who manages the audit on your side, for example "me" or "our controller".
tax-documents-checklist — Prepare a tax document checklist for your accountant
You need a list of documents, figures and questions to gather before tax season.
- return_type
- Whose taxes and which year, for example "our household, 2026" or "my sole proprietorship, 2026".
- jurisdiction
- The country and state or province you file in.
- situation
- Your income sources, business activity, property, investments and any changes this year, such as a move, a new job or a sale. Leave out ID and account numbers.
- last_year
- Last year's checklist or a list of what you sent. Write "none" if this is the first year.
- accountant_requests
- Anything your accountant has already asked for, such as their organizer or an email, with the deadline. Write "none" if nothing yet.
analyze-spreadsheet-findings — Analyze a spreadsheet and explain what it shows
You need trends, outliers and the main takeaways from a spreadsheet in plain language.
- data
- The spreadsheet data with its header row, pasted as text or CSV, or attach the file. Remove names and contact details first.
- column_notes
- What each column means, its units, and anything odd, such as total rows or amounts in thousands.
- question
- What you want to find out, for example "which products are growing and which are slipping this year".
- audience
- Who will read the findings, for example "my manager" or "the weekly operations meeting".
spreadsheet-macro-from-description — Write a spreadsheet macro or script from a plain description
You need repeated Excel or Google Sheets steps automated with a VBA macro or Apps Script.
- app_and_version
- For example "Excel for Microsoft 365 on Windows", "Excel 2019 on Mac", "Excel on the web" or "Google Sheets".
- how_to_run
- How you want to start it, for example "from a button on the Summary sheet", "from a custom menu" or "every Monday at 8 a.m.".
- manual_steps
- Each step you do by hand now, in order, as you would explain it to a colleague.
- sheet_layout
- Sheet names, column headers and what each holds, the header row, and how many rows there usually are.
- sample_rows
- Five to ten rows copied from the sheet, with personal data removed.
table-from-pdf-or-email — Pull a table out of a PDF, scan or email
You need figures trapped in a document turned into a clean table you can paste into a spreadsheet.
- source
- The PDF, scan, photo or email. Attach the file or paste the text, including the rows above and below the table.
- which_table
- Which table you need, for example "the price list on page 3" or "the second table in the email".
- columns_wanted
- The columns you want, in order, or "all, as in the document".
- number_format
- For example "plain numbers, dot for decimals, minus sign for negatives, no currency symbols".
- purpose
- What you will do with the table, for example "compare it with last month's prices in Excel".
recurring-report-template — Set up a recurring weekly or monthly report
You need a fixed report structure that you refill with new numbers each period.
- report_purpose
- Who reads it and what they decide with it, for example "store managers, to plan next week's staffing".
- frequency
- Weekly or monthly, and when it goes out, for example "every Monday by 10 a.m.".
- tool
- Where you will build it, for example Excel, Google Sheets, or a spreadsheet plus a slide.
- metrics
- The numbers you report now or want to, with the system or file each comes from and any targets.
- sample_data
- The column headers of the data you refill from, and five to ten sample rows with personal data removed.
- current_report
- The last report as text, or a description of it. Write "none" if this is a new report.
pivot-table-from-raw-data — Summarize raw data with a pivot table
You need the right rows, columns and values for a pivot table that answers your question.
- question
- What the pivot table should answer, for example "total sales and order count by region and month this year".
- app_and_version
- For example "Excel for Microsoft 365 on Windows", "Excel for Mac" or "Google Sheets".
- row_count
- Roughly how many rows of data, for example "about 8,000".
- audience
- Who the summary is for, for example "my team" or "the monthly sales review".
- columns
- Each column header with what it holds and its format, for example "Order date: dates, one per order".
- sample_rows
- Five to ten rows copied from the sheet, including any messy ones, with personal data removed.
dashboard-plan — Plan a dashboard before you build it
You need the questions it answers, the metrics, charts and filters agreed before building.
- audience_and_decisions
- Who will use the dashboard, how often they will look at it, and what they decide with it.
- data_sources
- Each data source with its column headers, a few sample rows and how often it updates. Remove personal data.
- current_reporting
- The reports, spreadsheets or recurring questions the dashboard should replace. Write "none" if there are none.
- tool
- For example Power BI, Tableau, Looker Studio or Excel.
spot-data-errors-and-anomalies — Find errors and anomalies in a dataset
You need duplicates, outliers and suspicious values flagged before you trust the numbers.
- data
- The dataset with its header row, pasted as text or CSV, or attach the file. Remove personal data you do not need checked.
- column_rules
- For each column: what it should hold, allowed values or range, and whether it must be unique or never blank.
- data_source
- Where the data came from, for example "a CRM export" or "a form merged from two spreadsheets".
- intended_use
- What you will use it for, for example "the quarterly sales report to the board".
- app_and_version
- Where you will check the full file, for example Excel for Microsoft 365, Google Sheets or Power Query.
explain-inherited-spreadsheet — Explain how an inherited spreadsheet works
You need to understand a colleague's workbook, its formulas and its flow before you change it.
- workbook_purpose
- What the file is for, as far as you know, for example "monthly commission calculation".
- app_and_version
- For example "Excel for Microsoft 365 on Windows" or "Google Sheets".
- change_planned
- What you need to change or keep running, for example "add a new region" or "just keep it working each month".
- sheet_list
- Each sheet's name, its column headers and what it seems to hold, including hidden sheets.
- formulas
- The key formulas copied with their sheet and cell. In Excel or Google Sheets, turn on Show formulas to see them all.
- extras
- Named ranges, links to other files, macros, pivot tables or data validation you found, or "not checked".
kpi-definitions — Define the KPIs your team will track
You need each metric defined with a formula, data source, owner and target so everyone counts the same way.
- team_and_goals
- The team, what it is responsible for and its goals for the period.
- candidate_metrics
- The metrics you track or are considering, with how each is calculated today and any disagreements about it.
- data_available
- The systems or files the numbers come from, their column names and a few sample rows with personal data removed.
- targets
- Targets already agreed, with the metric each belongs to, or "none yet".
- readers
- Who else relies on these numbers, for example "leadership and the finance team".
sales-data-breakdown — Break down sales data by product, region and rep
You need sales performance sliced and explained so you know what is driving the numbers.
- data
- The sales rows with a header row, at least date, product, region, rep and amount, pasted as CSV or attached.
- column_notes
- What each column means: gross or net of discounts and returns, the currency, and whether the date is order, invoice or payment date.
- periods
- The two periods to compare, for example "Q3 this year against Q3 last year".
- targets
- Targets or quotas by rep, region or product, or "none".
- known_events
- Anything that happened in the period that could affect sales. Write "none known" if nothing.
- audience
- Who will read the breakdown, for example "the sales director" or "the regional managers' meeting".
contract-key-terms-table — Pull a contract's key terms and dates into a table
You need parties, term, renewal, termination, payment, liability and notice dates in one place.
- contract_text
- The full contract, or the sections you need, copied exactly with clause numbers. Include schedules and amendments if you have them.
- our_role
- Your side, for example customer, supplier or landlord.
- start_date
- The signing or start date, or "unknown".
- audience
- Who will use the table, for example "the account team and finance".
nda-quick-check — Check an NDA before you sign it (not legal advice)
You need unusual or one-sided terms in an NDA flagged so you know what to ask about.
- nda_text
- The whole NDA, copied exactly with clause numbers.
- my_side
- Whether you mainly share information, receive it, or both, and your role, for example "freelance designer receiving a client's plans".
- purpose_of_sharing
- Why information is changing hands, for example "exploring a possible partnership".
- expectations
- What you assumed the NDA would say, for example "mutual, two years, nothing about hiring". Write "none" if you had no expectation.
compare-contract-versions — Compare two versions of a contract
You need to see what changed between drafts and which changes matter.
- earlier_version
- The earlier draft, copied exactly with clause numbers.
- later_version
- The later draft, copied exactly with clause numbers. Use the clean text, not only the redline.
- our_side
- Your side of the contract, for example customer or supplier.
- changed_by
- Who edited the later draft, for example "the supplier's lawyer" or "our team".
- priorities
- What matters most to you in this deal, for example "price protection, the right to leave early, data use".
- reviewer
- Who will review the changes, for example "our general counsel".
regulation-summary-for-team — Summarize a regulation for your team
You need what a law or rule requires of your team in plain terms, with questions to check with counsel.
- regulation_text
- The text of the law, regulation or rule, or the parts you need, copied with section numbers and definitions.
- source_details
- Where the text comes from and its version or date, for example "official text, as amended to January 2026".
- team_description
- What your team does, in a sentence or two, for example "we run online checkout for a retailer".
- reason
- What prompted this, for example "a customer asked if we follow it".
- audience
- Who will read the summary, for example "the customer support leads".
compliance-checklist-from-rule — Turn a regulation or standard into a compliance checklist
You need each requirement as a checklist item with the evidence you would show an auditor.
- rule_text
- The regulation or standard, or the parts you need, copied with section numbers.
- source_details
- Its name, version and date, for example "internal security standard, version 3, March 2026".
- scope
- Which sections or parts apply to you, if decided, or "not decided".
- process_description
- The team or process the checklist is for, in a sentence or two.
- existing_evidence
- Records, logs, policies and tools you already keep, one per line, or "none listed".
- owner
- Who will run the checklist, for example "the quality manager".
ai-acceptable-use-policy — Draft an AI acceptable-use policy for staff
You need clear rules on which AI tools staff can use, for what, and with what data.
- organization
- Your organization's name and what it does, in a few words.
- audience
- Who the policy covers, for example "all employees and contractors".
- policy_owner
- Who owns the policy, for example "the head of IT".
- approved_tools
- The AI tools you allow, with the account type for each, for example the company's business plan rather than personal accounts.
- data_rules
- Which kinds of information may and may not go into each tool, as you have decided them.
- encouraged_uses
- Work you want people to use AI for, such as first drafts or summarizing long documents.
- prohibited_uses
- Uses you do not allow, such as decisions about individual employees or customers.
- approval_process
- How someone asks to use a new tool and who says yes.
- existing_policies
- Sections of related policies (information security, data handling, acceptable use of IT) with their section numbers, or "none".
brief-for-your-lawyer — Brief your lawyer on a question
You need facts, documents and the exact question organized so counsel can answer quickly.
- lawyer
- Who will read it, for example "our outside employment lawyer".
- question
- What you want to know, as you would ask it.
- desired_outcome
- What a good result looks like for you, for example "end the lease early without paying the full balance".
- deadlines
- Any dates you know of, such as a reply date in a letter, or "none known".
- jurisdiction
- Country or state, or "unknown".
- facts
- What happened, in your own words, with dates where you have them. Leave out anything you are not allowed to share with an AI tool.
- documents
- Excerpts from contracts, letters or emails that matter, each with its title, date and clause numbers.
data-access-request-reply — Reply to a personal data access or deletion request
You need a response that acknowledges a privacy request, sets the timeline and asks for what you need.
- sender
- Who signs the reply, with their role, for example "the privacy team".
- organization
- Your organization's name.
- request_type
- What they asked for, for example "send a copy of their personal data" or "delete their account data".
- date_received
- The date the request arrived.
- request_text
- The request exactly as received, by email, form or letter.
- procedure
- Your internal procedure or privacy policy section for these requests, with section numbers.
- deadline
- The reply date your procedure or counsel sets, as a date, for example "by June 30".
- verification
- What you need to confirm identity, as your procedure lists it, for example "reply from the email address on the account".
- reference
- Your case or ticket number, or "none".
policy-gap-check — Check an internal policy against a new requirement
You need to see where your current policy falls short of a new rule or customer requirement.
- requirement_text
- The new rule, standard or customer requirement, copied with its section numbers.
- policy_text
- Your current policy, copied with its section numbers.
- requirement_source
- Where it comes from, for example "a new regulation" or "a customer's security questionnaire".
- due_date
- When the policy needs to be updated, or "not set".
- policy_owner
- Who owns the policy, for example "the compliance manager".
supplier-rfp — Write a request for proposal to send to suppliers
You need requirements, evaluation criteria and a timeline that suppliers can respond to.
- need
- What you are buying, for example "office cleaning for three sites".
- background
- A few sentences about your organization and why you are looking now.
- requirements
- What you need, one per line, each marked must-have or nice-to-have.
- volumes
- Quantities, sites, hours or service levels, as far as you know them.
- evaluation_criteria
- How you will choose, for example "price 40%, quality 30%, service 30%".
- timeline
- The dates for issuing, questions, responses, decision and start.
- budget
- A figure or range to share, or "do not share".
- contact
- The name or inbox suppliers should send questions and responses to.
- terms
- Any terms procurement or legal want included, such as confidentiality or contract terms, or "none provided".
process-improvement-review — Find delays and waste in a process
You need the bottlenecks, handoffs and rework in a process and practical fixes.
- audience
- Who will act on the review, for example "the finance operations team and its manager".
- process_name
- The process's name, for example "supplier invoice approval".
- output_and_customer
- What the process delivers and who receives it.
- volume
- How often it runs or how many items go through, for example "about 400 invoices a month".
- process_steps
- Each step as it really happens today, with who does it and any times you know: notes, a transcript or a list.
- pain_points
- What people complain about: delays, errors, chasing, duplicate work.
- constraints
- What cannot change, such as a system you must keep or an approval a policy requires.
vet-new-supplier — Vet a new supplier before you sign
You need the questions, documents and red flags to check before you take on a supplier.
- decision_maker
- Who approves the supplier, for example "the operations director".
- purchase
- What you would buy and roughly how much you expect to spend per year.
- dependence
- For example "sole source for a key part" or "easy to replace within a week".
- access
- Whether they will see your data or your customers' data, handle money, or work on your sites.
- our_requirements
- Your organization's supplier rules, such as required insurance or certifications, or "none set".
- supplier_material
- Everything they have sent: quote, proposal, emails, and text from their website.
corrective-action-plan — Turn audit or inspection findings into a corrective action plan
You need each finding with a root cause, action, owner and deadline.
- plan_owner
- Who owns the plan, for example "the site quality lead".
- recipient
- Who receives it, for example "the certification body's lead auditor" or "the health inspector".
- findings
- The findings exactly as written in the report, with reference numbers.
- cause_notes
- What you and the team know so far about why each finding happened.
- owners
- The people or roles who could own actions, one per line.
- response_requirements
- The deadline for your response and any form or template the auditor asked you to use.
staff-shift-schedule — Draft a staff shift schedule from availability
You need a fair schedule that meets coverage needs from availability and rules you provide.
- period
- The dates the schedule covers, for example "the week of May 4".
- location
- The site, store or team.
- scheduler
- Who reviews and posts the schedule, for example "the store manager".
- coverage_needs
- Each shift with its times, the number of people needed and any skill required, such as a key holder or first aider.
- staff_availability
- Each person's availability, contracted hours and skills, one person per line.
- rules
- Your scheduling rules: maximum hours, minimum rest, breaks, consecutive days and anything else that must hold.
- preferences
- Requests such as time off or preferred shifts, or "none".
prior-authorization-letter — Draft a prior authorization or insurance appeal letter
You work in a medical office and need a payer letter built from the clinical facts and policy criteria provided.
- payer_criteria
- The payer's coverage policy or prior authorization criteria for this item, copied with section numbers.
- clinical_facts
- The relevant facts from the chart, with dates and sources: diagnoses, history, prior treatments and results. Use only a tool your organization approves for patient information.
- denial_letter
- The payer's denial letter in full, or "none" for a first request.
- letter_type
- "Prior authorization request" or "appeal of a denial".
- payer
- The insurance company and plan name.
- patient_details
- Name, date of birth, member ID and any payer reference numbers.
- requested_service
- The service, drug or device, with the codes your clinician or coder supplied.
- clinician
- The signing clinician's name, credentials and practice details.
inventory-reorder-plan — Plan reorders from stock and sales numbers
You need reorder quantities and timing from current stock, sales pace and supplier lead times.
- audience
- Who places the orders, for example "the purchasing assistant".
- stock_data
- One line per item: name or SKU, current stock, units sold in the period, units on order, and days out of stock if known. A pasted spreadsheet works.
- sales_period
- The dates or number of days the sales figures cover, for example "last 90 days".
- supplier_terms
- For each supplier or item: lead time in days, minimum order quantity and pack or case size.
- safety_stock
- The buffer you want, in units or days of sales, for example "7 days of sales for every item".
- coverage_weeks
- How many weeks of sales each order should cover, for example "6".
- known_changes
- Promotions, seasonal peaks or items being dropped, with figures if you have them, or "none".
- today
- Today's date.
shift-handover-report — Write a shift handover report
You need the next shift to know what happened, what is open and what to watch.
- incoming
- Who takes over, for example "the night supervisor".
- location
- The site, unit or line.
- shift_details
- Date, shift times and who was on, for example "Tuesday day shift, 06:00 to 14:00, four on the floor".
- shift_notes
- Your notes, log entries and messages from the shift, in any order.
- open_items
- Anything you know is unfinished, or "see notes".
safety-briefing — Write a short safety briefing for frontline staff
You need a five-minute safety talk on one hazard with clear do's and don'ts.
- hazard
- The one hazard to cover, for example "forklifts in pedestrian aisles".
- supervisor
- Who gives the briefing, for example "the shift supervisor".
- crew
- Who hears it, for example "warehouse pickers, some in their first month".
- hazard_facts
- What is true about this hazard at your site: where, when, and what has happened or could happen.
- site_rules
- Your site's rules and procedures for this hazard, including emergency steps and contacts, with their numbers or titles.
- incidents
- Recent incidents or near misses here, without names, or "none".
- ppe
- The protective equipment your rules require for this hazard, or "none required".
presentation-tough-questions-prep — Prepare for tough questions after a presentation
You are presenting to leadership, a client or a committee and want the hard questions, with short honest answers, ready beforehand.
- audience
- Who you are presenting to, for example "the leadership team" or "the client's procurement committee".
- ask
- What you want from them, for example "approval for a six-month pilot".
- presentation
- Your slides as text, your script, or a summary of what you will say.
- backup_facts
- Extra facts, figures and sources you could use in answers. Write "none" if you have none.
- audience_notes
- What you know about the audience: their priorities, worries and earlier objections.
meeting-request-busy-person — Ask a busy person for a meeting
You need time with someone senior or outside your team and want a short request that makes yes easy and gives them a way to say no.
- person
- Who you are writing to and their role, for example "our regional director" or "the head of IT at a partner company".
- relationship
- How they know you, for example "we met once at the spring offsite" or "they do not know me".
- reason
- Why you want to meet and the outcome you want, for example "to get her view on whether to renew the vendor contract before I recommend it".
- their_benefit
- What they get from the meeting, if anything, or "nothing obvious".
- meeting_format
- Length and form, for example "20 minutes, video call".
- times
- Two or three times you can do, with your time zone.
- sign_off
- How to sign it, for example your first name.
slide-deck-review-before-presenting — Review your slide deck before you present
Your deck is drafted and you want blunt, slide-by-slide notes on what to cut, fix or move before anyone sees it.
- deck_text
- The text of every slide in order, with slide numbers, plus your speaker notes if you have them. Most slide tools can export this.
- audience
- Who will see it, for example "the executive team" or "a client's buying committee".
- goal
- What you want them to decide or do after the presentation.
- time_slot
- How long you have, for example "20 minutes including questions".
- setting
- How it will be shown, for example "shared on a video call" or "sent ahead as a pre-read".
collect-information-from-group — Ask several people for the same information by a deadline
You need updates, figures or details from a group and want replies that come back complete, on time and in the same shape.
- recipients
- Who you are asking, for example "the six store managers" or "everyone presenting at the board meeting".
- information_needed
- What you need in a few words, for example "your Q2 headcount and open roles".
- deadline
- The date and time you need it by, with the weekday.
- end_use
- What you will build from the replies, for example "the quarterly report to the leadership team".
- reason
- Why it matters and what happens if it is late, in a sentence or two.
- items
- Each piece of information you need, one per line if you can, with the unit or period if it matters.
- how_to_reply
- Where replies go, for example "reply to this email" or "fill in the shared spreadsheet".
- contact
- Who to ask with questions, often you.
reusable-email-templates — Build reusable templates for emails you send often
You write the same kinds of email every week and want saved templates with clear blanks, in your own voice.
- my_role
- Your job, for example "office manager at a dental practice".
- recipients
- Who usually receives these emails, for example "patients and suppliers".
- situations
- The kinds of email you write repeatedly, one per line, for example "chasing a missing purchase order number".
- sample_emails
- Two or three real emails you sent, with names and private details removed.
- rules
- Policies or required wording the templates must follow, or "none".
webinar-run-of-show — Write a run of show for a webinar or all-hands meeting
You are hosting an online session with several speakers and need a minute-by-minute plan of who does what, with cues and backup plans.
- event
- What the session is, for example "our quarterly all-hands" or "a customer webinar on the spring release".
- date_time
- Date, start time and time zone.
- session_length
- Total length, for example "60 minutes".
- platform
- The platform and features you will use, for example "Zoom webinar with polls and Q&A, recorded".
- people
- Each person and their role, for example "Ana: host; Sam: demo; Lee: producer".
- segments
- What has to happen, in rough order, with any timings you already know.
meeting-times-across-time-zones — Find meeting times across time zones and draft the invite
You need to schedule a call for people in several countries and want fair time options and an invite that shows everyone's local time.
- meeting_length
- How long the meeting is, for example "45-minute".
- attendee_group
- Who the invite is for, for example "the regional sales leads".
- attendees
- Each attendee with their city or time zone and working hours, one per line. Initials are enough.
- date_range
- The dates the meeting could happen, for example "any weekday from March 23 to April 3".
- constraints
- Who must attend, times to avoid, and any preference such as rotating early starts. Write "none" if there are none.
- meeting_purpose
- What the meeting is for, in a sentence.
spoken-update-for-meeting — Turn your notes into a short spoken update for a meeting
You have to give an update out loud at a stand-up, team meeting or all-hands and want it to sound natural and finish on time.
- meeting
- Where you are speaking, for example "Monday stand-up" or "the monthly all-hands".
- listeners
- Who is listening, for example "my team and two other team leads".
- time_limit
- How long you have, for example "two minutes".
- notes
- Your notes, however rough: results, problems, changes, dates.
- ask
- What you need from the listeners, or "nothing".
correct-english-and-explain — Correct your English and see why each fix was made
English is not your first language and you want a draft corrected to sound natural, with short explanations so you make the same mistakes less often.
- first_language
- Your first language, for example "Portuguese". It helps explain patterns in the mistakes.
- text_and_reader
- What the text is and who reads it, for example "an email to a client in Canada".
- formality
- How formal it should be, for example "polite but friendly" or "formal".
- text
- Your text, as you wrote it.
- spelling
- "American" or "British".
clean-up-dictated-voice-note — Turn a dictated voice note into clean text
You talked your thoughts into a phone or transcription app and need the messy transcript turned into readable text that still says what you said.
- tool
- What you dictated into, for example "my phone's voice memo app".
- destination
- What the text will become, for example "an email to my team" or "notes for a report".
- reader
- Who will read it, for example "my manager" or "only me".
- transcript
- The transcript, exactly as the app produced it.
- terms
- Names and terms the app may have misheard, with correct spellings, or "none".
edit-to-house-style-guide — Edit a document to match your house style guide
Your organization has rules for spelling, capitals, numbers and terms, and you need a draft brought into line with every change listed for review.
- style_guide
- Your style rules, pasted in full or the sections that apply.
- document
- The document to edit.
- reviewer
- Who approves the edit, for example "the communications lead".
- publication
- Where it will appear, for example "a customer newsletter article".
inclusive-language-check — Check a draft for language that could exclude readers
Before a document goes to a wide audience, you want wording that could exclude, stereotype or lose some readers flagged, with plain alternatives you can accept or reject.
- document_type
- What the draft is, for example "a job ad", "an all-staff email" or "a product page".
- audience
- Who will read it, for example "customers in several countries" or "all employees".
- draft
- The text to review.
- our_guidelines
- Any inclusive language or style rules your organization uses, pasted or summarized, or "none".
alt-text-for-images — Write alt text for the images in a page or document
You are publishing a web page, newsletter or report and need short, useful descriptions of each image for people who use screen readers.
- where_published
- Where the images will appear, for example "our charity's annual report web page".
- page_topic
- What the page or document is about, in a sentence.
- image_context
- For each image, in order: its caption or the sentence next to it, and whether it is a link. Attach the images themselves to the chat.
conference-talk-proposal — Write a conference talk proposal
A conference has a call for speakers and you need a title, abstract and bio that fit its limits and show the program committee why your talk belongs.
- conference
- The conference name and year.
- call_for_speakers
- The call for speakers text: themes, audience, formats and limits.
- my_idea
- What you want to talk about and the real experience, results or examples behind it.
- about_me
- Your role, relevant experience and any past talks.
- talk_format
- The format and slot, for example "25-minute talk" or "60-minute workshop".
card-message-for-colleague — Write a message for a farewell, sympathy or celebration card
A colleague is leaving, grieving, retiring or celebrating and you want a few warm, sincere lines for the card or message.
- recipient
- Who the card is for, for example "Priya, our team's office manager".
- occasion
- The occasion, for example "her retirement after 22 years" or "the death of his father".
- relationship
- Who you are to them, for example "her manager for three years" or "a colleague from another team".
- memories
- Specific things you remember or appreciate about them. A few honest lines are enough.
- tone
- How you normally talk to them, for example "friendly but not jokey".
- length
- How long, for example "under 40 words, for a small card" or "up to 80 words, for a shared online card".
- signature
- How to sign it, for example your first name.
recommendation-letter — Write a recommendation letter for someone you know
A former employee, colleague or student asked you for a reference letter and you want it specific, honest and in your voice.
- candidate
- The person's name and how they should be referred to.
- opportunity
- What they are applying for, for example "a master's program in public health" or "a senior analyst role".
- my_role_and_relationship
- Your role and how you know them, for example "her manager at a logistics company for four years".
- reader
- Who reads the letter, for example "the admissions committee" or "the hiring manager".
- criteria
- What the opportunity looks for, from the job ad, program page or the candidate's request.
- evidence
- What you saw them do: projects, results, moments that stood out, with dates if you have them.
- limits
- Anything you do not want to say or could not observe, or "none".
- signature
- Your name, title and organization as they should appear.
customer-language-from-reviews — Find the words customers use in reviews and feedback
You want headlines and copy built from how customers actually describe their problem and your product, taken from reviews, surveys or support messages.
- feedback
- Reviews, survey answers or support messages, one per line and numbered if you can, with personal details removed.
- product
- What you sell, in a sentence.
- source
- Where the feedback comes from and roughly how many pieces, for example "212 app store reviews from 2025 and 2026".
- team
- Who will use the findings, for example "marketing team".
- copy_use
- What the copy is for, for example "the new homepage and two ad campaigns".
welcome-email-sequence — Write a welcome email sequence for new subscribers
People just joined your list and you want a short series of emails that delivers what you promised, introduces you and leads to a first purchase or action.
- business
- Your business or brand name.
- signup_source
- Where they signed up, for example "the checklist download on our blog" or "the form at our market stall".
- promise
- What they were promised, for example "a free planting calendar and one email a week".
- goal_action
- The one action you want, for example "book a first consultation" or "make a first order".
- facts
- Facts about your business and offer: products, prices, any welcome offer with its terms, links.
- voice_sample
- One email, post or page you wrote that sounds like you.
- number_of_emails
- How many emails, usually 3 to 5.
creator-collaboration-pitch — Invite a creator or influencer to work with you
You have found a creator whose audience fits your product and want a first message that is personal, clear about the offer and easy to answer.
- creator
- The creator's name or handle.
- platform
- Where they post, for example "Instagram", "TikTok" or "YouTube".
- brand
- Your brand or business name.
- creator_notes
- Specific posts or videos of theirs you have watched, and what you noticed about them and their audience.
- fit
- What you sell and why it suits their audience, in a sentence or two.
- offer
- What you are offering: free product, a fee, commission or a mix. Say if you would rather not name a budget yet.
- ask
- What you would like, for example "one video showing the product in a real morning routine".
creator-content-brief — Write a content brief for a creator or UGC video
A creator has agreed to make content for you and needs a one-page brief with the message, must-haves, rules and dates, while keeping their own style.
- creator
- The creator's name or handle.
- deliverables
- What they will make, for example "one 30-second vertical video and three stories".
- brand
- Your brand or business name.
- campaign_facts
- Product, offer, key message, link or discount code, dates, payment and usage rights, as agreed.
- approved_claims
- What may be said about the product, word for word if your claims were approved by legal or regulatory review.
- restrictions
- What the content must not do, for example "no before-and-after comparisons, no mention of competitors", or "none".
ai-search-page-review — Review a web page so AI search tools can quote it
You want a page more likely to be used and cited when people ask AI assistants and AI search about your topic, without stuffing it with keywords.
- audience
- Who the page is for, for example "small landlords comparing insurance".
- target_questions
- The questions people ask that this page should answer, one per line, in their words.
- page_text
- The page's text with its headings, copied from the live page.
- facts_available
- Facts you could add, each with its source, or "none".
keyword-list-topic-clusters — Group a keyword list into topic clusters and pages
You exported a list of search keywords and need them grouped by topic, with one page planned per group, so you write fewer, better pages.
- keyword_list
- Your keyword export, one keyword per line, with volume and any other columns your tool provides.
- business
- What your site offers, in a sentence or two.
- existing_pages
- Your current pages that could match, with titles and URLs, or "none".
- data_source
- Which tool the data came from and what each column means, for example "keyword tool export: keyword, monthly searches, difficulty" or "Search Console, last 3 months: query, clicks, impressions".
- team
- Who will use the plan, for example "our two-person content team".
lead-magnet-plan — Plan a lead magnet people will trade their email for
You want a free checklist, template or short guide that attracts the right people to your list, and need the idea, outline and sign-up copy.
- business
- Your business name and what it does, in a sentence.
- audience
- Who you want on your list, for example "owners of independent cafes".
- offer
- What you sell, in a sentence.
- customer_problems
- What customers struggle with, from conversations, emails, reviews or sales calls.
- expertise
- What you know well and any material you already have that could become the resource.
- constraints
- How much time, design help and which tools you have, for example "a weekend and a free design tool".
win-back-lapsed-customers — Win back customers who stopped buying
Some past customers have not bought in months and you want a short email series that brings some back without discounting by reflex.
- business
- Your business name.
- lapsed_period
- How long since they last bought, for example "six months".
- whats_new
- Real changes since they last bought: new products, improvements, fixed problems.
- known_reasons
- Why customers stop buying, as far as you know, with guesses marked as guesses.
- offer
- A win-back offer with its terms and end date, or "none".
- voice_sample
- One past email that sounds like you.
sms-promotional-messages — Write promotional text messages (SMS) that fit the limit
You send texts to customers who opted in and need short promotional messages with an opt-out line and nothing that reads like spam.
- business
- Your business name.
- audience
- Who receives the texts, for example "customers who bought from us in the last year".
- goal
- What you want, for example "bookings for the last two weeks of December".
- offer_facts
- The offer or news with its exact terms, dates and link.
- sender_name
- Your business name as it should start each message.
- char_limit
- Your limit, for example 160 for a single standard text. Check your texting provider's settings.
social-media-comment-replies — Reply to comments on your social media posts
Your posts get questions, praise, complaints and the odd troll, and you want replies in your brand voice that answer people and know when to move a conversation private.
- platform
- Where the comments are, for example "Instagram" or "Facebook".
- business
- Your business or brand name.
- facts
- Facts replies can use: opening hours, prices, policies, links, and how customers reach you privately.
- voice
- How you sound, for example "friendly and plain, first names, no corporate phrases".
- comments
- The comments, one per line, each with the post it was left on.
cold-call-opener-and-voicemail — Write a cold call opener and voicemail
You are calling prospects who do not know you and want the first 30 seconds, a few questions and a voicemail that sound like a person, not a script.
- prospect_role
- Who you are calling, for example "facilities managers".
- company_type
- The kind of company, for example "private schools with 300 to 1,000 students".
- offer
- What you sell, in a sentence.
- call_goal
- What success on the call is, for example "a 20-minute meeting next week".
- proof
- Problems you solve and results you can honestly name, with customer names only if you may use them.
- prospect_notes
- Anything specific you know about this prospect or account, or "nothing yet".
price-negotiation-prep — Prepare for a price negotiation with a buyer
A deal is near the end and the buyer will push on price or terms, and you want your limits, trades and responses worked out before the call.
- buyer
- Who you are negotiating with, for example "the procurement lead at a regional hospital group".
- deal
- What the deal is, in a few words.
- current_proposal
- The proposal as it stands: products, price, terms, length, start date.
- their_position
- What you know about their budget, deadlines, alternatives, decision makers and requests.
- approved_limits
- How far you can go, as approved, for example "up to 8 percent off for a two-year term; no free implementation".
- our_wants
- What you would value in return for a concession.
reply-to-discount-request — Reply when a buyer asks for a discount
A prospect has asked for a lower price and you want a reply that holds your value, offers a fair trade if one is approved, and keeps the deal moving.
- buyer
- Who asked, for example "the operations director at a client we have pitched twice".
- their_message
- Their message asking for a discount, exactly as received.
- proposal
- Your proposal's price, terms and scope.
- their_priorities
- What they told you matters most to them.
- approved_options
- What you are allowed to offer and what you would want in return, or "none".
mutual-action-plan — Build a mutual action plan with a buyer
A deal has several people and steps on the buyer's side, and you want a shared plan of who does what by when, from today to go-live.
- buyer_company
- The buyer's company name.
- buyer_contact
- Your main contact there and their role.
- target_outcome
- What the plan leads to, with its date, for example "live by April 1 for the new financial year".
- buying_process
- What you know about their process: approvals, legal, security review, procurement, budget timing.
- people
- Everyone involved on both sides, with their roles.
- key_dates
- Dates already agreed or fixed, or "none yet".
- current_status
- Where the deal stands today, in a sentence or two.
event-contact-follow-ups — Follow up with people you met at a trade show or event
You came back from an event with a stack of contacts and notes, and want follow-ups that mention each conversation instead of one blast to everyone.
- event
- The event name and where it was.
- my_role
- Your role and company.
- contacts
- One line per person: name, company, role, what you talked about, any agreed next step, and how interested they seemed.
- what_i_can_offer
- What you can send or arrange, for example "the setup guide, a 20-minute demo, an introduction to a customer in their sector".
- signature
- Your name and title as you sign emails.
ask-customer-for-referral — Ask a happy customer for a referral
A customer is getting real value from you and you want to ask, without awkwardness, whether they know someone else who would benefit.
- customer
- The customer's name, role and company.
- customer_history
- How long they have been a customer, what they bought, and the results they have had, in their words if you have them.
- about_us
- Your company name, what you do and how to reach you, in a sentence or two.
- ideal_referral
- Who you would like to be introduced to, for example "other practice managers at independent vet clinics".
- referral_terms
- Any referral reward with its terms, or "none".
- channel
- How you will ask, for example "email" or "LinkedIn message".
business-case-for-buyer-to-share — Write a business case your buyer can share internally
Your contact supports the purchase but must convince a boss or committee, and you want a short, forwardable case written in their terms, not your pitch.
- champion
- Your contact who supports the purchase, with their role.
- decision_maker
- Who approves it, for example "their CFO" or "the operations committee".
- offer
- What they would be buying, in a few words.
- discovery_notes
- What the buyer told you about the problem, its cost, what they tried and their goals.
- proposal
- Your proposal's price, terms, timeline and scope.
- evidence
- Results, references or published figures you are allowed to share, or "none".
sales-to-onboarding-handoff — Hand a closed deal over to onboarding
A deal just closed and the onboarding or customer success team needs everything you know, so the customer never has to repeat themselves.
- receiving_team
- Who takes over, for example "the onboarding team" or "Maria, the customer success manager".
- customer
- The customer's company name.
- sales_notes
- Your notes from the sales process: calls, emails, CRM entries, in any order.
- order
- What was sold, as in the signed order or contract: products, quantities, dates, terms.
demo-plan-from-discovery — Plan a product demo around the buyer's problems
You have a demo booked and want to show only what matters to this buyer, in their order of priority, instead of touring every feature.
- discovery_notes
- Your notes or transcript from discovery: their problems, goals, current process and who said what.
- product_capabilities
- What your product can actually do that might be relevant, with the screens or steps to show it.
- attendees
- Who will attend and their roles, for example "ops lead, finance manager, IT admin".
- demo_length
- How long the demo is, for example "45 minutes".
prioritize-inbound-leads — Prioritize inbound leads against your qualification criteria
A batch of form fills, demo requests or inquiries came in and you want them sorted by fit and urgency, with a reason and a next step for each.
- company
- Your company name.
- sales_team
- Who will follow up, for example "our two account executives".
- criteria
- Your qualification criteria: who fits, what signals urgency, who you do not serve.
- leads
- The leads, one per line or as pasted from your form or CRM export, with what each person wrote.
animate-still-photo — Animate a still photo into a short clip
You have a real photo, such as a product, a place or a finished project, and want a few seconds of gentle motion for a post, slide or web page, from an image-to-video model.
- use_case
- Where the clip will be used, for example "the hero of our product page" or "a social post".
- subject
- The main thing in the photo, for example "the ceramic teapot on the table".
- motion
- What moves, concretely, for example "steam rises slowly from the spout and the curtain behind stirs slightly".
- camera_move
- One camera move, for example "a slow push-in" or "a static camera".
- duration_seconds
- A clip length your video model supports; check its settings.
- sound
- What we hear, for example "quiet kitchen ambience, no music". Write "silence" if the clip will play muted.
presenter-speaking-clip — Short clip of a presenter speaking your script
You need a few seconds of a fictional presenter saying one line to camera, for an explainer, announcement or course intro, from a video model that generates speech.
- presenter
- A fictional presenter, described concretely, for example "a woman in her forties with short gray hair, wearing a navy sweater". Do not describe a real, recognizable person.
- setting
- Where they stand, for example "a bright, tidy office with plants and a window behind".
- use_case
- What the clip is for, for example "the opening of a training course". Do not use it as, or present it as, a customer testimonial.
- voice
- How the voice sounds, for example "warm, mid-range, American English".
- line
- The exact words, one or two short sentences. Allow about two words per second, so an 8-second clip holds about 15 words and a short pause.
- duration_seconds
- A clip length your video model supports; check its settings.
- aspect_ratio
- 16:9 for a web page or slide, 9:16 for vertical social video.
virtual-staging-empty-room — Virtually stage a photo of an empty room
You have a photo of an empty room for a listing or rental ad and want it shown furnished, with the room itself left exactly as it is.
- room_type
- The room, for example "living room" or "main bedroom".
- use_case
- Where it will be used, for example "an online listing for an apartment for sale". Most listing services require staged photos to be labeled as virtually staged and the original photo to be shown too; check your local rules.
- furniture
- What to add, concretely, for example "a three-seat sofa, a low oak coffee table, a wool rug and a floor lamp".
- style
- The style, for example "warm modern" or "Scandinavian".
- palette
- Colors for the furniture and decor, for example "cream, oak and sage green".
- light_source
- Where the light comes from in your photo, for example "the large window on the left".
matching-illustration-set-midjourney — A set of matching illustrations for slides or a website
You need several illustrations that look like one family, for a deck, a web page or a report, from Midjourney.
- subject
- What this illustration shows, concretely, for example "a hand dropping a paper envelope into a mailbox". Change only this for each image in the set.
- use_case
- Where the set will be used, in a few words, for example "a company website" or "an annual report". Midjourney may draw what you name, so name the setting, not its content.
- palette
- Three or four colors, for example "deep navy, cream and coral". Keep it the same for every image.
- background
- The background color, for example "warm off-white".
- aspect_ratio
- The shape in whole numbers, for example 1:1 for icons or 4:3 for slide images.
- style_reference
- The URL of the first illustration you liked from this series, so the rest match it. For the very first image, delete --sref and this value.
new-manager-first-90-days — Plan your first 90 days as a new manager
You have just taken over a team, by promotion or a new job, and need a listening-first plan for your first three months.
- team_description
- The team you now manage: size, roles and what it does, for example "a six-person accounts payable team".
- my_manager
- Who you report to, for example "my director, Sam".
- how_i_arrived
- Promoted from within the team, moved from another team, or hired from outside.
- manager_expectations
- What your manager has asked for in the first months, in their words if you can. Write "not discussed yet" if nothing.
- what_i_know
- What you know about the team, its work, its results and its problems, and how you know it. Rough notes are fine.
team-request-triage — Triage your team's incoming requests against its capacity
Your team has more requests than people, and you need a ranked list plus honest replies to the people who will have to wait.
- decision_maker
- Who sets priorities with you, for example "my director" or "the operations leadership team".
- team_capacity
- People and time available, for example "four analysts, about 30 working days free over the next six weeks".
- priorities
- Your team's agreed priorities or goals for this period, most important first.
- requests
- Each waiting request: who asked, what they want, any deadline, and your rough effort estimate in days or hours.
career-development-conversation — Prepare a career development conversation with a direct report
You want to help someone on your team work out where they want to grow and agree on steps for the next six to twelve months.
- report_role
- The person's role and how long they have been in it, for example "a customer support specialist, two years in the role".
- what_i_know
- Their strengths, the work they enjoy, feedback they have had and anything they have mentioned about the future.
- their_stated_goals
- What they have told you about their goals. Write "nothing yet" if they have not said.
- opportunities
- What you can really offer: projects, stretch work, training budget, mentors, shadowing.
- meeting_length
- For example "45 minutes".
skip-level-meeting-prep — Prepare a skip-level meeting with people two levels below you
You manage managers and want honest, useful conversations with the people on their teams without going around them.
- attendees
- Who you are meeting, for example "the five analysts on the reporting team".
- their_manager
- Their manager's role or name, for example "the reporting team lead".
- format
- Group or one-on-one, and how long, for example "group, 45 minutes".
- reason
- Why now, for example "regular quarterly skip-levels" or "two resignations this quarter".
- context
- What you know about the team's work and anything you want to understand better.
- hr_contact
- Who handles formal concerns, for example "our HR business partner".
calibration-meeting-prep — Prepare your team's ratings for a calibration meeting
You have proposed performance ratings for your team and need evidence for each, plus a check for bias, before calibration.
- calibration_group
- Who calibrates with you, for example "the other operations managers and our director".
- rating_scale
- Your company's rating levels and their definitions, copied from the review guide.
- team_evidence
- One entry per person: role, level, proposed rating and your evidence with dates. Use initials if your company's AI policy asks for it.
role-expectations-document — Write clear expectations for someone's role on your team
Someone on your team needs to know in writing what good looks like in their role, before problems or a review.
- role_title
- The job title, for example "customer success associate".
- person_context
- Who it is for, for example "a new hire starting next month" or "an experienced analyst whose role has changed".
- role_description
- The job description or a summary of what the role covers.
- my_notes
- What good work looks like to you in this role. Rough notes are fine.
- team_norms
- Norms that apply to the whole team, for example "reply to internal messages within one working day".
employee-personal-issue-response — Respond when someone on your team shares a personal or health issue
Someone told you about an illness, bereavement, caregiving or another hard situation, and you want to respond well and know what comes next.
- what_they_shared
- What the person told you, as close to their words as you can, and how they told you. Leave out details they did not share.
- support_available
- Leave, flexible working, an employee assistance program or other support you know of. Write "not sure" if you do not know.
- work_context
- Their role and what is on their plate right now.
- hr_contact
- Who in HR to involve, for example "our HR business partner".
overloaded-team-member-check-in — Check in with someone on your team who seems overloaded
You have noticed signs that someone is stretched too thin and want to talk about their workload before it turns into burnout.
- report_role
- The person's role, for example "a senior bookkeeper".
- observations
- What you have seen yourself, with dates. Mark anything you heard from others.
- workload
- Their current projects, recurring work and deadlines.
- levers
- What you can actually change: deadlines you control, work you could move, help you could bring in.
- support_available
- For example an employee assistance program, flexible hours or HR. Write "not sure" if you do not know.
team-member-resignation-plan — Handle a resignation on your team: reply, announcement and cover
Someone on your team has resigned and you need to respond well, tell the team and make sure their work stays covered.
- role_and_reason
- Their role and, only if they told you and are happy to share, where they are going.
- last_day
- Their last working day.
- company_rules
- What you know about counteroffers, exit interviews and who announces departures. Write "not sure" if you do not know.
- their_work
- Their responsibilities, open projects, recurring tasks, key contacts and anything only they know.
- team_capacity
- Who else is on the team and how much room they have.
- my_manager
- Who you would discuss a counteroffer or backfill with.
reference-letter-for-former-employee — Write a reference for someone who worked for you
A current or former team member asked you for a reference, and you want it honest, specific and within company policy.
- person
- The person's name.
- their_role
- Their job title while working for you.
- dates
- When they worked for you, for example "March 2022 to August 2025".
- recipient
- Who will read it, for example "a hiring manager at another company" or "a graduate program admissions panel".
- company_policy
- Your company's rules on references. Write "not sure" if you do not know.
- my_notes
- What they did, results, strengths, examples and anything they asked you to mention.
- target_role
- The job or program they are applying for, or "not known".
- contact_line
- How the reader can reach you, for example "my email and mobile number".
hiring-debrief-from-feedback — Run a hiring debrief from the interview panel's feedback
The panel has interviewed a candidate and you need their feedback organized by criterion so the hiring manager can decide fairly.
- criteria
- The criteria or competencies on your scorecard, with the rating scale.
- panel_feedback
- Each interviewer's notes and ratings, labeled with their name or role.
- candidate_ref
- The candidate's initials or reference number.
- role
- The job title.
- hiring_manager
- Who makes the decision with the panel, for example "the finance director".
screen-applications-against-criteria — Screen applications against a role's must-have criteria
You have a pile of applications and want each checked against the same job-related criteria, with a person making every decision.
- role
- The job title.
- compliance_confirmed
- Write "yes" only if HR or legal has confirmed AI-assisted screening is allowed here and any required notice was given. Otherwise describe what you know.
- criteria
- The must-have criteria from the approved job description, one per line.
- applications
- The applications or resumes, each with a reference number. Remove names, contact details and photos first.
recruiter-intake-meeting — Prepare a recruiter intake meeting with a hiring manager
A new role has opened and you need the right questions for the hiring manager and a role brief you both agree on.
- hiring_manager
- The hiring manager's role or name, for example "the warehouse operations manager".
- what_i_have
- The job title, any draft description, the hiring manager's request and what you know about the team.
- pay_and_location
- The approved range and location rules, or "not approved yet".
- meeting_length
- For example "30 minutes".
boolean-search-string — Write a Boolean search string to find candidates
You need search strings for LinkedIn, a job board or your applicant system that find the right people without thousands of misses.
- role
- The job title.
- platform
- Where you will search, for example LinkedIn Recruiter, Indeed or your applicant tracking system.
- must_haves
- The skills, tools, qualifications and experience the person must have.
- nice_to_haves
- Skills that would help but are not required.
- titles
- Job titles people doing this work often have, or "not sure".
- location
- For example "within 30 miles of Denver" or "remote, US only".
- false_matches
- Words that bring in the wrong people, or "none known".
stay-interview-guide — Plan stay interviews with the people you want to keep
You want managers to ask valued employees what keeps them and what might push them out, and to act on the answers.
- who
- Which employees, for example "everyone in customer support with more than one year of service".
- interviewers
- Who will run them, for example "each person's direct manager".
- reason
- Why now, for example "turnover rose this year".
- what_we_can_change
- The levers you really have: budget, flexibility, training, workload, recognition.
- existing_data
- Themes from recent surveys or exit interviews, or "none".
- hr_contact
- Who handles formal complaints.
career-ladder-draft — Draft a career ladder for a job family
You need levels with clear expectations for one kind of role, so promotions and pay conversations rest on the same standards.
- job_family
- The kind of role, for example "customer support" or "finance and accounting".
- audience
- Who will review the draft, for example "HR and the two support team leads".
- levels
- How many levels and their titles, for example "four: Associate, Specialist, Senior Specialist, Lead".
- source_material
- Job descriptions, competency lists, notes on what good looks like, or an existing ladder to improve.
accommodation-request-response — Respond to an employee's request for a workplace accommodation
An employee asked for an adjustment because of a disability, health condition, pregnancy or religion, and you need a prompt, respectful first reply.
- my_role
- For example "HR generalist" or "the employee's manager".
- reviewer
- Who reviews legal and medical points, for example "our HR lead" or "employment counsel".
- request
- The employee's request in their words. Remove details they did not need to share.
- policy
- Your accommodation policy or process, or "none written".
- job_context
- Their role and the tasks or conditions the request affects.
candidate-offer-negotiation-reply — Reply to a candidate who wants to negotiate an offer
A candidate asked for more pay or different terms, and you need a reply that stays within what is approved and keeps them interested.
- role
- The job title.
- my_role
- For example "the recruiter" or "the hiring manager".
- current_offer
- The offer as made: base pay, bonus, start date, benefits, remote terms.
- candidate_request
- What the candidate asked for, in their words.
- approved_flexibility
- What you are allowed to change and by how much, for example "base up to the top of the range; no signing bonus".
- context
- Other offers they mentioned, start date, when you need an answer. Write "none" if nothing.
- approver
- Who can approve going further, for example "the head of talent".
workplace-investigation-plan — Plan a workplace investigation before the first interview
A complaint needs a formal look, and you need a scope, witnesses, questions and a timeline before anyone is interviewed.
- complaint
- The complaint as received, or your notes of it. Use roles or initials instead of names if you can.
- policies
- The policies the complaint may involve, for example your harassment or conduct policy.
- my_role
- For example "HR manager".
- people
- The complainant, respondent and possible witnesses, by role or initials.
- interim_measures
- Steps already taken, for example a schedule change, or "none".
- audience
- Who approves the plan, for example "the HR director and employment counsel".
explain-pay-decision-to-employee — Explain a pay or raise decision to an employee
An employee is getting a raise, no raise or less than they hoped, and you need to explain the decision clearly and honestly.
- who_tells_them
- Who will have the conversation, for example "me, their manager" or "their manager, with HR present".
- employee_role
- The employee's role, for example "a senior account manager".
- decision
- The approved decision, for example "a 2% increase from April 1" or "no increase this cycle".
- pay_process
- How pay decisions work at your organization, as far as you can share it.
- reasons
- The reasons for this decision, from the review or the approver.
- their_expectation
- What they expected or asked for, or "not known".
job-posting-fit-check — Check how well you fit a job posting before you apply
You want an honest read on which requirements you meet, which you do not, and whether the job is worth applying for.
- job_posting
- The full job posting, copied from the site.
- my_background
- Your resume, or a summary of your roles, skills and results.
- my_priorities
- What you need from the job and what would rule it out, for example "remote at least three days, salary above $70,000, no weekend shifts".
tell-me-about-yourself-answer — Write your answer to "Tell me about yourself"
You need a natural, short answer to the most common interview opener, built from your real experience and aimed at one job.
- target_role
- The job and company, for example "operations coordinator at a regional food distributor".
- interviewer
- Who you expect to meet, for example "a recruiter" or "the hiring manager, a finance director".
- my_background
- Your resume or notes on your roles, results and skills.
- why_this_job
- Why you want this job, in your own words. A rough sentence is fine.
- to_explain
- A career change, gap or short job to mention briefly, or "none".
questions-to-ask-interviewer — Prepare questions to ask at the end of a job interview
You want thoughtful questions that help you judge the job and show you did your homework, instead of generic ones.
- role
- The job title and company.
- interviewer
- Their role, for example "the hiring manager" or "a future peer on the team".
- job_posting
- The full job posting.
- what_i_know
- What you have learned about the company and team so far.
- my_priorities
- What matters most to you, for example "growth into management, steady hours".
- stage
- For example "first interview" or "final round".
explain-gap-or-layoff — Explain a resume gap or a layoff with confidence
You were laid off or took time away from work and need honest, short wording for your resume, LinkedIn and interviews.
- target_roles
- The kind of jobs you are applying for.
- what_happened
- For example "laid off in a restructuring in May" or "eight months caring for a parent".
- comfort_level
- How much you want to say, for example "happy to say it was a layoff" or "prefer to keep it private".
- during_gap
- Anything you did in the time, or "mostly job searching".
- recent_roles
- Your last two or three roles with dates and a line on each.
reply-to-recruiter-message — Reply to a recruiter who contacted you
A recruiter reached out about a role and you want to show interest, ask the right questions, or decline without closing the door.
- my_answer
- Interested, not now, or not interested.
- recruiter_message
- The recruiter's message, copied in full.
- what_i_want
- Your pay floor, location or remote needs, the work you want and your timing.
- my_situation
- What you are happy to say about your current job, or "nothing".
- my_name
- Your name as you sign messages.
interview-thirty-sixty-ninety-plan — Write a 30-60-90 day plan to present in a job interview
An interviewer asked how you would approach your first three months, and you need a realistic plan built from what you know.
- role
- The job title and company.
- audience
- Who you will present to, for example "the hiring manager and two team leads".
- job_posting
- The full job posting.
- what_i_learned
- What you know from interviews, the website, annual reports or the brief for this task.
- my_experience
- The parts of your background that matter for this role.
- format
- What the interviewer asked for, for example "10-minute presentation" or "one-page document". Write "not specified" if they did not say.
ask-for-a-reference — Ask someone to be your reference and brief them
You need a former manager or colleague to give you a reference, and you want to ask well and remind them what to speak to.
- reference_person
- Their name and role, for example "Dana, my manager at my last job".
- target_role
- The job and company you applied to.
- relationship
- How you worked together and when you were last in touch.
- timing
- When and how the employer will contact them, for example "a phone call next week".
- job_highlights
- The main requirements of the job, copied or summarized from the posting.
- shared_work
- Projects or situations they saw you handle, with dates and results.
personal-development-plan — Write your own development plan for the next year
You want a realistic plan for the skills and experience you will build this year, to share with your manager or keep for yourself.
- time_frame
- For example "12 months" or "six months".
- reader
- Who will see the plan, for example "my manager" or "only me".
- where_i_am
- Your role, strengths, recent feedback and what you find hard.
- goal
- Where you want to be and why, for example "ready for a team lead role in a year".
- resources
- Hours a week, any budget, a mentor, projects you could join.
flexible-work-request — Ask your employer for flexible or remote work
You want to request remote days, different hours or another arrangement, with a proposal your manager can say yes to.
- manager
- Who you are asking, for example "my manager, Priya".
- arrangement
- What you want, for example "two remote days a week" or "a 7 to 3 schedule".
- role_details
- Your main tasks, meetings, and anything that needs you on site.
- policy
- Your company's policy on flexible or remote work, or "none that I know of".
- reason
- As much of your reason as you want to share, or "prefer not to say".
- track_record
- Results, reliability, or a time you worked remotely and it went well.
internal-job-application — Apply for an internal job or transfer
You want to move to another team or a bigger role inside your company, and need to tell your manager well and apply strongly.
- internal_role
- The job title you are applying for.
- other_team
- The team or department, for example "the finance operations team".
- posting
- The internal job posting.
- my_record
- Your current role, main results and anything that connects to the new role.
- mobility_rules
- Your company's internal transfer rules, or "not sure".
- manager_situation
- For example "supportive, we talk about my career" or "likely to be upset, the team is short-staffed".
weekly-job-search-plan — Build a weekly job search plan you can keep up
You are looking for work and want a realistic weekly routine with targets, so the search does not become endless applying.
- weeks
- For example "8" or "12".
- target_roles
- The jobs you want, for example "HR coordinator or recruiting coordinator roles in Chicago".
- situation
- For example "employed and searching quietly" or "laid off last month, severance until March".
- hours
- Realistic hours per week, for example "10".
- background
- A short summary of your experience and strengths.
- progress_so_far
- Applications sent, responses, interviews and contacts so far, or "just starting".
recruiter-screen-call-prep — Prepare for a recruiter screening call
A recruiter has booked a first call and you want ready answers on salary, why you are looking, timing and logistics.
- role
- The job title and company.
- posting
- The job posting or the recruiter's message.
- background
- A short summary of your experience.
- target_pay
- The range you are aiming for, or "not decided".
- availability
- For example "four weeks' notice" or "available now".
- location
- For example "hybrid in Austin" or "fully remote only".
- why_looking
- Your honest reason, for example "want to move from agency to in-house".
feature-request-reply — Reply to a customer's feature request you cannot promise
A customer asked for a feature that is not planned or not decided, and you need an honest reply that keeps them on side.
- customer_message
- The customer's message, as received.
- status
- Where the request stands, in the product team's words, or "unknown".
- workarounds
- Existing features or workarounds that help, or "none".
- tracking
- For example "logged in our feedback board; we email customers when a request ships".
- agent_name
- The name the reply is signed with.
troubleshooting-steps-reply — Walk a customer through troubleshooting at their level
A customer has a technical problem and you need clear steps matched to how comfortable they are with technology.
- customer_message
- The customer's message, including what they have already tried.
- known_steps
- Your documented troubleshooting steps for this issue.
- setup
- Device, browser, app version or plan, or "unknown".
ask-customer-for-details — Ask a customer for every detail you need in one message
You cannot solve a ticket without more information and want to ask for all of it at once, so it does not drag on for days.
- ticket
- The customer's message and any replies so far.
- info_needed
- What your team needs for this type of issue, for example "order number, photo of the damage, delivery address".
- already_known
- What you already have, so the reply does not ask again.
- agent_name
- The name the reply is signed with.
- verification_method
- How you check identity safely, for example "the secure verification link in your account".
renewal-conversation-prep — Prepare for a customer's renewal conversation
A contract is coming up for renewal and you need a brief on value delivered, risks and the questions to ask before you talk.
- customer
- The customer's company name.
- renewal_date
- When the contract ends.
- my_role
- For example "customer success manager" or "account manager".
- internal_audience
- Who else reads the brief, for example "my manager" or "the account executive".
- account_notes
- Goals, usage trends, support history, meeting notes, stakeholders and recent changes.
- commercial_facts
- Current plan and price, and any approved renewal terms.
- approver
- Who approves terms beyond what you can offer, for example "the head of customer success".
sales-to-success-handoff — Turn sales notes into a handoff for customer success
A deal has closed and the person taking over the account needs to know what was promised, why they bought and who is who.
- receiver
- Who takes over, for example "the onboarding specialist" or "our customer success manager".
- customer
- The customer's company name.
- sales_notes
- Call notes, emails, the proposal and anything the sales rep wrote down.
- terms
- The signed contract terms or order summary.
- sales_owner
- The salesperson who closed the deal.
abusive-customer-boundary-reply — Reply to an abusive customer and set a boundary
A customer is insulting or threatening staff, and you need a reply that stays calm, sets a clear limit and still offers help.
- customer_messages
- The abusive message and any earlier messages in the thread.
- abuse_policy
- Your policy on abusive or threatening customers, or "none".
- what_we_can_do
- What you can actually do about the problem underneath, for example "reship the order" or "escalate to billing".
low-satisfaction-score-follow-up — Follow up on a low satisfaction or NPS score
A customer gave a low rating in a survey and you want to find out what went wrong and fix it, not argue with the score.
- survey
- Which survey, for example "post-ticket satisfaction survey" or "quarterly NPS survey".
- score
- The score they gave, for example "2 out of 10".
- comment
- Their survey comment, word for word, or "none".
- records
- Recent tickets, orders or account notes for this customer.
- what_i_can_do
- What you can actually offer or fix, or "apology and follow-up only".
- sender_name
- The name the message is signed with.
- root_cause_team
- Who should fix the cause, for example "the billing team" or "the support team lead".
feature-retirement-notice — Tell customers a feature or product is being retired
You are removing a feature, plan or product and need a clear notice with dates, what changes and what customers should do.
- what_is_retiring
- The feature, plan or product, for example "the legacy reports page".
- facts
- The decided facts: dates, reasons, replacements, what happens to data and settings, and any migration steps.
- affected_customers
- Who is affected, for example "customers on the Classic plan who used legacy reports in the last 90 days".
- channel
- Where it will go, for example "email plus an in-app banner".
new-contact-after-champion-leaves — Rebuild an account after your main customer contact leaves
Your main contact at a customer has left, and you need to introduce yourself to their replacement and show what the account has achieved.
- customer
- The customer's company name.
- former_contact
- The person who left and their role.
- my_role
- For example "customer success manager".
- new_contact
- Their replacement's name and role, or "not known yet".
- change_details
- What you know about the change and when it happened.
- account_history
- Why they bought, goals, results, usage, open issues and renewal date.
call-to-ticket-notes — Turn a support call into clear ticket notes
You have just finished a customer call and need accurate notes on the ticket, so the next person can pick it up without asking again.
- note_reader
- Who reads the notes next, for example "the billing team" or "any agent on the queue".
- call_notes
- Your notes or the call transcript.
- note_format
- Your team's required fields, or "none".
categorize-bank-transactions — Categorize bank transactions to your chart of accounts
You have a bank or card export to code before it goes into the books, and want each line matched to one of your own accounts.
- reviewer
- Who checks the coding before it is posted, for example "our bookkeeper" or "me, before I enter it in the accounting software".
- chart_of_accounts
- Your list of accounts, with numbers if you use them. Export it from your accounting software.
- past_coding
- How recurring vendors were coded before, for example "Utility company: Utilities 6200", or "none".
- transactions
- The bank or card export: date, description, amount and direction. Remove full card and account numbers first.
- statement_balances
- The opening and closing balance on the statement, or "not available".
- business_description
- What the business does in a sentence, for example "a two-person landscaping company".
ar-aging-collections-plan — Prioritize collections from an accounts receivable aging report
Your list of unpaid invoices is long, and you need to know who to chase first, how, and what to report on receivables.
- period
- The time the plan covers, for example "the next two weeks".
- collector
- Who will do the chasing, for example "our accounts assistant" or "me".
- aging_report
- The aged receivables report from your accounting software, one line per invoice.
- customer_notes
- Payment habits, open disputes and promises to pay, one line per customer, or "none".
- policy
- Your collections steps and approval rules, or "no written policy".
- today
- Today's date.
month-end-accruals-list — List month-end accruals and prepayments for review
You are closing the month and need costs incurred but not yet billed, and amounts paid in advance, turned into proposed entries.
- period_end
- The month-end date, for example "April 30".
- reviewer
- Who reviews and posts the entries, for example "our outside accountant".
- period_facts
- Everything relevant to this month's costs: late bills with their dates and amounts, contracts, unbilled work, prepayments.
- prior_entries
- Last month's accrual and prepayment entries, or "none".
- accounts_and_basis
- The account names to use and whether your books are on an accrual or cash basis, for example "accrual; Accrued expenses 2100, Prepaid expenses 1300".
- threshold
- The smallest amount you bother accruing, for example "500", or "none".
financial-ratios-health-check — Calculate key ratios from your financial statements
You want margins, liquidity and collection ratios worked out from your own statements and explained in plain words.
- reader
- Who the explanation is for, for example "me, the owner" or "our management team".
- income_statement
- Your profit and loss statement, with the dates it covers.
- balance_sheet
- Your balance sheet with its date, plus the previous one if you want changes shown.
- benchmarks
- Your targets, last year's figures or loan covenant levels, or "none".
spending-savings-review — Find savings in your spending by vendor and category
You need to cut costs and want your actual spending sorted into what to cancel, renegotiate, check or keep.
- decision_maker
- Who decides on the cuts, for example "the two partners" or "our operations director".
- period
- The months the spending covers, for example "January to June".
- spending
- A spending export by vendor: name, category, amount, how often, and what it is for if you know.
- protected
- Costs that must stay and why, for example "insurance, payroll software", or "none".
- target
- How much you want to save a year, or "no set target".
bills-to-pay-when-cash-is-short — Decide which bills to pay first when cash is short
You cannot pay every bill this week and need a payment order that protects the business, with the reasons shown.
- payer
- Who approves payments, for example "me" or "the finance director".
- cash_available
- The cash you can use for bills now, after anything already committed.
- dates
- Today's date and the date of your next payment run, for example "Monday 3rd; next run Friday 14th".
- expected_receipts
- Payments you expect before the next run, with amounts, dates and whether each is certain, or "none".
- bills
- Each bill: supplier, amount, due date, what it is for, any late fee or interest, and what happens if it is paid late.
- priorities
- Any order you have already decided, for example "payroll first, then the flour supplier", or "none".
payroll-change-check — Check a payroll run against the last one before approval
Before payroll is approved, you want every change from last period found and explained, so errors are caught before people are paid.
- approver
- Who approves the payroll run, for example "the owner" or "the finance manager".
- previous_register
- Last period's payroll register. Use only an AI tool your company approves for payroll data, and replace names with employee IDs if you prefer.
- current_register
- This period's payroll register, in the same layout as the last one.
- known_changes
- Starters, leavers, rises, bonuses and leave you already know about, or "none".
- threshold
- The smallest change you want flagged, for example "any change over 50 or 5%".
spending-approval-matrix — Draft a spending approval matrix for your team
You need clear rules for who can approve which purchases, contracts and payments, at what amounts, written so people can follow them.
- audience
- Who will use the matrix, for example "all budget holders and the accounts team".
- roles
- The roles involved and who holds them now, for example "Owner; Operations manager; Office manager".
- decisions
- The limits you have decided, in any form, for example "Office manager up to 1,000 on supplies".
- spend_types
- The kinds of spending to cover, for example "purchases, new suppliers, contracts, refunds, write-offs, capital equipment".
- amount_basis
- Your currency and how an amount is measured, for example "USD, contracts counted over their full term".
profit-vs-cash-explained — Explain why profit and cash moved differently
The business made a profit but the bank balance fell, or the reverse, and you need the reasons shown in numbers.
- reader
- Who the explanation is for, for example "me and my business partner".
- period
- The period to explain, for example "the quarter to June 30".
- income_statement
- The profit and loss statement for the period.
- balance_sheets
- Balance sheets at the start and the end of the period.
- cash_balances
- Bank balances at the start and end, for example "start 31,200, end 9,800".
- known_events
- Big cash events you know about, such as a loan repayment or a van purchase, or "none".
margin-by-product-or-customer — Calculate profit margin by product, customer or job
You want to see which products, customers or jobs actually make money once their direct costs are counted.
- unit
- What to measure margin for: "product", "customer" or "job".
- reader
- Who will read the analysis, for example "the owners" or "our sales manager".
- period
- The period the figures cover, for example "last 12 months".
- sales_data
- Revenue for each product, customer or job in the period.
- direct_costs
- The costs you can tie to each one: materials, direct labor, shipping, fees, commissions, discounts. If your sales figures are already after discounts, leave discounts out here.
- shared_costs
- Overheads and the method you want used to split them, for example "rent split by revenue share", or "leave out".
budget-request-pushback-reply — Reply to a budget request you cannot fully fund
A department has asked for more budget than is available, and you need a reply that says what can be funded and why, without souring the relationship.
- requester
- Who asked for the budget, for example "Dana, head of marketing".
- request
- Their budget request, with the lines and amounts they asked for.
- decision
- What you will fund, line by line if possible, for example "approve 40,000 of 65,000: contractors yes, new tool no".
- constraints
- The reasons you are willing to share, in your own words.
- conditions
- What would let them ask again, for example "show the pilot cut lead cost by 20% by June".
depreciation-schedule — Build a depreciation schedule for equipment and other assets
You have bought equipment, vehicles or fit-out and need a schedule of monthly or yearly depreciation for the books, with every figure shown.
- reader
- Who will check and post it, for example "our bookkeeper".
- assets
- Each asset: description, purchase date, cost, date it was put into use, and residual value if any.
- policy
- Your depreciation method, useful lives by asset type, start-month and disposal-month rules, and capitalization threshold. Your accountant can supply these.
- schedule_period
- The months or years to show, for example "each month of this financial year".
- disposals
- Assets sold, scrapped or written off, with dates and amounts received, or "none".
supplier-scorecard-review — Score a supplier's performance before a review meeting
You have delivery, quality and cost data for a supplier and need a fair scorecard and an agenda for the review.
- supplier
- The supplier's name.
- audience
- Who will use the scorecard and run the meeting, for example "our purchasing manager and the warehouse lead".
- agreed_terms
- The service levels, quality limits and prices in the contract or purchase terms, quoted where possible.
- performance_data
- Orders and deliveries with promised and actual dates, rejects, invoice errors and complaints for the period.
- period
- The period the data covers, for example "January to June".
- weights
- How much each area counts and how it is scored, for example "delivery 40%, quality 40%, cost 20%; each scored as the % of its target met", or "none".
weekly-operations-review — Write a weekly operations review from your KPI numbers
You have this week's operations numbers and targets and need a short review that shows what is off track, why, and who is acting on it.
- site
- The site, team or operation, for example "the Eastside warehouse".
- audience
- Who reads the review, for example "the operations director and shift leads".
- metrics
- This week's and last week's figures for each metric, with its target.
- notes
- What happened this week and what people are doing about problems, with owners and dates.
- status_rules
- Your rules for green, amber and red, for example "amber within 2% of target", or "none".
capacity-check-against-demand — Check staff and equipment hours against forecast volume
You have a forecast of orders, units or jobs and need to know, week by week, whether your people and equipment hours cover it, and what to do where they do not.
- planner
- Who plans staffing, for example "the shift manager".
- demand
- Forecast volume per week, with week dates.
- work_standards
- How long each unit of work takes, by type if it differs.
- capacity
- People or machines, available hours per week, leave, shutdowns and overtime limits.
- utilization
- The share of paid hours spent on productive work that you plan with, for example "85%", or "none".
- buffer
- The spare capacity you want to keep, for example "10% of available hours" or "one person-day a week".
preventive-maintenance-schedule — Build a preventive maintenance schedule for your equipment
You need routine maintenance for machines, vehicles or building systems turned into a dated schedule your team can follow.
- period
- The time the schedule covers, for example "the next 12 months".
- team
- Who does or arranges the maintenance, for example "our maintenance technician and the facilities manager".
- equipment
- Each item: name or ID, location, usage rate and last service date.
- tasks
- Each maintenance task with its interval, where it comes from (manual page, service contract, internal rule), how long it takes if known, and whether it is safety-critical.
- people_and_windows
- Who can do the work, their hours for maintenance, and when equipment can be stopped, for example "weekends only for the line".
defect-pareto-analysis — Find the few causes behind most defects, errors or returns
You have a log of defects, errors or returns and want to know which few causes account for most of them, so you fix those first.
- audience
- Who decides what to fix, for example "the quality lead and production manager".
- period
- The dates the log covers.
- defect_log
- One line per defect, error or return, with date, product or process, type or reason, quantity and cost if known.
- volume
- Total units, orders or transactions in the period, saying which, so a rate can be worked out.
- categories
- Your standard defect or reason codes, or "none, group them for me".
business-continuity-plan — Write a continuity plan for one critical process
You need a plan for keeping a critical process running if a key system, supplier, site or person is suddenly unavailable.
- process
- The one process the plan covers, for example "taking and shipping customer orders".
- audience
- Who will use the plan, for example "the shift supervisors and the office manager".
- process_description
- How the process runs, everything it relies on (systems, suppliers, sites, people, data), and who has authority to start the plan.
- tolerance
- How long you can manage without it and what happens after that, for example "half a day; after that we miss courier cut-offs".
- existing_measures
- Backups, manual workarounds, spare equipment, alternative suppliers and emergency contacts you already have.
- scenarios
- The failures to plan for, for example "order system down, main courier unavailable, warehouse inaccessible".
stock-count-variance-investigation — Investigate differences between a stock count and your system
A physical stock count does not match what the system says, and you need the differences ranked and the likely reasons to check.
- audience
- Who investigates and approves adjustments, for example "the warehouse manager and finance".
- count_data
- Each counted item with location, system quantity, counted quantity and unit cost.
- activity
- Receipts, shipments, returns, transfers and adjustments around the count, with dates and times.
- count_details
- When each area was counted, when the system quantities were taken, and whether stock movement was stopped.
- tolerance
- The difference you accept without investigating, for example "2 units or 1% of value".
supplier-quality-complaint — Raise a quality problem with a supplier and request corrective action
A supplier delivered goods that do not meet the agreed specification, and you need a clear, factual complaint that asks them to fix the cause.
- supplier
- The supplier's company name and contact.
- sender
- Who signs the complaint, for example "our quality manager".
- agreed_spec
- The specification, drawing tolerance or purchase order terms the delivery had to meet, quoted.
- findings
- What you found: dates, order and lot numbers, how many checked and rejected, measurements, photos.
- impact
- What it has cost or caused so far, for example "line stopped two hours; 180 parts quarantined".
- requests
- What you want and by when, as dates, for example "replacement stock by Friday, May 9; root cause and corrective action by May 23".
overtime-drivers-analysis — Find what is driving your overtime
Overtime hours or cost have gone up and you need to see where, when and why from your timesheet and workload data.
- audience
- Who will act on the findings, for example "the operations manager and HR partner".
- period
- The weeks or months the data covers.
- hours_data
- Timesheet or payroll hours by person or role: regular hours, overtime hours, team, date, and reason if recorded.
- workload_data
- Volume over the same period, by week or day.
- events
- Absences, open roles, breakdowns or peaks during the period, or "none known".
maintenance-backlog-triage — Prioritize a backlog of maintenance and repair requests
Repair and maintenance requests have piled up and you need them ranked by safety and impact, with a plan for the next two weeks.
- audience
- Who plans and does the work, for example "the facilities coordinator and two technicians".
- backlog
- The open requests, one per line, with ID, date, location or asset, description and who reported it.
- resources
- Technician hours available in the next two weeks, plus parts or contractors already on order.
- priority_rules
- Your own priority levels, or "none".
supplier-renewal-negotiation-plan — Prepare for a supplier contract renewal negotiation
A key supplier contract is up for renewal and you need your asks, fallback positions and evidence in one plan before the meeting.
- supplier
- The supplier's name and what they supply.
- negotiator
- Who leads the negotiation, for example "our procurement lead" or "me".
- current_terms
- The current contract's price, volumes, service levels, length, notice and renewal terms.
- their_offer
- The supplier's renewal proposal or price change notice.
- performance_and_spend
- Their record against the service levels and your annual spend with them.
- alternatives
- Other quotes, the cost and time of switching, or "none yet".
- goals
- What you want from the renewal and what you could give, for example "price freeze; could commit to 2 years".
- deadline
- When you must decide, and the notice date in the current contract.
peak-season-readiness-plan — Get your operation ready for a peak season
A busy season is coming and you need a dated checklist covering staffing, stock, equipment, carriers and customer promises.
- peak
- The season and its dates, for example "the holiday season, November 20 to December 24".
- audience
- Who runs the plan, by role, for example "the warehouse lead, customer service lead and office manager".
- volume
- Expected volume per day or week at peak, saying whether days are calendar or working days, and where the figure comes from.
- last_peak
- What went wrong and what worked last time, or "first peak".
- current_setup
- Your staff, equipment, stock, carriers, systems and hours as they stand now, plus any rates you know, such as orders per picker hour or boxes per order.
- dates
- Peak start and end, last order dates, supplier cut-offs and holidays.
break-even-point — Work out your break-even point
You want to know how many sales a month you need to cover your costs, and how that changes with a decision or with price and cost moves.
- business
- Your business in a few words, for example "my coffee cart".
- decision
- What the numbers are for, for example "opening on Sundays" or "taking the bigger unit".
- prices
- Your average price per sale, or each product's price and roughly how many of each you sell, for example "cakes 85 (40 a month), cupcake boxes 36 (70 a month)".
- variable_costs
- Costs that come with each sale, per sale: materials, packaging, card fees, commissions, delivery.
- fixed_costs
- Monthly costs you pay whatever you sell, with amounts.
- current_sales
- Sales per month now, or "not trading yet".
- decision_changes
- What would change if you go ahead, for example "rent goes from 1,200 to 2,150; expect 60 more sales a month", or "none".
afford-your-next-hire — Work out whether you can afford your next hire
You are thinking about hiring and need the full monthly cost of the role and the extra sales or saved time it has to cover.
- business
- Your business in a few words, for example "my hair salon".
- role
- The hire, for example "a full-time salon assistant" or "a part-time bookkeeper".
- role_details
- Pay, hours, start date and the main duties.
- employer_costs
- Employer costs on top of pay as figures your payroll provider or accountant gave you, or "don't know yet".
- one_off_costs
- Recruiting, equipment and training costs, or "none".
- business_numbers
- Average monthly revenue, gross margin %, monthly fixed costs and current cash.
- payoff
- How the hire earns its keep and how soon, for example "frees me for 10 more client hours a week within 2 months".
chargeback-response-letter — Respond to a chargeback with your evidence
A customer disputed a card payment with their bank, and you need a clear rebuttal letter that matches the dispute reason and points to your evidence.
- business
- Your business name.
- dispute_details
- The dispute notice from your processor: reason code and wording, amount, dates and deadline.
- what_happened
- The facts of the sale and what happened after, with dates. Leave out full card numbers.
- evidence
- Files you can attach, with names and what each shows, for example "1-invoice.pdf; 2-tracking.png, delivered May 3; 3-emails.pdf".
- policy
- Your refund or cancellation terms and how the customer saw or accepted them, for example "checkbox at checkout".
compare-financing-offers — Compare business loan and financing offers
You have more than one offer of a loan, credit line or cash advance and need their true costs side by side before you choose.
- business
- Your business in a few words.
- advisor
- Who you will discuss it with, for example "my accountant" or "my business partner".
- need
- How much, what for and by when, for example "25,000 for a delivery van, within a month".
- offers
- Each offer's terms as the lender wrote them: amount, rate or factor rate, fees, repayment schedule, guarantees, early repayment terms.
- revenue_pattern
- Average monthly revenue and your weakest month, for example "about 40,000; 25,000 in January".
job-cost-estimate — Build a job estimate from materials, labor and markup
You need to price a job from your own material list, labor hours and rates, with the cost build-up shown so the quote covers everything.
- job_description
- What the customer wants done, where, and anything unusual about the site.
- materials
- Each material with quantity and your cost per unit.
- labor
- Each task with who does it, hours, and your hourly cost per person.
- other_costs
- Equipment hire, permits, disposal, travel, subcontractor quotes, or "none".
- pricing_rules
- How you price and quote, for example "30% markup on materials and labor, 10% waste on tile, minimum charge 250; quotes show one total per room".
referral-partnership-pitch — Propose a referral partnership to another local business
You want a business that serves your customers at a different moment to send people your way, and you send people theirs, starting with one easy step.
- business
- Your business name and what you do, for example "Fern & Stem, a florist".
- partner
- The business you are writing to, and the owner's name if you know it.
- about_us
- What you do, who your customers are and where you are based.
- about_them
- What you know about them from visits, their website or customers, or "only what is on their website".
- overlap
- Why your customers overlap, for example "couples booking our flowers usually still need a photographer".
- proposal
- How you want it to work, for example "swap cards and mention each other; 10% off for customers they send; no fees".
- connection
- How you know them, for example "we did the same wedding fair in May", or "we have never met".
- channel
- How you will send it, for example "email to their info address" or "Instagram message".
large-order-decision — Decide whether to take on a large order or client
A big order or client could make your year or overstretch you, and you want the cash, capacity and risk checked before you say yes.
- business
- Your business in a few words, for example "our four-person print shop".
- opportunity
- The order or client: what, how much, price, timing, payment terms and length of commitment.
- current_business
- Monthly revenue, monthly overheads, gross margin, top customers and their share, cash, team and current workload.
- requirements
- Extra people, materials, equipment or upfront spending the deal needs, with costs and how long each commitment lasts.
- client_notes
- What you know about how they pay and work with suppliers, or "nothing yet".
cancellation-no-show-policy — Write a cancellation and no-show policy for appointments
Late cancellations and no-shows are costing you, and you need a clear, fair policy for clients plus short versions for booking pages and reminders.
- business
- Your business name.
- service
- What clients book, for example "massage appointments" or "tutoring sessions".
- prices
- The prices or price range of these appointments, for example "60 minutes 80, 90 minutes 115".
- notice
- For example "24 hours" or "48 hours for sessions over 2 hours".
- charges
- For example "50% of the price for late cancellation, full price for a no-show".
- deposits
- For example "20 deposit taken at booking, applied to the bill" or "none".
- exceptions
- For example "one free late cancellation a year; emergencies at the owner's discretion".
- our_side
- What clients get if you cancel or run late, for example "full refund or priority rebooking".
- lateness
- For example "after 15 minutes the session is shortened; after 30 it counts as a no-show".
end-client-relationship — End a working relationship with a client politely
A client relationship is no longer working, and you need to end it clearly and professionally, with a clean handover of what is left.
- client
- The client's name or company.
- background
- Why you are ending it, for your own context only, for example "late payments and constant scope changes".
- agreement_terms
- The ending, notice, payment and ownership terms from your contract or proposal, quoted, or "nothing in writing".
- today
- Today's date.
- end_plan
- Your last working day for them and what you will complete, for example "finish the March newsletter, stop on March 31".
- money
- Unpaid invoices, prepaid work to refund, or "nothing outstanding".
- handover
- What they will receive and how, for example "all design files via a shared folder; transfer the domain login".
- referral
- A person or firm you are happy to recommend, or "none".
loan-application-business-summary — Write the business summary for a loan application
A lender wants a written description of your business, how you will use the money and how you will repay it, and you need it built from your own facts.
- business
- Your business name.
- lender
- The bank, credit union or lender, and the loan program if there is one.
- business_facts
- What you do, when you started, your customers, team, and the owners' background.
- financials
- Revenue, profit and cash for recent years or months, from your accounts, and what the owners take out as pay or drawings.
- loan_terms
- Amount requested, the term, and the repayment if the lender has quoted one.
- uses
- Each thing the loan pays for, with its cost and whether that is a quote, an invoice or your estimate.
- expected_effect
- What the purchase will do for revenue or costs, and why you expect it, for example "second oven doubles wholesale capacity; two cafes have asked for supply".
- existing_debt
- Current loans, credit lines or leases and their monthly repayments, or "none".
legal-letter-received — Understand a legal letter or demand you received (not legal advice)
You have received a demand letter, cease-and-desist or legal notice and need to know what it claims, asks and requires by when, before you call a lawyer.
- letter_text
- The full letter, copied exactly, including the date, sender details and any reference number.
- relationship
- For example "they were our customer until March" or "a competitor we have never dealt with".
- our_facts
- What you know about the matter, briefly and honestly, including anything that supports their side.
- received
- Each date it arrived and how, for example "May 7 by email; May 9 by post".
- today
- Today's date.
- reader
- Who needs to understand it, for example "me and my co-founder" or "our managing director".
contract-renewal-calendar — Build a renewal and notice calendar across your contracts
You have several supplier or customer contracts and need every renewal, notice and price-change date in one list, so none rolls over by surprise.
- audience
- Who will use the calendar, for example "the office manager and finance".
- contract_extracts
- For each contract: its name, the other party, start date, term, and the renewal, notice and price change clauses copied with their numbers.
- today
- Today's date.
- lead_time
- How long before each deadline you want a reminder, for example "30 days".
commercial-lease-check — Read a commercial lease's costs and terms before signing (not legal advice)
You are about to rent a shop, office or unit and need the lease's costs, commitments and exit terms laid out, with questions for your lawyer.
- lease_text
- The full lease, with schedules if you have them, copied exactly with clause numbers.
- use_of_space
- Your business and what you will do there, for example "a cafe with 30 seats and takeaway, open 7 a.m. to 9 p.m.".
- agreed_terms
- What the landlord or agent told you or offered, for example "3 months rent-free, landlord pays for new flooring", or "nothing agreed".
- plans
- How long you hope to stay and what could make you leave early, for example "3 to 5 years; might bring in an investor".
- reader
- Who is reviewing it with you, for example "me and my business partner".
privacy-notice-from-practices — Draft a privacy notice from your actual data practices
Your website or service needs a privacy notice, and you want a plain draft built from what you really collect and do, ready for a lawyer to check.
- business
- Your business or organization name.
- where
- Where the notice will appear, for example "our website and booking app".
- data_collected
- Every kind of personal data you collect, from whom and how, including cookies and analytics tools.
- purposes
- What you use each kind of data for, for example "email address: order updates and, if they opt in, our newsletter".
- sharing
- The services and partners that receive or process data, for example "Stripe for payments, Mailchimp for email".
- storage_and_retention
- Where data is held and how long you keep each kind, or "not decided".
- choices
- What people can ask for and how, for example "unsubscribe link; email us to see or delete their data".
- contact
- The email or address for privacy questions.
- changes
- The date the notice takes effect and how you will tell people about changes, or "not decided".
- jurisdictions
- Where you and your customers are, and any laws your lawyer has named, or "not yet checked".
document-preservation-notice — Draft a document preservation notice for staff
Your lawyer has said records must be kept for a dispute or investigation, and you need a clear notice telling the right people what to keep and how.
- approver
- Who approves the notice before it is sent, usually your lawyer or in-house counsel.
- matter_summary
- The exact description of the matter your lawyer has approved for staff, for example "a dispute with a former supplier about the 2025 warehouse lease".
- scope
- What must be kept, as your lawyer instructed: topics, people, date range and record types.
- recipients
- Who gets the notice, by name or role.
- systems
- Email, chat, shared drives, phones, paper files and anything IT is doing separately.
- contact
- Who to ask, with email and phone.
- acknowledgment
- How and by when people confirm, for example "reply 'I confirm' by Friday".
conflict-of-interest-review — Review a conflict of interest disclosure against your policy
An employee has disclosed an outside interest, relationship or gift, and you need the facts set against your policy for the person who decides.
- decision_maker
- Who decides on the disclosure, for example "the compliance officer" or "the HR director".
- policy
- Your conflict of interest policy, copied with section numbers.
- disclosure
- The disclosure form or message, as submitted. Share only what your organization allows you to put into an AI tool.
- role_context
- What the person does and which decisions, suppliers or customers they deal with.
- precedents
- Similar past cases and how they were handled, or "none".
data-incident-timeline — Build a fact timeline of a data incident for legal review
Something has gone wrong with personal or confidential data, and your lawyer or privacy lead needs the facts in order before deciding on next steps.
- incident_notes
- Everything written so far: emails, chat messages, ticket notes, log extracts, with times and time zones where known. Use only an AI tool your organization approves for this material.
- systems_and_data
- The systems and kinds of data you think are involved, for example "shared drive folder with customer invoices".
- responders
- Who is working on it, by role, for example "IT lead, office manager, outside IT support".
- time_zone
- The time zone the timeline should use, for example "US Eastern".
- reviewer
- Who decides on next steps, for example "our lawyer and the managing director".
compliance-risk-assessment — Rate compliance risks and controls in a risk register
You need your compliance obligations, the controls you have and the gaps rated in one register, for a compliance review or audit committee.
- audience
- Who the register is for, for example "the audit committee" or "our compliance working group".
- obligations
- The obligations you track, each with its source (law, regulation, contract or policy, as identified by your team or lawyer).
- controls
- The controls for each obligation, their owners if known, and the evidence that they work, such as test results or audit findings.
- incidents
- Recent incidents, complaints, audit findings or near misses, or "none".
- impact_notes
- What a breach of each obligation could lead to (fines, loss of a client, harm to people), as your team or lawyer has assessed it, or the impact score you already use, or "none".
- scoring_method
- Your likelihood and impact scales and how scores map to ratings, for example "1 to 5 each; 15 or more is high".
regulator-inspection-prep — Prepare for a regulator's inspection or audit visit
You have notice of an inspection or regulatory audit and need a document tracker, a readiness check and a briefing for the staff who will meet the inspector.
- coordinator
- Who coordinates the response, for example "our quality manager".
- notice
- The inspection or audit notice and any document request, copied in full.
- requirements
- The rules, standards or permit conditions in scope, as your team or advisors have identified them, quoted.
- current_state
- What is ready, what is not, and any weak spots you already know about.
- people
- Roles likely to meet the inspector, for example "site manager, two shift leads, office manager".
- dates
- Today's date and the date and time of the visit.
small-claims-evidence-pack — Organize your evidence for a small claims case
A customer has not paid or a dispute is heading to small claims court, and you need your facts, amounts and evidence in order before you file or attend.
- my_side
- Who you are in the dispute, for example "a painting contractor owed for a finished job".
- other_party
- Who the claim is against, with the name exactly as it appears on your contract or invoices.
- my_account
- What happened, in order, in your own words.
- evidence
- Each document or item you have, with its date, for example "Quote, March 2; signed acceptance email, March 4".
- claim
- The amount you are asking for and how you got to it.
- their_position
- What the other side has said in writing or in person, or "nothing".
- court_guidance
- Any instructions, forms or limits from the court's own website or office, quoted, or "none yet".
read-research-paper-outside-field — Read a research paper outside your field and judge what it shows
You need to understand a study someone cited, what it actually found and how far you can rely on it, without a background in the field.
- paper_text
- The paper's full text, or at least the abstract, methods and results, with the title, authors and year.
- decision_or_use
- What you will use it for, for example "deciding whether to pilot a four-day week" or "a slide for the board".
- claim_heard
- What someone said the paper shows, in their words. Write "none" if you are reading it cold.
- my_background
- Your job and what you already know, for example "HR manager, no statistics training".
trace-statistic-to-source — Trace a statistic to its original source before you repeat it
You saw a number in an article, deck or post and need to know where it came from and whether it still says what the original said.
- statistic
- The number and the words around it, copied exactly, for example "78% of employees say they would quit over a bad manager".
- where_seen
- Where you saw it, with the date and link if you have them.
- intended_use
- Where you want to use it, for example "a slide in our hiring proposal".
- source_text
- Text from each source you have found, in order, with its name and date. Write "none" if you have not looked yet.
literature-review-matrix — Build a literature review matrix and find the gaps
You have read a set of papers for a thesis, report or proposal and need them compared side by side, grouped into themes, with the gaps shown.
- papers
- For each paper: the citation details, and the abstract or your notes on its aim, method, sample, findings and limitations.
- research_question
- Your question or topic, as specifically as you can put it.
- review_purpose
- What the review is for, for example "the literature review chapter of my master's thesis" or "a policy report for our board".
annotated-bibliography-entries — Write annotated bibliography entries from your sources
You need a summary, an evaluation and a note on relevance for each source, in the citation style your course or publisher asks for.
- citation_style
- For example APA 7th edition, MLA 9th edition or Chicago author-date.
- research_question
- Your question, or the assignment as set.
- annotation_length
- For example "100 to 150 words".
- reader
- For example "my course instructor" or "my thesis supervisor".
- sources
- Each source's full details and its abstract or your reading notes.
narrow-research-question — Narrow a broad topic into a research question you can answer
You have a topic that is too big and need a few focused questions, with the evidence each would need and whether you can get it in time.
- topic
- The topic as you would describe it now, for example "AI in customer service".
- purpose_and_reader
- Why you are doing it and who reads the result, for example "MBA capstone, read by faculty and my employer".
- time_and_resources
- For example "six weeks, evenings only, no budget".
- access
- Data, people or systems you can get at, for example "our ticket data for 2023 to 2025". Write "none" if you have none.
- deliverable
- For example "a 3,000-word report" or "a ten-minute presentation".
reports-with-different-numbers — Explain why two reports give different numbers
Two sources disagree on a figure, such as a market size, a rate or a survey result, and you need to know why before you choose one.
- figure
- What both sources measure, for example "number of small businesses in Texas" or "annual staff turnover in retail".
- use_and_audience
- Where the figure will go and who sees it, for example "a market sizing slide for our investors".
- source_a
- The first source's name, date and the text around the figure, including any methods or definitions section.
- source_b
- The second source, with the same details.
quiz-me-on-material — Quiz yourself on material you are learning, one question at a time
You are studying for an exam, a certification or a new role and want to be tested on your own material, with feedback after each answer.
- learning_goal
- What you are preparing for, for example "the PMP exam in six weeks" or "my first month as a claims handler".
- current_level
- For example "read it once" or "know the basics, weak on the exceptions".
- question_count
- How many questions, for example 10.
- question_types
- For example "short answer and scenarios, no multiple choice".
- material
- The notes, chapter, policy or guide to be tested on.
glossary-for-new-field — Build a glossary of terms from the documents of a new field
You have joined a new team, industry or project and need the jargon in its documents defined in plain words, the way your organization uses it.
- field
- For example "commercial insurance claims" or "the hospital's finance team".
- my_role
- Your job and what you know already, for example "new project coordinator, from retail".
- other_readers
- For example "new starters on the team" or "just me".
- documents
- Several typical documents or extracts, with names or dates so quotes can point to them. Remove anything confidential.
literature-search-strings — Write search strings for a literature or database search
You need keyword and Boolean searches for Google Scholar, a library database or a news archive that find the right sources without thousands of misses.
- research_question
- Your question, as specifically as you can put it.
- purpose
- For example "a literature review chapter" or "background for a policy briefing".
- databases
- For example "Google Scholar, PubMed and our library's EBSCO search".
- inclusion
- For example "2015 onward, English, peer-reviewed studies and government reports".
- exclusion
- For example "opinion pieces, studies of children". Write "none" if nothing.
- known_sources
- Titles or short notes on two or three sources you know belong in the results.
check-understanding-by-explaining — Check your understanding by explaining a topic back
You have been learning something new and want your own explanation checked for gaps and mistakes before you rely on it at work or in an exam.
- topic
- What you are learning, for example "how our sales commission is calculated" or "confidence intervals".
- use_context
- Where you will rely on it, for example "an exam next week" or "explaining it to my team on Monday".
- how_learned
- For example "an online course and two conversations with finance".
- my_explanation
- Your explanation, written as if teaching it to a colleague. Do not polish it first.
- reference_material
- The policy, chapter or notes it should match. Write "none" if you have nothing to paste.
abstract-for-paper-or-submission — Write an abstract for a paper, thesis or conference submission
You need an abstract within a strict word limit that states the question, method, findings and why they matter, using only what your work shows.
- venue_rules
- For example "conference abstract, 250 words, headings Background, Methods, Results, Conclusions".
- readers
- For example "the program committee" or "journal editors and readers in public health".
- field
- Your discipline, for example "nursing education" or "supply chain management".
- work_text
- The paper or a full summary of it, including the results with their numbers.
response-to-reviewers — Respond to peer reviewer comments point by point
You have reviewer or examiner comments on a paper, thesis or report and need a polite, complete response letter that matches the changes you made.
- reviewer_comments
- All reviewer and editor comments, copied exactly, with the reviewer numbers.
- my_notes
- For each comment, what you changed and where (section, page or line), or why you did not change it.
- venue_and_decision
- For example "journal article, major revision" or "thesis, minor corrections".
- format_rules
- Any rules from the editor or university about the response, or "none".
fix-spreadsheet-formula-error — Fix a spreadsheet formula that shows an error or the wrong result
A formula returns #N/A, #VALUE!, #SPILL! or a number you know is wrong, and you need the cause, the fix and a way to confirm it.
- app_and_version
- For example "Excel for Microsoft 365", "Excel 2016" or "Google Sheets".
- formula
- The formula exactly as it appears in the formula bar, and its cell, for example "=VLOOKUP(A2,Prices!A:B,2,FALSE) in Orders!F2".
- what_it_shows
- For example "#N/A on about half the rows" or "a total of 0".
- expected_result
- The right answer for at least one row and how you know, for example "F2 should be 18.50, from the price list".
- who_uses_it
- For example "the whole sales team" or "just me".
- sample_data
- Headers and five to ten rows of the cells involved, copied as they appear, with personal data removed.
compare-two-lists-spreadsheet — Compare two lists in a spreadsheet and find what is missing or changed
You have two lists, such as last month's and this month's customers or a system export and your own tracker, and need what is in one but not the other and what changed.
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- list_a
- For example "Sheet 'Sept', columns A to F, about 2,400 rows".
- list_b
- For example "Sheet 'Oct', columns A to G, about 2,550 rows".
- match_key
- For example "Customer ID in column A of both" or "email address".
- compare_columns
- The columns that might change, for example "Plan and Status". Write "none" if you only need missing items.
- purpose
- For example "finding customers who cancelled" or "checking the payroll export against HR records".
- sample_rows
- Headers and five rows from each list, with personal data replaced by placeholders.
conditional-formatting-rule — Write a conditional formatting rule that highlights the rows you need
You want overdue items, values over a limit or whole rows that meet a condition to stand out automatically in Excel or Google Sheets.
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- condition
- For example "rows where the due date has passed and status is not Done".
- highlight_style
- For example "light red fill on the whole row".
- range
- For example "A2:H500 on the Tasks sheet; headers in row 1".
- users
- For example "the project team" or "our front desk staff".
- sample_rows
- The headers and five to ten rows, copied as they appear.
tracker-spreadsheet-design — Design a tracker spreadsheet for a team process
You need a shared sheet to track requests, tasks, applicants or orders, with the right columns, drop-down lists and status formulas so it stays clean.
- process
- For example "IT equipment requests from staff" or "job applicants for three open roles".
- users
- For example "four coordinators enter data; the operations manager reads it weekly".
- app_and_version
- For example "Google Sheets" or "Excel for Microsoft 365 in SharePoint".
- questions_to_answer
- For example "how many requests are open, which are over 5 days old, average time to close".
- current_tracking
- The current headers, or a description such as "an email folder". Write "none" if new.
- volume
- For example "about 30".
date-and-working-day-formulas — Calculate due dates, working days and durations in a spreadsheet
You need formulas for deadlines, working days between dates, tenure or days overdue that handle weekends, holidays and blanks correctly.
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- calculation
- For example "due date 5 working days after the received date" or "years and months of service as of today".
- date_columns
- For example "Received in column B, shown as 05/22/2025; Closed in column F, often blank".
- working_calendar
- For example "Monday to Friday; US federal holidays" or "Sunday to Thursday".
- users
- For example "the support team" or "HR".
- sample_rows
- Headers and five rows, including a blank and any odd-looking date.
combine-sheets-into-one-table — Combine several sheets or files into one table
Your data is split across monthly tabs, regional files or several exports, and you need one combined table that updates when new data arrives.
- app_and_version
- For example "Excel for Microsoft 365 on Windows" or "Google Sheets".
- sources
- For example "12 monthly tabs, Jan to Dec, in one workbook; a new tab each month" or "5 regional files in one SharePoint folder".
- column_match
- For example "yes", "same columns, different order" or "not sure".
- purpose
- For example "a pivot table of sales by region for the year".
- sample
- The header row and two data rows from at least two sources, labeled with the source name.
explain-statistical-output — Explain regression or statistical output in plain words
You ran an analysis, or were sent one, and need to know what the coefficients, p-values and R-squared actually say before you report them.
- question
- For example "Does training hours predict first-year sales, once region is taken into account?"
- tool
- For example "Excel Analysis ToolPak", "SPSS", "R" or "a colleague's report".
- data_description
- For example "one row per sales rep, 146 reps, 2024".
- audience
- For example "the regional managers" or "my manager".
- output
- The whole output table or summary, copied exactly, with its labels.
survey-ratings-summary — Summarize survey ratings and multiple-choice results correctly
You have rating-scale and multiple-choice answers from a staff, customer or student survey and need percentages, comparisons and a summary you can defend.
- survey_description
- For example "annual staff engagement survey, all employees, May 2025".
- response_counts
- For example "412 invited, 287 responded".
- groups
- For example "department and length of service". Write "none" for no comparisons.
- min_group_size
- For example 10. Many organizations use 5 or 10 to protect anonymity.
- audience
- For example "the leadership team" or "all staff".
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- results
- Counts per answer for each question with the question wording, or the raw responses with one row per person. No names.
simple-spreadsheet-forecast — Build a simple forecast in a spreadsheet from past monthly numbers
You need the next few months of volumes, sales or sign-ups projected from history, with a range and the formulas, without a statistics package.
- measure
- For example "monthly support tickets" or "new members per month".
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- horizon
- For example "the next 6 months".
- purpose
- For example "planning staff hours for next quarter".
- known_changes
- Anything coming that the history cannot know about. Write "none known" if nothing.
- history
- At least 12 periods, ideally 24 or more, as date and value pairs.
explain-sql-query — Explain a SQL query before you reuse or change it
Someone gave you a query that produces a report, and you need to know what it does, what it counts and how to change a date or filter safely.
- database
- For example "PostgreSQL", "SQL Server", "BigQuery" or "Snowflake". Write "not sure" if you do not know.
- stated_purpose
- What the person who gave it to you said, for example "monthly active customers by region".
- change_wanted
- For example "run it for last quarter instead of last month". Write "none, just explain" if no change.
- sql_level
- For example "I can read SELECT and WHERE, joins confuse me".
- query
- The full query, copied exactly.
- schema_notes
- Anything you know about the tables. Write "none" if you have nothing.
remove-duplicates-keep-right-record — Remove duplicate records and keep the right one
Your contact list, CRM export or sign-up sheet has the same person or item several times, and you need rules for which row to keep and formulas to mark the rest.
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- row_meaning
- For example "one customer", "one order" or "one applicant".
- match_columns
- For example "email", or "first name, last name and postcode".
- keep_rule
- For example "the most recent Last updated date" or "the row with a phone number".
- purpose
- For example "a mailing to members" or "importing into our new CRM".
- sample_rows
- Headers and ten or so rows that include duplicates, with real names and contact details replaced by placeholders.
reshape-wide-table-to-long — Reshape a wide table so you can pivot, filter and chart it
Your data has months, sites or products as columns, and you need one row per item per period so pivot tables, filters and charts work.
- app_and_version
- For example "Excel for Microsoft 365" or "Google Sheets".
- table_description
- For example "monthly sales by store, one row per store, one column per month".
- column_roles
- For example "Store and Region identify the row; Jan to Dec are values".
- next_step
- For example "build a pivot table by region and quarter" or "chart each store over time".
- sample_rows
- The header row and three data rows, including any total row or column.
three-point-estimates — Estimate tasks with best, likely and worst cases
You need task and project estimates that show a realistic range and a figure you can commit to, instead of one optimistic number.
- project_summary
- One or two sentences on the project, for example "moving our client records to a new CRM by March".
- audience_and_decision
- For example "the sponsor, who must confirm the go-live date".
- unit
- For example "person-days of effort" or "working days".
- history
- For example "our last migration took 40% longer than estimated". Write "none" if unknown.
- task_estimates
- One line per task: name, best, likely and worst case, in the unit above.
issue-log-from-notes — Turn scattered project problems into an issue log with owners
Problems are spread across emails, chat and meeting notes, and you need one log of what is wrong now, who owns each and what happens next.
- project_name
- The project's name.
- people
- Names or roles and what each looks after, for example "Sam, project lead; IT lead; Finance contact".
- severity_scale
- Your own scale, or "default".
- review_meeting
- For example "Thursday's project team meeting".
- source_notes
- The emails, chat messages and notes, each with its date and author if you have them.
decision-log — Keep a decision log from meetings and messages
Decisions on your project are spread across meetings, emails and chat, and you need one record of what was decided, by whom, why and what it replaced.
- project_name
- The project's name.
- decision_rights
- For example "sponsor: budget and dates; steering group: scope; project lead: day-to-day".
- readers
- For example "the project team and the steering group".
- source_material
- Notes and messages with their dates and authors.
- existing_log
- Your current log, copied in. Write "none" if you are starting one.
retrospective-board-to-actions — Turn a retrospective board into themes and a few actions
Your team's sprint or monthly retrospective produced a board of notes and votes, and you need clear themes and two or three actions people will actually do.
- team_and_period
- For example "support tooling team, sprint 14 (two weeks)".
- format_used
- For example "Start, Stop, Continue" or "Went well, To improve, Ideas".
- previous_actions
- Last time's actions and their status. Write "none recorded" if there were none.
- board_notes
- Every note as written, with its column and vote count, exported or copied from the board.
team-capacity-check — Check whether your team has capacity for the planned work
You need to see, person by person and week by week, whether the work planned fits the hours people really have, before you commit to dates.
- period
- For example "the six weeks from May 5".
- audience_and_decision
- For example "my director, deciding whether we can take on the audit project in May".
- team_availability
- One line per person: name or role, hours per week for this work, and dates off.
- planned_work
- One line per task: name, estimated hours, owner, start and due dates.
project-closure-report — Write a project closure report
The project is finished and you need a record of what was delivered against plan, what is still open, who owns it now and when benefits will be measured.
- project_name
- The project's name.
- readers
- For example "the sponsor signs off; the steering group and the operations manager read it".
- handover
- For example "the service desk owns support from July 1; documents in the project SharePoint". Write "not agreed" if it is not settled.
- baseline
- The approved goals, scope, deliverables, dates and budget, from the charter or last approved plan.
- actuals
- What was delivered, final dates and costs, approved changes and anything left open.
cross-team-dependency-map — Map the dependencies between teams on a project
Several teams or suppliers must hand work to each other, and you need to see who is waiting on whom, by when, and which hand-offs could sink the date.
- project_and_deadline
- For example "new payroll system, live for the January 1 pay run".
- teams
- Each team or supplier and its contact, for example "HR (Dana), IT (Lee), Finance (Omar), vendor (account manager)".
- audience
- For example "the steering group" or "the team leads at Monday's meeting".
- source_notes
- Plans, notes and messages about what each team needs, with dates and authors.
tracker-export-health-check — Find slipping and stuck tasks in a project tracker export
You have an export from Jira, Asana, Monday, Smartsheet or a spreadsheet and need overdue, unassigned and stalled tasks pulled out before your weekly review.
- today
- Today's date, for example "May 6, 2025".
- tool
- For example "Jira", "Asana" or "our Smartsheet plan".
- milestones
- For example "Pilot launch May 20; full rollout June 30".
- stale_days
- For example 7.
- max_open
- For example 8.
- use
- For example "Wednesday's project review" or "my update to the sponsor".
- export
- The exported rows with headers. Remove columns with personal or confidential details you do not need.
project-recovery-plan — Write a recovery plan for a project that is behind
Your project has slipped on time or budget, and you need the causes, realistic options and a revised plan to take to the sponsor.
- project_name
- The project's name.
- sponsor_priorities
- For example "the COO; the date matters most because of the trade show".
- fixed_constraints
- For example "budget cannot rise; the regulator's deadline is fixed". Write "none" if everything can move.
- status
- Planned against actual: milestones and dates, percent complete, spend against budget.
- team_input
- Causes and recovery ideas from the team, with any estimates of time or cost.
statement-of-work-for-contractor — Write a statement of work for a contractor or agency
You are hiring a freelancer, agency or contractor for part of a project and need deliverables, acceptance criteria, dates and payment written down before work starts.
- work_description
- The project and the part being contracted, for example "redesign of our website's five main pages".
- contractor
- The freelancer or company, and their contact.
- approver
- For example "Jo Park, marketing lead".
- payment
- For example "fixed fee of $18,000: 30% at start, 70% on acceptance".
- dates
- Start, key milestones and end date.
- our_inputs
- For example "brand guidelines and page copy by May 1; weekly 30-minute review call".
- notes
- Emails, call notes and the contractor's proposal or quote.
forecast-project-final-cost — Forecast a project's final cost from spend and progress so far
Partway through a project, you need to know whether it will finish over or under budget, using spend to date and how much work is actually done.
- project_name
- The project's name.
- budget
- For example "$480,000 including contingency".
- audience_and_purpose
- For example "the finance director, for the quarterly forecast".
- known_changes
- For example "approved change CR-07 adds $22,000". Write "none" if nothing.
- cost_data
- One line per work package with budget, planned value to date, actual cost to date, percent complete and how it was measured.
brief-for-mid-project-joiner — Brief someone joining a project halfway through
A new team member, manager or contractor is joining a running project and needs the context, decisions, people and current state in a few pages.
- project_name
- The project's name.
- joiner
- For example "Alex, contract business analyst, owning user testing".
- first_week
- For example "meet the site leads; review the test plan". Write "not set" if unknown.
- project_material
- The charter, latest plan and status, decision and risk logs, and key recent emails, with their dates.
feature-requests-by-problem — Group feature requests by the problem behind them
You have a pile of feature requests from customers, sales and support, and need to see which problems come up most and for whom.
- requests
- The feature requests, one per line or entry, with whatever you have for each: who asked, segment, revenue, date, source.
- product
- Your product, in a few words.
- fields
- What each request includes, for example "customer name, plan, date and the request text".
- strategy
- What the team is focused on this quarter, for example "retaining mid-size accounts". Write "none set" if there is no focus.
- audience
- Who will read the result, for example "the product trio and the head of product".
working-backwards-press-release — Write a working-backwards press release and FAQ for a product idea
You want to test a product idea by writing its launch announcement and its hardest questions before anyone builds it.
- audience
- Who decides, for example "the leadership team at the quarterly planning review".
- idea
- The product or feature idea, in one to three sentences.
- customer_problem
- Who the customer is and the problem they have today.
- evidence
- What you know so far: interview notes, data, requests, sales feedback. Write "none yet" if you have nothing.
- constraints
- Known limits on budget, timing or technology. Write "none known" if there are none.
feature-enablement-brief — Brief sales and support on a feature before it launches
A feature ships soon and customer-facing teams need to know what it does, who it is for, what it does not do and how to answer questions.
- teams
- Who the brief is for, for example "account executives, customer success and the support team".
- feature_facts
- What the feature does: the spec, release notes, design notes or a demo script.
- launch_details
- Launch date, who gets it, which plans or regions, and any pricing change.
- limitations
- What it does not do yet and known bugs at launch. Write "none known" if there are none.
- customer_questions
- Questions customers or prospects have already asked. Write "none yet" if there are none.
- escalation_route
- Where reps send questions they cannot answer, for example "the #launch-billing channel, owned by the PM".
analytics-tracking-plan — Write an analytics tracking plan for a new feature
A feature is about to be built and you need the events and properties defined so you can tell after launch whether it works.
- feature_flow
- The feature and its flow, step by step from the user's side, including errors and the success moment.
- questions
- What you need to know after launch, numbered, for example "1. How many accounts use it in the first month? 2. Where do people abandon the setup?"
- conventions
- Your naming convention and a list of existing events. Write "none" if you have no convention yet.
- tool
- The analytics tool, for example Amplitude, Mixpanel, PostHog or Google Analytics.
- privacy_rules
- What must never be tracked, for example "no personal data, no health information".
usability-test-script — Write a usability test script for a prototype
You are testing a prototype or a live flow with users and need realistic tasks, neutral moderator wording and a note-taking sheet.
- prototype_description
- What the prototype covers: the screens or steps, what works and what is only a picture.
- learning_goals
- What you want to find out, for example "whether people find bulk edit and understand what it changes".
- participants
- Who you are testing with, for example "five office managers who order supplies monthly".
- session_length
- How long each session is, for example 45 minutes.
- session_format
- For example "remote, moderated, over video call".
- moderator
- Who runs the sessions, for example "our product designer".
beta-program-plan — Plan a beta program with clear exit criteria
You are about to put a new feature in front of a small group of customers and need who to invite, what to ask and when the beta is over.
- audience
- Who needs to agree on the plan, for example "product, engineering and the customer success lead".
- feature
- What the feature does and what state it is in.
- learning_goals
- What you most need to find out, for example "whether admins can set it up without help".
- candidate_customers
- Customers or segments you could invite. Write "none chosen yet" if you have no list.
- capacity
- How long the beta can run and how much time the team has for beta users, for example "6 weeks, one PM and one support person part time".
- known_risks
- Rough edges and risks you already know about. Write "none known" if there are none.
feature-retirement-plan — Plan a feature's retirement and the notice to customers
You are removing or replacing a feature and need a timeline, a migration path and a customer notice that does not cause a flood of tickets.
- feature_details
- What the feature does, who uses it and what data it holds.
- usage_data
- Usage numbers: active accounts, how often they use it, segments, top users.
- reason
- Why it is being retired, in plain words, for example "few customers use it and it blocks the new reporting system".
- replacement
- What customers should use instead, or "none".
- dates
- Dates already decided, or "not decided".
- commitments
- Contract terms, notice periods or legal requirements that apply. Write "none known" if there are none.
- audience
- Who approves the plan, for example "the VP of product and the head of support".
- min_notice
- The minimum notice you want customers to have, for example 90 days.
interface-microcopy — Write interface text for buttons, errors and empty states
You need clear, consistent text for a screen or flow: labels, buttons, error messages, empty states and confirmations.
- screens
- Each screen and the elements that need text, for example "Invite screen: title, email field label, role dropdown, send button, error when the email is already a member".
- style_guide
- Your product's writing rules or voice notes. Write "none" if you have none.
- users
- The product and who uses it, for example "scheduling software for clinic receptionists".
- platform
- Where the text appears, for example "mobile app, iOS and Android".
- char_limits
- Limits by element, for example "buttons 20 characters, titles 40". Write "none" if there are none.
onboarding-drop-off-diagnosis — Find where new users drop off in onboarding and what to test
Too few new sign-ups reach the moment they get value, and you need to see where they stall and which fixes to test first.
- team
- Who will use the analysis, for example "the growth squad".
- activation_definition
- The moment a new user gets value, for example "creates a project and invites one teammate within 7 days".
- funnel_data
- Counts or rates for each onboarding step, with the date range, from your analytics tool.
- flow_description
- The onboarding steps as a new user sees them, screen by screen.
- qualitative
- Ticket themes, recording notes, survey comments or interview notes about onboarding. Write "none" if you have none.
customer-journey-map — Map the customer journey from research and support data
You need one view of how customers find, start, use and leave your product, with the pain at each stage backed by real evidence.
- research
- Interview notes, survey results, support ticket themes, reviews and analytics findings, each labeled with its source.
- product
- Your product, in a few words.
- segment
- The customer group to map, for example "small accounting firms on the starter plan".
- stages
- Your own journey stages, or "none".
- owner_teams
- The teams that could own fixes, for example "marketing, sales, onboarding, support, product".
- audience
- Who will use the map, for example "product, marketing and customer success leads".
coding-agent-dependency-upgrade — Brief a coding agent to upgrade a dependency to a new major version
You need a library or framework moved to a new major version, with breaking changes handled and the tests still passing.
- package
- The library or framework, for example react-router or Django.
- current_version
- The version you are on now.
- target_version
- The version to move to.
- reason
- Why you are upgrading, for example "security fixes and support for Node 22".
- usage_locations
- Folders or files that use it heavily, or "not sure".
- migration_notes
- A link to the official migration guide, or the relevant section pasted in.
- related_packages
- Plugins or packages tied to it, or "not sure".
- check_commands
- The commands for tests, build and types, for example npm test && npm run build && npx tsc --noEmit.
- max_files
- The number of files above which the agent must check with you first, for example 15.
- off_limits
- Files, folders or systems that must not change, for example migrations or generated code.
agents-md-for-repository — Have a coding agent write an AGENTS.md or CLAUDE.md for your repository
You want a short instructions file that tells coding agents how to build, test and work in your repository, checked against commands that actually run.
- file_name
- AGENTS.md (read by Codex, Cursor and many others) or CLAUDE.md (read by Claude Code).
- team_rules
- Rules you want agents to follow that the code does not show, one per line, for example "never edit files in src/generated" or "every API change needs a changelog entry".
- existing_docs
- Docs worth reading first, for example README.md and CONTRIBUTING.md, or "none".
- off_limits
- Folders or files agents must not change without asking, for example infra/ or database migrations.
- max_lines
- The maximum length, for example 80. Short files get read and followed; long ones get skimmed.
coding-agent-performance-fix — Brief a coding agent to speed up a slow code path, measured before and after
Something in your code is too slow, and you want an agent to find the cause and prove its fix with measurements rather than guesses.
- slow_operation
- What is slow, for example "generating the monthly invoice PDF" or "the /search endpoint".
- current_timing
- How long it takes now and how you measured it, for example "about 8 seconds for an account with 2,000 invoices".
- target_timing
- The time you need, for example "under 2 seconds for the same account".
- location
- Files, functions or endpoints involved, as far as you know.
- repro
- The input, data or request that triggers the slow case.
- suspicion
- Your guess at the cause, or "none".
- test_command
- The command that runs the tests, for example npm test or pytest.
- off_limits
- Files, folders or systems that must not change.
coding-agent-flaky-test — Brief a coding agent to fix a flaky test
A test passes and fails at random, and you want the cause fixed rather than the test retried, skipped or loosened.
- test_name
- The test's name as the runner shows it, for example "checkout applies discount once".
- test_file
- The file it lives in, for example src/cart/checkout.test.ts or tests/test_checkout.py.
- failure_pattern
- How often and where it fails, for example "about 1 in 20 CI runs, never locally".
- failure_output
- The exact output from a failed run, pasted rather than described.
- single_test_command
- The command to run only this test, for example npx jest src/cart/checkout.test.ts -t "applies discount".
- suite_command
- The command for the full test suite.
- off_limits
- Files, folders or systems that must not change, for example the CI configuration.
zero-downtime-schema-change — Plan a database schema change without downtime
You need to rename, split or change a column or table on a live database and want a step-by-step plan that keeps the app working throughout.
- current_schema
- The table definitions involved, with indexes and constraints.
- change
- What you need to change and why, for example "split the name column into first_name and last_name for the new billing export".
- database
- The database and version, for example PostgreSQL 16 or MySQL 8.4.
- table_sizes
- Row counts and write traffic for the tables involved, or "unknown".
- deploy_process
- How code ships, for example "rolling deploys, old and new versions run together for about 10 minutes".
- migration_tool
- For example Rails migrations, Alembic, Flyway or plain SQL scripts.
- code_paths
- Services, files or queries that read or write these tables, as far as you know.
- reviewers
- Who reviews the plan, for example "the backend team and our database administrator".
slow-sql-query-tuning — Speed up a slow SQL query using its query plan
A query is too slow and you have its text and execution plan, and want the likely cause and fixes ranked from safest to riskiest.
- database
- The database and version, for example PostgreSQL 16, MySQL 8.4 or SQL Server 2022.
- requester
- Who will act on it, for example "me" or "the on-call backend engineer".
- query
- The slow query, exactly as it runs.
- query_plan
- The execution plan, ideally with actual timings (EXPLAIN ANALYZE or the equivalent).
- schema
- CREATE TABLE statements and existing indexes for the tables in the query.
- volumes
- Row counts and how often the query runs, for example "orders has 40 million rows; runs on every dashboard load".
on-call-runbook — Write an on-call runbook for an alert
An alert fires and whoever is on call needs to know what it means, how to check impact and what to do, without the person who built the service.
- alert_definition
- The alert's name, condition, threshold and where it fires, copied from your monitoring tool.
- service_description
- What the service does and which users or systems depend on it.
- past_notes
- Past incident notes, chat threads and anything the owner knows about this alert. Write "none" if it has never fired.
- tools
- Dashboard names, log queries and commands on-call engineers can use, pasted exactly.
- escalation
- Who to contact, when and how, for example "page the payments owner through PagerDuty if checkout errors last over 15 minutes".
review-coding-agent-pull-request — Review a pull request written by a coding agent
A coding agent opened a pull request and you want it checked against the brief for scope creep, weakened tests and invented code before you merge.
- brief
- The task you gave the agent, as you wrote it.
- agent_summary
- The agent's own summary of what it did, from the pull request or the session.
- diff
- The full diff of the pull request.
- project_notes
- Anything that helps judge the diff: the project's AGENTS.md or CLAUDE.md, relevant interfaces, or "none".
- reviewer
- Who decides on the merge, for example "me" or "the tech lead".
socratic-tutor-system-prompt — System prompt for a tutor that guides students without giving answers
You are building a Custom GPT, Gem or chatbot for a course and want it to coach students toward the answer instead of doing the work for them.
- course
- The course or subject, for example "Algebra 1" or "Introduction to Statistics".
- level
- Grade or level, for example "9th grade" or "first-year university".
- course_material
- Key definitions, methods, notation and common mistakes from your course, pasted in. Do not include answer keys.
- teacher
- Who students should go to, for example "your teacher, Ms. Rivera".
- support_contact
- Your school's support route, for example "the school counselor or a crisis line".
- input
- The student's message. Your app inserts it at run time; the Chatbot Safety Test puts its attack probes here.
Resources
Not advertised
30-day availability
Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.
- Successful checks
- 1 of 1 (100%)
- Average latency
- 3562 ms
- 95th percentile latency
- 3562 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 3562 ms · metadata changed · 8 tool(s), 500 prompt(s) (partial: item-cap)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
Claude Code configuration
claude mcp add --transport http thinkhard-si-mcp https://thinkhard.si/mcpCodex
Codex configuration
codex mcp add thinkhard-si-mcp --url https://thinkhard.si/mcpCursor
Cursor configuration
{
"mcpServers": {
"thinkhard-si-mcp": {
"url": "https://thinkhard.si/mcp"
}
}
}Cline
Cline configuration
{
"mcpServers": {
"thinkhard-si-mcp": {
"type": "streamableHttp",
"url": "https://thinkhard.si/mcp",
"disabled": false
}
}
}VS Code
VS Code configuration
{
"servers": {
"thinkhard-si-mcp": {
"type": "http",
"url": "https://thinkhard.si/mcp"
}
}
}Gemini CLI
Gemini CLI configuration
gemini mcp add --transport http thinkhard-si-mcp https://thinkhard.si/mcpClaude Desktop
Claude Desktop configuration
{
"mcpServers": {
"thinkhard-si-mcp": {
"url": "https://thinkhard.si/mcp"
}
}
}Windsurf
Windsurf configuration
{
"mcpServers": {
"thinkhard-si-mcp": {
"serverUrl": "https://thinkhard.si/mcp"
}
}
}Let your agent find its tools
Find servers like thinkhard.si MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other productivity and knowledge servers
Do you run thinkhard.si MCP?
Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.