The most useful skill for your AI assistant is often the one that fixes a correction you keep making. A meeting brief forgets your last promise. A customer reply invents a fix date. A checklist leaves out who does the work.
For these tasks, start with five skills: Sales call preparation, Support ticket triage, Research synthesis, Business process documentation, and Word document creation. Give them your notes, messages, or records. Ask for a clear deliverable, then check the facts and open decisions before using it.
You do not need all five. Choose the one that matches a task you repeat. If you want a first exercise with no account connections, start with Business process documentation and turn rough notes into a checklist.
Choose a skill by the work you need done
These five options are listed in the JuicyAgents AI skills directory. This shortlist focuses on Anthropic's skills.
Scroll sideways to see all columns.
| Your recurring task | Skill to explore | Input to prepare | Result to review |
|---|---|---|---|
| Prepare for a client call | Sales call preparation | Meeting details and earlier notes | Brief with commitments and open questions |
| Handle a customer issue | Support ticket triage | Customer message and your support rules | Suggested next step and reply draft |
| Answer a question from several records | Research synthesis | Source records with dates and authors | Answer with sources and conflicts |
| Explain a routine to someone else | Business process documentation | Rough steps, roles, and exceptions | Checklist with clear responsibilities |
| Deliver an editable report | Word document creation | Approved content and layout needs | A usable .docx file |
How we chose them: We reviewed the authors' instructions and the directory's source entries on 5 October 2026. We have not tested these skills in a live business. Every task and output below is a fictional example to help you run your own trial.
What an AI skill adds to your assistant
An AI skill is a reusable set of instructions and resources for a compatible AI tool. In the Agent Skills format, it is a folder with a SKILL.md file. It may also include scripts, templates, and reference files. The assistant can load the instructions when they match the task. Agent Skills overview
A saved prompt can be enough for a simple request. Consider a skill when you keep repeating several steps or need templates and file tools. You still supply current facts and business rules.
Before adding one, check three parts:
- Assistant support: Can your AI tool load this skill or its parent plugin?
- Required tools: Can it read the needed records or create the required file?
- Your instructions: Have you supplied the real owners, deadlines, and rules?
Four picks belong to Anthropic's knowledge-work plugins. The Word skill is in its separate Skills repository. Follow the author's setup notes and our guide to adding agent skills. Installation happens in your chosen AI tool.
1. Sales call preparation: remember what you promised
Skill: call-prep · Package: Anthropic Sales plugin
Use this when preparing for a customer meeting means searching through earlier conversations. The skill brings together meeting details, account history, past commitments, and suggested questions. Its instructions support uploaded files and pasted notes as well as connected business tools. Author's call-prep instructions
Try it with a missing budget
Prepare a one-page brief using only these sample notes. I am the project lead. My call with Northstar Studio is on 8 October 2026 at 10:00 Europe/Warsaw. I will meet founder Alex. Alex asked for a simpler website menu. I promised to bring two menu options. We have not discussed budget. Include confirmed facts, what I must bring, and questions to ask. Do not search for extra information.
A useful illustrative brief would include:
- Confirmed: Call with Alex on 8 October at 10:00 Europe/Warsaw; the client wants a simpler menu.
- Bring: Two menu options, as promised by the project lead.
- Open question: What budget should guide the next proposal?
Check the date, time zone, and commitment against your input. Any budget figure or claim that Alex approved a budget would fail the task.
Setup: Pasted notes are enough for this exercise. To gather live context, connect the relevant calendar, customer records, or conversation sources. Check which sources the brief actually used. A source it could not read is a gap to resolve before the call.
2. Support ticket triage: choose the next step before replying
Skill: ticket-triage · Package: Anthropic Customer Support plugin
Use this when a customer issue needs a category, suggested priority, owner, and first reply. With suitable connections, the skill can check related tickets and known issues. Author's ticket-triage instructions
The source includes default teams and response targets. Replace or override them with your actual support rules before using the output. A template's reply target is not a promise your business has made.
Try it before the cause is known
Triage this sample email: “My report export has failed twice today. I can still view the dashboard, but I need the report for tomorrow's meeting.” Our first contact is Maya in support. She collects details before sending the issue to a technical team. No investigation has started, no workaround is confirmed, and no fix time is known. Suggest urgency with reasons. Draft a reply under 100 words. Do not send, assign, or update anything.
An illustrative assessment could say:
Issue: Report export fails; dashboard is still available.
Suggested category: Data/export issue; cause unconfirmed.
Urgency: Needs prompt review because the report is needed tomorrow.
First contact: Maya, following the supplied support rule.
Unknown: Error details, cause, workaround, number of users affected.
Next step: Ask which report fails and what error appears.
A matching illustrative reply:
Thanks for flagging this. I understand you need the report for tomorrow's meeting. Which report are you exporting, and what happens when the export fails? If an error message appears, please share its text. These details will help us identify the next step.
Review both parts. The assessment should explain urgency without assuming a wider outage. The reply should avoid claims that a team is investigating or that a fix will arrive tomorrow. Those facts are unknown.
Setup: Start with a pasted message. Add support-system connections when checking ticket history or known issues becomes part of the task. If those sources were not checked, the output should say so.
3. Research synthesis: resolve conflicts without hiding them
Skill: knowledge-synthesis · Package: Anthropic Enterprise Search plugin
Use this when the answer is spread across several records. The skill combines search results, removes repetition, keeps source references, and considers source authority and age. Its source defines it as a background skill inside the plugin, not a separate user command. Author's knowledge-synthesis instructions
Try three records that disagree
Supply these fictional records:
Scroll sideways to see all columns.
| Source | Date | Recorded information |
|---|---|---|
| A: Planning draft | 1 October 2026 | Launch on 12 October |
| B: Project owner's decision | 3 October 2026 | Launch moved to 15 October |
| C: Team chat | 4 October 2026 | Repeats 12 October; records no new decision |
Then ask:
Using only records A, B, and C, what is the best-supported launch date? Answer in under 100 words. Name the source of the decision and any conflict that needs follow-up.
An illustrative answer:
The best-supported launch date is 15 October, based on the project owner's decision in record B, dated 3 October. Record A lists 12 October. Record C repeats 12 October later, but contains no new decision. Confirm the date with the project owner and update the shared plan before announcing it.
A newer message can repeat an older decision. Counting two mentions of 12 October would also miss the explicit change by the project owner.
For a harder exercise, remove the author's role from record B. The assistant should explain that the authority of the change is unclear.
Setup: Use the Enterprise Search plugin's search flow for live work. Relevant source connections are needed to retrieve records. Pasting this small example lets you assess the answer style, but does not test search coverage or prove the background skill loaded.
4. Business process documentation: make gaps visible in the checklist
Skill: process-doc · Package: Anthropic Operations plugin
Use this when a routine lives in someone's head. The skill structures a process around purpose, steps, responsibilities, timing, outputs, and exceptions. It accepts rough descriptions and existing documents. Author's process-doc instructions
Try a routine with an unassigned step
Create a one-page checklist for client meeting preparation. I am the project lead and approve the agenda. Maya checks the meeting date and reads the previous notes. If she cannot find the notes, she asks me before drafting begins. We have not agreed who writes the agenda. Show missing decisions; do not fill them in. Return a draft only.
An illustrative checklist could look like this:
Scroll sideways to see all columns.
| Step or condition | Action | Owner | Result or open decision |
|---|---|---|---|
| Start preparation | Check the meeting date | Maya | Date checked |
| Read previous notes | Find and read the notes | Maya | Earlier context available |
| Notes are missing | Ask the project lead; pause drafting | Maya | Missing context needs a decision |
| Notes are available | Draft the agenda | To confirm | Agree who writes it before this step |
| Draft is ready | Review and approve the agenda | Project lead | Approved agenda |
The missing writer is part of the result. Assigning the task to Maya because she already handles other steps would hide a team decision.
Ask another person to follow the checklist using a sample case. Where do they stop? Use those questions to improve the steps and settle open responsibilities before sharing it.
Setup: Begin with your own notes. Connections can help find existing documents. The source also describes publishing to a wiki and creating tasks when connectors are available. Keep the first exercise as a draft, then decide where the approved checklist belongs.
5. Word document creation: deliver a file that works
Skill: docx · Package: Anthropic Skills repository
Use this when the deliverable is an editable Word file. The skill covers creating, reading, and editing .docx documents. It includes layout guidance and instructions to render and inspect the finished output. Author's docx instructions
Try an action table with an open decision
Create an editable, one-page Word meeting record from these sample notes. I am the project lead. We agreed to simplify the website menu. I will prepare two options by 12 October 2026. The client still needs to confirm the budget. We did not agree who will request that decision or when. Include an action table and mark missing owners and dates as “To confirm”.
The action table should preserve these facts:
Scroll sideways to see all columns.
| Action or decision | Owner | Due date |
|---|---|---|
| Prepare two menu options | Project lead | 12 October 2026 |
| Request budget confirmation from the client | To confirm | To confirm |
Review the document in two passes. First check meaning: the deadline belongs to the menu options, and the budget remains open. Then open the file in the editor you will use. Check the page count, headings, table cells, and whether you can edit the content.
A polished layout can make an invented owner look official. Approve the content before sharing the file.
Setup: The assistant needs file access and document software. The source lists the docx JavaScript package, Pandoc, LibreOffice, and Poppler for its document workflow. Reading a skill file alone does not supply those tools. Confirm support in your chosen environment before starting.
Test the skill against the work you already do
Compare the skill with your current method, including a saved prompt if you already use one.
Run the same task in fresh conversations, once with your current method and once with the skill enabled. Keep the model, source material, tool access, and business rules the same where possible. Record differences you cannot control, such as a plugin adding extra tools.
Check the assistant's visible skill activity or logs if available. A message saying “I used the skill” alone is weak evidence. If you cannot confirm activation, record that limit; you can still compare the outputs.
Record these checks for both versions:
Scroll sideways to see all columns.
| Check | What to record | Example of a failed check |
|---|---|---|
| Facts | Wrong or invented details | Budget added without a source |
| Open decisions | Missing items and how they are marked | Unassigned agenda writer treated as confirmed |
| Requested output | Whether the result is complete and usable | Text returned when you requested a Word file |
| Review effort | Minutes checking sources and fixing the result | Extra time removing promises from a reply |
Reject a result with an invented commitment, even if it took less time to produce. Compare review effort among results that meet your basic checks.
Try three cases: a normal task, one with missing information, and one with a conflict. Repeat them with different inputs before trusting the method. A small trial helps you choose what to keep; it cannot prove reliability across all future work.
If the skill adds little, keep the simpler prompt. If it helps, try it again with your real templates and team rules.
Choose one task for this week
Pick the correction that costs you the most effort. Open the matching listing, read the source requirements, and try its sample task with fictional or suitable test data.
Find Business process documentation, write down one routine, and look for a missing step or owner. Settle those decisions before using the checklist.
Browse the AI skills directory when you have a clear task to improve.