{"id":44406,"plugin_id":"plugin_asdk_app_6a9b2ca24f4481918d44163552d6b2f1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:16:30.646Z","digest":"26b7635f46c631cd05e054239fdf1dbb63dd42ddad9dfa2a95418294fd29bd6a","against":null,"payload":{"description":"Write or update help center articles, FAQs, macros and canned replies from the questions customers actually ask, using the company's past tickets and existing docs. Use when the user wants to reduce repeat questions, fill gaps in their help center, or turn a common support answer into an article or macro. Do not use when the company has no support history or docs to draw on.","included_files":[],"name":"write-help-center-articles","skill_md_contents":"---\nname: write-help-center-articles\ndescription: \"Write or update help center articles, FAQs, macros and canned replies from the questions customers actually ask, using the company's past tickets and existing docs. Use when the user wants to reduce repeat questions, fill gaps in their help center, or turn a common support answer into an article or macro. Do not use when the company has no support history or docs to draw on.\"\n---\n\n# Write help center articles\n\nThe outcome: articles that answer what customers really ask, in the company's voice.\n\n1. Agree which topic or gap. If the user doesn't know, start with find-what-customers-ask-about.\n2. Ask eesel through `chat` to draft the article from the relevant past tickets and existing docs, and to say what it based it on.\n3. Show the draft and where eesel says it saved it. Drafts usually go to the user's eesel files, which `files` lists.\n4. Publishing into the help center depends on the connected helpdesk. Ask eesel whether it can publish there, and publish only if the user asks.\n\n## Working with eesel\n\n- eesel is the company's AI teammate. It works from the company's connected helpdesk, help center, docs and past tickets, so its answers follow this company's policies and tone, not general best practice.\n- Ask it through `chat`, in the user's words, with every specific they gave. Relay its reply faithfully: don't rewrite it into your own answer or add facts it didn't give.\n- Pass the reply's `task_id` back on follow-ups about the same thing. If a reply says eesel is still working, tell the user it is on it, and collect the result with `chat` and only that `task_id` when they ask. Don't poll in a loop. If it is still working after three collection attempts, call `status`: if the trial has ended or credit has run out, tell the user that is why.\n- If a reply says an action is waiting for approval, show the user what it would do. Call `decide_approval` only on the user's clear yes. A clear \"approve all\" covers only the actions they have just been shown.\n- If eesel has no helpdesk or knowledge connected yet, use set-up-ai-support first.\n- Never ask the user to paste passwords or API keys into this conversation.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}