Do this with your agent
Five procedures your assistant can follow against your ShowPilot workspace — read the week, answer what nobody could answer, brief an account, launch an offer, work the leads.
Connect the MCP server and your assistant can reach every operation in the API. That tells it what is possible. A skill tells it what to do — the order of calls, what to show you before writing anything, and what not to guess.
Each skill below is one Markdown file. Download it, drop it where your assistant reads skills, and ask for the job by name.
The library
| Skill | Ask for it like this | What it does |
|---|---|---|
| Weekly review | "How did the agent do this week?" | Reads the window against the one before, the questions nobody answered, and the warm accounts. Writes a short review. |
| Answer the gaps | "What are people asking that we cannot answer?" | Clusters the unanswered questions, drafts knowledge for the ones you can answer, and says which need a person. |
| Brief me on an account | "What has Acme been looking at?" | The company card, the people, what they asked, and the one question to open the call with. |
| Launch an offer | "Put an offer up for the June webinar." | Drafts the copy and the gates from a sentence, shows you what it guessed, then creates it switched off. |
| Follow up on leads | "Who came in, and what should I send?" | Leads with their journeys, open promises first, and one specific next action each. |
Installing one
Save the file under .claude/skills/ in one repository, or ~/.claude/skills/ to have it everywhere:
mkdir -p ~/.claude/skills/showpilot-weekly-review
curl -o ~/.claude/skills/showpilot-weekly-review/SKILL.md \
https://www.showpilot.com/developers/skills/weekly-review.mdWhat they have in common
Every skill starts with whoami, because nothing else is safe until the workspace is settled. If you belong to several organizations and your client connected before it could ask you to pick one, reads run against a default and writes refuse — the skill stops and asks rather than writing to a guess.
Every skill that writes shows you the draft first. draft_offer and propose both write nothing at all, which makes "show me what you would do" a real step rather than a promise.
And none of them asks ShowPilot to think for you. The tools return figures and the visitor's actual words; your assistant does the reasoning on your own subscription. That is why find_knowledge_gaps hands back questions rather than themes — you will group them better than a pattern would.
Writing your own
A skill is a Markdown file with a name and a description in its frontmatter and a procedure in its body. The ones above are worth copying for shape: numbered steps naming real tools, then a short list of rules that say what not to do. The rules matter more than the steps. An assistant works out the order on its own; what it cannot work out is that a CRM gate fails closed, or that an open follow-up outranks a cold lead.
Start from the tool list, and ask your assistant to run whoami and describe_api while you write — it can read its own permissions and the exact input every operation takes.