← UserorbitCONTENT HISTORY
WHAT CHANGED
Update to Userorbit
Snapshot Oct 29, 2026 · 12:07 UTC · version 1.0.15
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Userorbit and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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"
}SHA-256 of public snapshot: 693164497c6d2f77eec2cf407a778db06cac80cb70668f9f82fea1d59dbbe2e3