Help Center Writing
Help Center Writing: Write a support article that solves one customer task. Review the user question, product behavior, prerequisites, and current screenshots and produce a help article with steps and troubleshooting.
--- name: customer-support-help-center-writing description: Use for help center writing when asked to write a support article that solves one customer task; produce a help article with steps and troubleshooting. license: MIT metadata: author: Thrive category: customer-support --- # Help Center Writing ## When to use Use this skill for help center writing when you need to write a support article that solves one customer task. The expected result is a help article with steps and troubleshooting. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect the user question, product behavior, prerequisites, and current screenshots. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Read the customer's account history, exact failure, environment, urgency, policy, and prior promises. 2. **Decide.** Lead with the answer and order steps by what the user must do. 3. **Produce.** Build a help article with steps and troubleshooting from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Distinguish what support can resolve now from what needs escalation. Do not promise dates without an owner. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Acknowledge the customer's actual issue and state the next owned action. - Avoid promising a resolution or timeline that has not been verified. ## Verification Test the instructions against the current product. Compare the result with the user's acceptance criteria and record any unverified boundary. Provide the customer-facing response, internal case note, next action, and confirmation needed to close the case. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a help article with steps and troubleshooting. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->