{"id":44397,"plugin_id":"plugin_asdk_app_6a9b2ca24f4481918d44163552d6b2f1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:16:30.275Z","digest":"670bc55f29677090bb42d3cce7867c68901deecb03eaa25d1eac7a56d01e5aa1","against":null,"payload":{"description":"Find what the company's own help center, docs, policies and past support tickets say about a question. Use for questions like \"what's our refund window\", \"how do we handle damaged orders\", \"what did we tell customers about the outage\", or anything the user wants answered the way their company actually does it. Do not use for general knowledge that isn't specific to the user's company.","included_files":[],"name":"answer-from-company-knowledge","skill_md_contents":"---\nname: answer-from-company-knowledge\ndescription: \"Find what the company's own help center, docs, policies and past support tickets say about a question. Use for questions like \\\"what's our refund window\\\", \\\"how do we handle damaged orders\\\", \\\"what did we tell customers about the outage\\\", or anything the user wants answered the way their company actually does it. Do not use for general knowledge that isn't specific to the user's company.\"\n---\n\n# Answer from company knowledge\n\nThe outcome: the company's actual answer, with where it came from.\n\n1. Ask eesel through `chat`, adding context from this conversation (a product, a customer, an order).\n2. Relay the answer with any sources or links eesel cites.\n3. When the user has asked for their company's answer, give eesel's answer, not your own guess at how companies usually handle it.\n4. If eesel finds nothing, say so. It usually means the topic isn't in the connected sources. Offer to connect the missing source (set-up-ai-support) or to teach eesel the answer (fix-a-wrong-ai-answer).\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":{}}