> ## Documentation Index
> Fetch the complete documentation index at: https://resources.athenaintel.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Save your method as a skill
> A reusable skill that follows your checklist and can be corrected in one place.
In this episode, you'll save your team's review method as a skill. Then you'll use it in chat, and correct it in one place.
Every team has a way it reviews a dispute. Today it lives in a PDF, or in someone's head. A skill puts it where Athena can use it. Create a Skill, and name it Exception review. Athena turns that into a skill name: exception-review. The editor says it isn't valid yet, because it needs a description. Add one line on when to use it. Then write the instructions. Start from the checklist your team already follows, in plain steps. When the editor says the skill is valid, your changes are saved. Saved isn't the same as shared. That's next.
Right now this is a draft. Publish makes it the version your team uses. Click Publish, confirm, and wait for Skill published. The status changes from Not published to Published. From now on, edits you make stay as unpublished changes until you publish again, so a half-finished edit doesn't reach anyone.
Open a new chat, and @-mention the skill, the same way you mention a file. Then ask for the work: review dispute 1041 in the tracker. Read the answer against your checklist. Carrier and ID first. The billed amount against the contract rate. Evidence named by document. And one recommended action at the end. If it follows the steps, the skill is doing its job. You can also attach skills in Runtime Config, under Skill Assets. That applies to new sessions.
Sam points out the checklist also asks for the date a dispute was raised. Don't fix that in every chat. Fix it in the skill. Add the line, and the status shows Unpublished changes. Click Publish again. The button is still called Publish. Now test it properly: open a new chat and mention the skill again, because a fresh chat doesn't carry the old attachment. Ask for the same dispute. The new step is there. Correct once, and every chat after that gets it.
Quick check. You edited a published skill. When does your team get the change? When you click Publish again. Until then, it shows Unpublished changes.
An audit team writes its sampling method as a skill. Every auditor mentions it in their own chats, so the work comes back in the same shape. When a reviewer corrects the method, one person updates the skill and publishes it, and the next chat follows the fix.
Try it in your own workspace with this prompt. Look for Published in the skill's status row, and an answer that follows your steps in order.
## Before you start
Upload these files from the [Northwind starter kit](/docs/athena-101/starter-kit): **Northwind exception-review checklist.pdf** and all files in **Lesson 11**: the tracker, invoice, rate contract, and proof of delivery.
Create and publish the skill in Athena; uploading the checklist does not publish it. If publishing is unavailable, use the checklist directly in chat and compare the answer with its steps.
## Steps
Create a **Skill** from your checklist. Add a **Description** that says when to use it, then write the steps in plain words.
Click **Publish** and confirm. Check for **Published**; saving your draft alone does not publish it.
Open a fresh chat and @-mention the skill and tracker. Ask for one dispute review, then compare the answer with your checklist.
Add a missing step and click **Publish** again. Open another fresh chat, mention the skill again, and check that the changed step appears.
## Try it
> Create a skill from \[your team's checklist], publish it, then @-mention it and ask for one piece of work it should shape.
Look for **Published** and an answer that follows your steps in order.
## Next
[Give your team an agent, everywhere](/docs/athena-101/12-team-agent)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.