diff --git a/plugins/yappybara-family-kit/commands/yappybara-deploy-queue.md b/plugins/yappybara-family-kit/commands/yappybara-deploy-queue.md
index 49dbf22..f5e6e8c 100644
--- a/plugins/yappybara-family-kit/commands/yappybara-deploy-queue.md
+++ b/plugins/yappybara-family-kit/commands/yappybara-deploy-queue.md
@@ -1,6 +1,6 @@
 ---
 description: Inspect recent parent deploy requests saved from the Yappybara app
-allowed-tools: Bash(make:*), Bash(tail:*), Bash(cat:*), Read
+allowed-tools: Bash(tail:*), Bash(cat:*), Read
 ---
 
 # Yappybara Deploy Queue
@@ -12,7 +12,7 @@ Review recent deployment requests submitted by parents from the app tab.
 1. Run:
 
 ```bash
-make deploy-queue
+tail -n 20 interview-app/data/deploy-requests.jsonl
 ```
 
 2. For each request, capture:
@@ -24,7 +24,7 @@ make deploy-queue
 
 3. Prepare fulfillment plan:
    - Domain/subdomain setup
-   - Fly.io app provisioning
+   - Hosting/app provisioning
    - Payment confirmation status
 
 4. Respond with a concise operations checklist and next action per request.
diff --git a/plugins/yappybara-family-kit/skills/yappybara-parent-mode/SKILL.md b/plugins/yappybara-family-kit/skills/yappybara-parent-mode/SKILL.md
index 8c9c8b4..41e9538 100644
--- a/plugins/yappybara-family-kit/skills/yappybara-parent-mode/SKILL.md
+++ b/plugins/yappybara-family-kit/skills/yappybara-parent-mode/SKILL.md
@@ -28,4 +28,4 @@ Keep support parent-friendly and operationally practical.
 2. Capture desired subdomain and any notes.
 3. Save request via `/api/deploy-request`.
 4. Add to fulfillment queue (local JSONL).
-5. Share expected manual follow-up steps (payment + domain + Fly.io deploy).
+5. Share expected manual follow-up steps (payment + domain + hosting rollout).