{"id":51304,"plugin_id":"plugin_asdk_app_6ac51a7318048191981337c8880dd20d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:45:56.425Z","digest":"b8083fd75294a5398c61fac76f22aa0f39b1e08a9a3d3c8300f303288cdd0fc4","against":null,"payload":{"description":"Use the connected Flopinio workspace to find client context and carry requests, projects, tasks, notes, decisions, time, invoices, and approval-backed actions forward. Trigger when the user asks to inspect, summarize, plan, create, or update work in Flopinio.","included_files":[],"name":"flopinio-workspace","skill_md_contents":"---\nname: flopinio-workspace\ndescription: Use the connected Flopinio workspace to find client context and carry requests, projects, tasks, notes, decisions, time, invoices, and approval-backed actions forward. Trigger when the user asks to inspect, summarize, plan, create, or update work in Flopinio.\n---\n\n# Flopinio Workspace\n\nUse the Flopinio MCP server as the source of truth for workspace records.\n\n## Workflow\n\n1. Search or list before creating records so existing projects, tasks, notes, requests, and time coverage are reused when they already fit.\n2. Fetch the exact record before making a consequential update.\n3. Keep reads scoped to the connected user and workspace. Never infer record IDs, workspace membership, permissions, billing state, or private content.\n4. Use the narrowest tool that matches the requested action.\n5. Treat MCP work logs as delivery evidence, not billable time entries.\n\n## Writes And Approvals\n\n- Only create or update records when the user asks for the change or the write is an explicit step in the requested workflow.\n- Preserve useful existing descriptions and context when updating records.\n- Flopinio write tools normally stage approval-backed actions. Report an action as pending when the tool returns an approval or review URL; do not claim the record changed until execution is confirmed.\n- Keep invoice writes, approval resolution, and other financially significant or destructive operations explicit. Do not broaden their scope or bypass Flopinio approval controls.\n\n## OAuth Permissions\n\nFlopinio requests permissions per tool family, including separate read and write scopes for requests, tasks, notes, decisions, time entries, invoices, approvals, and runtime context. If a tool reports `insufficient_scope`, explain which permission is needed and let the user reconnect or grant that scope.\n\n## Response Style\n\nLead with the workspace outcome. Include stable record names and links returned by Flopinio, distinguish confirmed changes from staged approvals, and keep operational detail concise.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}