AssistantSupport
Answer a partner question, or escalate it cleanly
Ground a partner's technical question in the docs and internal knowledge: send a ready draft when it is covered, give a careful answer plus a copy-paste Dev Support ticket when it is only partial.
Updated
Before you start
- What you need
- The partner's question, your public documentation, and your internal knowledge base.
- Connector (MCP)
- Recommended. It searches your documentation and internal knowledge base directly, which is what keeps the answer grounded rather than guessed.
- Without a connector
- Paste the question and the doc pages you would have searched. It will only answer from what you gave it.
A connector, often called MCP, lets an assistant read your tools directly instead of you pasting. Set it up once, then it reads those tools on its own. How that is done differs per assistant, so check its own documentation.
How to try it
- Download the skill and unzip it. Inside are the instruction, the partner-draft and escalation templates, and a page on loading it.
- If your assistant reads skills, copy the partner-answer folder into the place it reads them from. If it does not, use Copy as text instead: that is the same instruction with both templates already inlined.
- Take a partner question you have already answered and compare its draft with what you sent.
- Check the draft to the partner carries no internal links and no account data, and that anything the docs do not cover becomes an escalation instead of a guess.
- Use it on live questions. Read every draft before it leaves.
Download to install it once. Copy to paste it into a chat.