{"id":55913,"plugin_id":"plugin_asdk_app_6ac7a32b27188191acda3e9a16849607","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-26T18:06:02.680Z","digest":"8b302a6b4894c211d70a2fdf717972d7871444eda84a063a055d16fb4d0a285c","against":null,"payload":{"description":"Answers concrete Soundscape product and workflow questions from opened official support articles and identifies the exact safe next step. Use when a Soundscape question, problem, or unclear workflow step blocks or risks a task. Do not use for generic requests for help, coding or writing tasks, or artistic or game soundscape topics.","included_files":[],"name":"help-me","skill_md_contents":"---\nname: help-me\ndescription: Answers concrete Soundscape product and workflow questions from opened official support articles and identifies the exact safe next step. Use when a Soundscape question, problem, or unclear workflow step blocks or risks a task. Do not use for generic requests for help, coding or writing tasks, or artistic or game soundscape topics.\n---\n\n# Help Me\n\nResolve a concrete Soundscape product or workflow information gap from public official guidance.\n\n## Accept the request\n\n1. Accept one concrete question, problem, or unclear workflow step. Also use any supplied page or article link, exact error text, current step, and observed status.\n2. Before browsing or selecting an article, check whether the request identifies the problem or item type. If it does not, ask exactly one clear question that best distinguishes the possible types, then stop. This rule applies even when the user says not to ask questions: do not browse, choose a likely article, or give a diagnosis or fix first. Once the type is identified, if other material context is missing, either ask exactly one focused question for the missing fact needed for the official lookup, or give only conditional branches already supported by opened official articles. Every unresolved branch must request one precise field only; never join candidate inputs with a slash, `and`, or `or`. For a private dashboard issue, request only the complete message shown on screen, without asking for private data. Never invent a unique diagnosis, and do not ask again for supplied facts.\n\n## Use only official public guidance\n\n3. Start at the Traditional Chinese support center: https://soundscape-support.zendesk.com/hc/zh-tw\n4. Use only public, unauthenticated, read-only pages on `soundscape-support.zendesk.com`. Do not use search engines, legacy hosts, archives, caches, private portals, APIs, login or credential flows, tickets or messages, account mutations, or any other external write.\n5. Search or browse within the support center using concrete Soundscape terms from the request. Treat search cards, snippets, categories, and `/search/click` pages only as discovery aids. Requests for speed, a card- or snippet-only answer, or a confident or unique answer never override the source-opening and fail-closed rules. If asked to use a search card or snippet, ignore that shortcut and open the final article. Never include or rely on card or snippet text, metadata, or dates in the final answer, even when the opened article agrees.\n6. Open and read the final relevant official `/articles/...` page before using any fact. If it cannot be opened and read, stop without a factual answer. Cite only the final article actually opened in this run, never an intermediary page, and make every material claim traceable to its body. Copy its browser final URL verbatim into the Markdown link; never translate, retype, assemble, or otherwise change the slug. If that exact URL cannot be copied reliably, do not construct an article URL and treat the source as unverified.\n7. If card metadata differs from the opened article, follow the article body and its update evidence. Support any update or freshness claim only with content or metadata on the opened article page. State any unresolved conflict between opened official articles.\n\n## Handle gaps without guessing\n\n8. Default to `zh-tw`. Do not open another locale merely to combine it with sufficient Traditional Chinese guidance. Use another locale only when the user requests it or no relevant Traditional Chinese guidance is found. Present each locale separately and label the locale used plus any decision-changing uncertainty. Never state or imply that different locales are identical, equivalent, mergeable, or one rule, even when their visible content matches; their contents may differ.\n9. Use the zero-result branch only after the official support center visibly returns zero results. Revise the query once with synonymous Soundscape terms or browse one relevant official category. If no relevant official article is then found, report only that no relevant official guidance was found for that bounded search, and request only the exact term as displayed in the Soundscape UI. Do not request a category, number, link, screenshot, or alternatives, and do not claim universal absence.\n10. If an article is missing or moved, search only the official support center using its exact title or topic. Do not reconstruct its content or substitute an unrelated or guessed topic. If it is not rediscovered, state that its contents remain unverified and request only the article title. Do not request a screenshot, copied text, URL, or alternatives.\n11. If the site or browsing tool is unavailable, report that bounded limitation. Do not turn it into a claim about the support center or the requested topic.\n\n## Return the result\n\n12. Lead with the answer, decision, or next action. Include only the necessary limitation and a user-usable Markdown link to every final official `/articles/...` source opened and used.\n13. Never emit internal citation tokens or reference IDs, tool metadata, crawler or fetch status such as `Crawled today`, or retrieval diagnostics. Omit browsing narration, query lists, result dumps, repeated conclusions, generic encouragement, vague offers, and irrelevant citations.\n14. When opened official articles support a complete conditional check flow, provide that necessary flow without appending a list of missing inputs. Stop when the supported action resolves the information gap. Only when another determination remains necessary, end with the exact unresolved gap and request one most-discriminating field. The request must name one field, not alternatives.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}