{"id":85873,"plugin_id":"plugin_asdk_app_6ad611088870819195ee8f37d67ad51f","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-07T13:28:54.531Z","digest":"6936914195038a5462de6d44809bca9e71045beed57d68b68bab84def09d0484","against":null,"payload":{"description":"Use MonkAndMonkey tasks, goals, habits, journals, streaks, life areas, tracked time, analytics, and productivity briefs through the hosted MCP.","included_files":[],"name":"monkandmonkey","skill_md_contents":"---\nname: monkandmonkey\ndescription: Use MonkAndMonkey tasks, goals, habits, journals, streaks, life areas, tracked time, analytics, and productivity briefs through the hosted MCP.\n---\n\n# MonkAndMonkey\n\nUse the MonkAndMonkey MCP as the source of truth for the user's productivity data. Prefer existing summary and analysis tools over rebuilding aggregation in the conversation.\n\n## Daily brief\n\nFor a morning or daily brief, request the productivity brief and attention tasks. Keep the result compact and actionable:\n\n1. unfinished work from yesterday and overdue tasks;\n2. today's tasks and any active session;\n3. habits or streaks at risk;\n4. goals, projects, or life areas receiving unusually little attention;\n5. at most three concrete next actions.\n\nUse the user's requested date range and timezone. Include journal context only when the user asks for it.\n\n## Reads and analytics\n\n- Use reference-data tools before resolving human-readable areas, projects, tags, or units.\n- Use the server's named/custom date ranges and daily or entity grouping instead of manually recomputing totals.\n- Distinguish facts returned by MCP from interpretation. Do not invent activity for empty periods.\n- Keep large task and journal lists bounded; offer to drill into one area.\n\n## Writes\n\n- Create or update tasks, habits, and journal entries only when the user explicitly asks.\n- Use stable record IDs. Resolve an ambiguous name before writing.\n- For task completion and planning moves, let the protected API enforce valid state transitions.\n- For habit logs, preserve the requested local date, tracking type, unit, and value semantics.\n- Summarize exactly what changed after a successful write.\n\nNever perform deletion, arbitrary HTTP requests, direct database access, or session control. If a requested action has no narrow MCP tool, explain the boundary and offer the closest safe supported action.\n\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}