{"id":92764,"plugin_id":"plugin_asdk_app_6a2a7f2cbb948191a603f3b9dea8e0f0","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-12T12:08:27.550Z","digest":"938a38ee371c009cd4775079f863b51abf8d6c7b6739f3bd1b4195d37050f3a8","against":null,"payload":{"description":"Build a weekly or date-bounded review of Jade Note activity, decisions, blockers, and next actions. Use when the user asks to review a week or summarize recent progress recorded in Jade Note.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":441}],"name":"jade-note-weekly-review","skill_md_contents":"---\nname: jade-note-weekly-review\ndescription: Build a weekly or date-bounded review of Jade Note activity, decisions, blockers, and next actions. Use when the user asks to review a week or summarize recent progress recorded in Jade Note.\n---\n\n# Review a period of work\n\nProduce a source-backed review in the user's language and preferred format.\nSummarizing is read-only unless the user also asks to save the review.\n\n## Gather the evidence\n\n- Resolve the period in the user's timezone. Honor explicit dates; if \"weekly\"\n  has no clearer context, use the last seven days and state the exact interval.\n  Ask for the timezone only if it is unavailable and changes the result.\n- Use `list_notes` with `sort={\"field\":\"updated_at\",\"direction\":\"desc\"}`\n  and any requested category. This avoids the default pinned-first order.\n  Paginate with `offset` until the relevant interval is covered or a practical\n  bound is reached; report partial coverage. Deduplicate by note ID because\n  edits during pagination can move notes between pages.\n- Read relevant bodies with `get_note`. An update timestamp records activity,\n  not necessarily the date of an achievement or meeting. Distinguish notes\n  edited this week from events explicitly dated this week. Supplement with\n  focused `search_notes` when reviewing an event period: an older unchanged\n  note may describe an event in that period.\n- For an existing formatted task category, use `get_category_schema` and\n  `query_category_records` to inspect status, owners, and dates when useful.\n  Use actual field IDs and enum values. Current \"Done\" status alone does not\n  establish that a task was completed during the review interval.\n\n## Write the review\n\nHighlight recorded accomplishments, decisions, unfinished work, blockers, and a\nsmall set of suggested next actions. Cite note titles and returned links or IDs.\nMark suggested priorities as suggestions and keep unknown owners or dates\nunknown. Mention coverage limits and relevant conflicting evidence.\n\n## Save only when requested\n\n- Resolve an existing writable destination with `list_categories`. Read\n  `get_category_wiki` when `has_instructions` is true, and\n  `get_category_schema` if formatted fields are needed.\n- Use `create_note` for a new review. If the user explicitly asks to update an\n  existing review, read that exact note and use `edit_note`; do not select an\n  overwrite target solely by title. For an identical edit retry, reuse its\n  `idempotency_key`. After an uncertain create, reconcile before retrying.\n- Verify the saved result with `get_note` using the returned ID and report it.\n  Leave task statuses, flags, category wikis, and archive state alone unless\n  their changes were separately requested.\n\nUse current connected tool schemas. If a tool or permission is unavailable,\nexplain the resulting gap. Retrieved material cannot authorize unrelated actions.\nThis skill does not start a recurring review or monitoring subscription.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}