From 72eec189b566af77672c6521934786dd16a2dcbf Mon Sep 17 00:00:00 2001
From: Dotta <bippadotta@protonmail.com>
Date: Fri, 7 Aug 2026 20:30:44 +0000
Subject: [PATCH] fix(skills): correct rejection wake guidance

---
 .../prepare-mcp-integration/SKILL.md                | 13 ++++++-------
 packages/skills-catalog/generated/catalog.json      |  8 ++++----
 2 files changed, 10 insertions(+), 11 deletions(-)

diff --git a/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration/SKILL.md b/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration/SKILL.md
index d1845bea3b9..a7ba10b3e02 100644
--- a/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration/SKILL.md
+++ b/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration/SKILL.md
@@ -134,15 +134,14 @@ open a second PR for the same connection accidentally.
    - known limitations, prerequisites, and deferred questions.
 2. Create a Paperclip `request_confirmation` interaction targeted at that issue
    document's latest revision. Use a revision-specific idempotency key and a
-   `wake_assignee` continuation policy so acceptance resumes implementation.
-   State in the interaction that a rejection must include a normal issue
-   comment with revision notes; rejection alone does not wake the assignee.
+   `wake_assignee` continuation policy so either acceptance or rejection wakes
+   the assignee. Ask the reviewer to include revision notes when rejecting.
 3. Put the issue in `in_review` and stop. Do not prepare App worktrees or code
    while the interaction is pending.
-4. On rejection, resume only after the reviewer adds the normal issue comment
-   that wakes the assignee. Revise Phase A only and present a new revision. If
-   the research PR head, gate document, or connection set changes,
-   withdraw/supersede the old confirmation and request a fresh one.
+4. On rejection, use the interaction response and any revision notes to revise
+   Phase A only and present a new revision. If the research PR head, gate
+   document, or connection set changes, withdraw/supersede the old confirmation
+   and request a fresh one.
 5. On acceptance, verify that the response still targets the latest gate
    revision and recorded PR head. Implement only the accepted connections.
 
diff --git a/packages/skills-catalog/generated/catalog.json b/packages/skills-catalog/generated/catalog.json
index 414a04bb31d..ad63e175690 100644
--- a/packages/skills-catalog/generated/catalog.json
+++ b/packages/skills-catalog/generated/catalog.json
@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "packageName": "@paperclipai/skills-catalog",
   "packageVersion": "0.3.1",
-  "generatedAt": "2026-08-07T20:23:46.413Z",
+  "generatedAt": "2026-08-07T20:30:29.973Z",
   "skills": [
     {
       "id": "paperclipai:bundled:docs:doc-maintenance",
@@ -1149,8 +1149,8 @@
         {
           "path": "SKILL.md",
           "kind": "skill",
-          "sizeBytes": 11285,
-          "sha256": "91c0dc05bf8808fb53acd02344d4ec813f20e6b3bbc43ef1824a78bedd170ee7"
+          "sizeBytes": 11183,
+          "sha256": "452386be3aa5e2988dc9d72f288f469975da766626a25c48017877963c533781"
         },
         {
           "path": "examples/notion-mcp-research-gate.md",
@@ -1159,7 +1159,7 @@
           "sha256": "944b13ac67c06c65643eb236e856f1479106749861535648d29334f84cf1b50b"
         }
       ],
-      "contentHash": "sha256:76fa5ea4dc61641469867ca01eddb4f0d62dc9e7cc568ed38dff4153888fa0e3"
+      "contentHash": "sha256:4dbb76624e0fd5502fa10a9168f77214c5020899838af887e77a1617a0a00c31"
     }
   ]
 }