diff --git a/skills/week-review/SKILL.md b/skills/week-review/SKILL.md
index 8cd2054..3e5bf47 100644
--- a/skills/week-review/SKILL.md
+++ b/skills/week-review/SKILL.md
@@ -30,12 +30,15 @@ context.
 ```sh
 source ~/.env.claude
 curl -s -H "Authorization: token $GITEA_TOKEN" \
-  "https://git.naps.pt/api/v1/repos/yolo/agent-skills/issues?state=open&limit=50" \
+  "https://git.naps.pt/api/v1/repos/yolo/agent-skills/issues?state=open&labels=weekly-review&limit=50" \
   | python3 -c "import json,sys; [print(f\"#{i['number']} {i['title']}\") for i in json.load(sys.stdin)]"
 ```
 
-Ask which of them to take this week. Do not silently re-litigate one the user
-already deferred — a deferred item stays open and is mentioned in one line.
+Read the bodies, not just the titles — several carry a design already argued
+through, so the run starts from the open question rather than from scratch.
+
+Ask which to take this week. Do not silently re-litigate one the user already
+deferred; a deferred item stays open and gets one line in the summary.
 
 ## 2. Scan
 
@@ -115,12 +118,15 @@ secrets, no internal ticket IDs. Describe the shape of the problem, not the
 customer it happened at. When quoting the user as evidence, strip identifying
 detail first.
 
+Label every issue `weekly-review` (id 37) so step 1 picks it up next run. An
+issue filed without it is invisible to the next review.
+
 ```sh
 source ~/.env.claude
 curl -s -X POST -H "Authorization: token $GITEA_TOKEN" \
   -H "Content-Type: application/json" \
   "https://git.naps.pt/api/v1/repos/yolo/agent-skills/issues" \
-  -d '{"title":"...","body":"..."}'
+  -d '{"title":"...","body":"...","labels":[37]}'
 ```
 
 Close issues that got done this week, with a one-line comment saying what