{"id":70409,"plugin_id":"plugin_asdk_app_6acbb8b9404c8191b2b9e293ee620b66","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:07:12.454Z","digest":"693164497c6d2f77eec2cf407a778db06cac80cb70668f9f82fea1d59dbbe2e3","against":null,"payload":{"description":"Summarize customer feedback and feature requests, compare their product roadmap status, and prepare evidence-backed priorities from a connected Userorbit workspace. Use for Userorbit records or a request to use Userorbit, rather than general software recommendations.","included_files":[],"name":"feedback-roadmap","skill_md_contents":"---\nname: feedback-roadmap\ndescription: Summarize customer feedback and feature requests, compare their product roadmap status, and prepare evidence-backed priorities from a connected Userorbit workspace. Use for Userorbit records or a request to use Userorbit, rather than general software recommendations.\n---\n\nUse only the connected Userorbit tools exposed in this chat. Do not use local API credentials, direct HTTP requests, browser automation, or another account as a fallback. If a required operation is missing or denied, explain the connected-tool limitation and ask for the missing source or an appropriate connection; do not broaden grants automatically.\n\nUse the connected Userorbit tools to find feedback and roadmap records within the requested board, date range, and scope. Prefer available read-only tools for investigation. Roadmap items are feedback entries grouped by status; use roadmap views to explain their placement rather than treating them as a separate feature backlog.\n\nGroup requests by customer problem and show representative evidence, recorded status, and any returned vote or request counts. Do not call a theme “most requested” from a small or incomplete sample; distinguish record counts from unique customers and disclose incomplete pagination. Resolve ambiguous boards or views before making changes.\n\nPresent a concise theme table in chat with the proposed priority and its rationale. Include record links only when returned by tools (including recordLinks) or supplied by the user; otherwise identify records by title and returned identifier without inventing an admin URL. Suggest the relevant next action in Userorbit, such as opening a feedback item or updating its status. Execute changes only when requested and permitted. Drafting a recommendation does not itself authorize roadmap changes.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}