Prompt library

I want to find recurring tasks in my work that an AI assistant could draft for me. Interview me about my last working week. Ask one question at a time. For each task I mention, ask how often it happens, how long it takes, how much I dislike it on a scale of 1 to 5, what a mistake would cost on a scale of 1 to 5, and whether a mistake can be undone. When I say I am done, give me the answers as a table.

Here are my notes on recurring tasks from this week:

[paste your notes]

Turn them into a table with these columns: task, runs per week, minutes per run, weekly minutes, dread (1-5), error cost (1-5), reversible (yes or no). Calculate weekly minutes as runs per week times minutes per run. Sort by weekly minutes, highest first. Do not invent numbers. If a value is missing, write "missing".

Here is my audit table:

[paste your table]

Rank these tasks as first targets for an AI assistant that only produces drafts for me to check. Favor tasks with high dread, low error cost, and mistakes that can be undone. Exclude tasks that send anything outside my company, move money, or change a system other people rely on. Explain each ranking in one sentence.

I plan to automate this task first: [describe the task]. Make the strongest case against starting here. List what could go wrong, what I might not notice, and which task from my list would be a safer start. Be specific to my task.

Interview me about a recurring task so you can write a SKILL.md file for it. Ask one question at a time. Cover: what the task produces and who reads it; the exact sources it reads and for what period; the sections of the output, their order and a length limit; the tone; what to do when there is nothing to report; and what the skill is not for. Then write the SKILL.md with a header holding only a name (lowercase, with hyphens) and a description. The description must say when to use the skill and what it is not for. Add these rules: the result is a draft and is never sent; use only numbers from the sources; say at the top if a source is missing.

Review this SKILL.md before I install it:

[paste your SKILL.md]

List every problem you find under these headings: vague sources, a missing time period, an output format that is not fixed, no rule for missing data, no rule for when to stay silent, a description without a "not for" clause, and anything that names one product’s tools. Do not rewrite the file. List the problems and suggest one fix for each.

---
name: larkfield-status-report
description: Drafts the Friday status report for the Larkfield Supply leadership team from this week’s shipment log, supplier notes and team updates. Use when asked for the weekly or Friday status report. Not for customer emails, board reports or monthly finance summaries.
---

# Friday status report

## Sources
Read only these, for the current week (Monday to Friday):
1. The shipment log spreadsheet in the Operations folder.
2. The Supplier Updates document.
3. Team updates in the #ops-weekly channel.

## Output
A draft with four sections, in this order:
1. Headline: one sentence on the week.
2. Shipments: the on-time rate and any late orders, with order numbers.
3. Suppliers: delays or changes, with the supplier name and the expected date.
4. Decisions needed: anything the leadership team must decide, or "None this week".
Keep the draft under 300 words. Write plain sentences.

## Rules
- This is a draft for Dana to check. Never send it.
- Use only numbers that appear in the sources. Never estimate.
- If a source is missing or empty, say so at the top of the draft.
- If nothing changed in a section, write "No change this week".
- End with a list of the sources you read.

Here is the SKILL.md for a recurring task:

[paste your SKILL.md]

Map it to four building blocks. Skill: anything the instructions still need. Connections: list each source it must read, and nothing more. Schedule: when it should run, and how long I need to check the draft before it is due. Actions: what the assistant may do with the result. The result must stop at a draft, so list any action I should leave turned off. Then list what each block needs from my plan, and what I should check on the vendor’s current pages.

Use the [your-skill-name] skill to draft this week’s [task name]. Attached is a past example that shows the format I want. Follow its length, order and tone. Use only the sources named in the skill. If any source is empty or you cannot read it, say so at the top of the draft. Save the draft and do not send it.

Here is your draft:

[paste the draft]

Here is what I would have sent:

[paste your version]

List every difference. For each one, say whether it comes from a vague instruction in the skill, a missing source, or a matter of taste. For the first two kinds, suggest an exact change to the skill or to its sources.

Here is my SKILL.md:

[paste your SKILL.md]

Add these rules to it, without changing anything else: the result is a draft and is never sent; end the draft with a list of the sources read; if a source is empty or cannot be read, say so in the first line; if nothing changed in a section, write "No change this week"; give a reason or cause only when a source states it. Show me the full updated file.

Here is how my automation works: [describe the skill, its sources, its schedule and where the draft lands]. List every way it could fail without telling me. For each one, say how I would notice and what check would catch it sooner.

Here is my log from the last two weeks of an automated task:

[paste your log: date, minutes spent reviewing, edits made, anything unusual]

List where the drafts needed the most edits, and group the edits by cause. For each group, suggest one exact change to the skill or its sources. Then say whether review time is falling, flat or rising.

This product change was just announced: [paste or describe the change]. Here is my record of automations: [paste your records]. List which automations it could affect and what I should test for each, starting with the one most likely to break.

Here is my SKILL.md:

[paste your SKILL.md]

Rewrite it two ways. First, as a Microsoft 365 Copilot scheduled prompt: keep the sources, output and rules, and drop the header. Second, as a Gemini skill: keep the file as it is, and list anything Gemini may not support. In both versions, keep these rules: the result is a draft and is never sent; use only numbers from the sources; say when a source is missing. Then list every source I must reconnect, and what it is likely called in each product.