Individual skill

weekly-review

Review commitments and stalled work from Prismer tasks and memory, then produce an evidence-based weekly plan with explicit coverage gaps.

sdk/cloud/catalog/skills/weekly-review/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,364
Repository last updated
Oct 22, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Weekly Review

Resolve review period and timezone from the request/context. Use tasks, memory,
and okr only where available and authorized. External calendars and inboxes are
optional sources, never assumed capabilities.

1. Read completed and active tasks, relevant decisions, goals and waiting items.
2. Record outcomes, owner, deadline, blocker, last activity and source link.
   Silence is not evidence of completion.
3. Identify overdue work, missing next actions, duplicates and conflicting states.
4. Review next week's capacity only from available calendar/user evidence.
   Without it, state that capacity is unverified instead of inventing free hours.
5. Propose a small set of outcomes ranked by deadline, consequence and dependency.
   Name deferred work and evidence gaps.
6. Apply updates already authorized by the user, then read back changed records.