Prompt Library

I have a CSV of chargeback cases with columns: Case_ID, Scheme, Date_Received, Current_Stage. Calculate the response deadline for each case: Visa = 30 days, Mastercard = 45 days, AMEX = 20 days from Date_Received. Add columns: Deadline_Date, Days_Remaining, Urgency (Overdue / Urgent / This Week / Pipeline). Sort by Days_Remaining ascending. Output as Excel with RED for Overdue, YELLOW for Urgent (under 3 days).

I have a pipeline CSV with: Deal_Name, Company, Stage, Deal_Value, Last_Contact_Date. Create a one-page pipeline snapshot: total value, deal count by stage, stale deals (no contact 14+ days) with value at risk, and top 3 deals by value with their current stage and days since contact. Format as markdown. Flag anything stale in bold.

I have a Zendesk ticket CSV with: Ticket_ID, Priority, Created_Date, Status, Assigned_To, SLA_Target_Hours. Calculate hours open and SLA remaining for each ticket. Create an Excel workbook: Sheet 1 -- SLA Breach Risk (tickets within 25% of target), Sheet 2 -- Unassigned tickets sorted by priority. RED for breached, YELLOW for at risk.

I have a CSV of AML screening alerts classified as LIKELY FALSE POSITIVE with columns: Alert_ID, Merchant_Name, Risk_Score, Match_Name, Match_Details, Rationale. For each alert, generate a closure-ready review note with: the AI rationale, analyst verification checkboxes (name match verified, no corroborating identifiers, KYC file reviewed), and a recommendation (Close or Reclassify). Output as markdown with checkboxes.

I'm pasting raw meeting notes. Extract: (1) action items as a table with Owner, Due Date, Priority, Status columns -- mark unclear items as TBD, (2) decisions made with who approved and reasoning, (3) open questions with suggested follow-up owner. Do not invent information. Mark ambiguity with [UNCLEAR FROM NOTES].

[Paste notes here]

Help me build my CLAUDE.md. Ask me 5 questions:
1. What is my role and department?
2. What tools do I use every day? (Name each one and what I use it for)
3. What terminology or acronyms does my team use that outsiders would not know?
4. How do I want my outputs formatted? (File type, word limits, structure)
5. What data should NEVER be processed by AI in my role?

Then generate a complete CLAUDE.md file I can save to my workspace root.

I want to build a custom Cowork skill. Here is my task:

**Task name:** [what you call this task]
**How often:** [daily/weekly/monthly]
**Current time:** [how long it takes manually]
**Input:** [what data or information do you start with]
**Output:** [what do you need at the end]
**Steps:** [describe what you do, step by step]
**Rules:** [any constraints, formatting requirements, or safety rules]

Use /skill-creator to turn this into a reusable skill.

I am about to use this AI-generated output in production. Before I do, run it through the 5 Failure Mode checks:

1. **Math check:** Are all numbers, totals, and percentages correct? Verify against source data.
2. **Classification check:** Are all categories, codes, and priority levels correctly assigned?
3. **Confidence check:** Does the output make claims without evidence? Flag any "definitely" or "clearly" statements.
4. **Red flag check:** What patterns or anomalies might be missing from this output?
5. **Source check:** Does every data point trace back to the correct source file, scheme, or time period?

Tell me what passes and what needs manual verification.

[Paste the output to verify]

I manage a team that uses Cowork. Help me audit our skill library:

1. List all skills in .claude/skills/ with their names and descriptions
2. For each skill, check: when was it last modified? Does it reference outdated tools, deadlines, or processes?
3. Flag skills that overlap (doing the same thing with different names)
4. Flag skills that reference tools we no longer use
5. Suggest which skills should be retired, merged, or updated
6. Recommend 3 new skills based on common team tasks that are not yet automated

Format as a table I can review with my team.

I need a skill that does not exist yet. Help me write a skill request I can share with my team or post in our department Slack channel:

**What I need automated:** [describe the task]
**How often I do it:** [frequency]
**How long it takes manually:** [time estimate]
**What the input looks like:** [describe the data you start with]
**What the output should look like:** [describe what you need]
**Who else would use this:** [which roles or teams]

Format this as a concise request with a clear "value proposition" -- why building this skill is worth the 20 minutes it takes.