Prompt library

Research accounts, score contacts, leave outreach for you to approve. · Playbook

Research the 25 accounts in this CRM view. Score them against our ideal customer profile and recent intent, identify up to three relevant contacts per account, and draft email and LinkedIn outreach in the style examples attached.
Skip anyone already in an active sequence.
Return a review list with evidence for each score.
Do not send, enroll, or edit CRM records.

Source candidates, explain the match, draft outreach — never contact anyone. · Playbook

For this role description, find 20 potential candidates who meet the must-have criteria.
Exclude anyone already in our ATS, explain the evidence for each match, and draft personalized outreach in my voice.
Do not contact anyone.
Flag any regional, privacy, or source-term issue instead of working around it.

Monitor spend and recommend moves. Never change a budget on its own. · Playbook

Pull current spend and performance by campaign. Compare it with the monthly budget and target customer acquisition cost, then recommend reallocations with the supporting numbers.
Draft a Slack update for the growth team.
Do not change budgets or send the message.

Reconcile receipts and flag exceptions. Leave reimbursements untouched. · Playbook

Build this week's expense summary from the expense system and attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner.
Return the summary and drafts.
Do not send messages or change reimbursements.
Cite the policy section on every exception.

Investigate with evidence. Never touch production settings. · Playbook

Investigate the checkout latency increase since yesterday's release. Review dashboards, traces, and flamegraphs; identify the highest-confidence hotspot; and return a short write-up with screenshots and direct links.
Separate facts from hypotheses.
Do not change alerts or production settings.

Turn a report into a reproduction pack. Stay out of production customer data. · Playbook

Read this bug report and reproduce it in staging using a fresh test account.
Return exact steps, expected and actual behavior, screenshots, browser and OS details, relevant console or network notes, and a minimal test case if possible.
Do not use production customer data.

Rank the watch list with evidence. Do not contact customers or edit the CRM. · Playbook

Review the accounts in this portfolio. Combine recent usage, support escalations, renewal timing, and stakeholder activity into a ranked watch list.
For each account, include the evidence, why it matters, and a suggested next step.
Do not contact customers or edit the CRM.

A source-linked digest of what changed and what needs a decision. · Playbook

Review activity since yesterday across my approved channels, inbox, calendar, and meeting notes. Return only items that map to the priorities in this document.
For each item, include the source, why it matters, the proposed next step, and whether I owe a decision.
Do not send messages or change meetings.

Related guide

Follow along while I complete this job once. Record the systems I open, the clicks that matter, the files I touch, and every place I stop to judge.
Do not send, publish, purchase, or delete anything during this demonstration.
When I finish, restate the path as numbered steps, including exceptions and the approval stop.
We will replay it on a second sample before any schedule is created.

Related guide

Revise the existing artifact. Separate facts found in source systems, inferences, actions already completed, actions waiting for approval, and unresolved questions.
Cite sources. Do not treat the chat summary as proof of completion.