diff --git a/skills/live/SKILL.md b/skills/live/SKILL.md
index 5d888efc..63eb0501 100644
--- a/skills/live/SKILL.md
+++ b/skills/live/SKILL.md
@@ -9,7 +9,7 @@ metadata:
 # Live Browser
 
 > **PREREQUISITE:** Read `subtext:shared` for MCP conventions and sightmap upload.
-> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it before connecting — it specifies which MCP server prefix to use for live tools.
+> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it before connecting — it specifies which MCP server prefix to use for live tools, plus host-specific gotchas (local-app login/auth, patterns for testing locally-built code through subtext tools, screenshot strategy nuances, and similar).
 
 API catalog for live browser tools (all prefixed `live-`) on the unified subtext MCP server. These tools let you open browser connections, navigate views, interact with elements, and inspect console/network activity.
 
diff --git a/skills/recipe-reproduce-from-session/SKILL.md b/skills/recipe-reproduce-from-session/SKILL.md
index 21809817..e52108e9 100644
--- a/skills/recipe-reproduce-from-session/SKILL.md
+++ b/skills/recipe-reproduce-from-session/SKILL.md
@@ -9,6 +9,7 @@ metadata:
 # Recipe: Reproduce from Session
 
 > **PREREQUISITE:** Read `subtext:shared`, `subtext:session`, `subtext:live`, `subtext:sightmap`, and `subtext:tunnel`.
+> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it — it documents MCP prefix selection and host-specific gotchas (local-app login/auth, patterns for testing locally-built code through subtext tools, screenshot strategy, and similar).
 
 ## Steps
 
diff --git a/skills/reproduce-workflow/SKILL.md b/skills/reproduce-workflow/SKILL.md
index 86a9a037..a9195d93 100644
--- a/skills/reproduce-workflow/SKILL.md
+++ b/skills/reproduce-workflow/SKILL.md
@@ -9,6 +9,7 @@ metadata:
 # Reproduce
 
 > **PREREQUISITE:** Read `subtext:shared`, `subtext:session`, `subtext:live`, `subtext:sightmap`, and `subtext:tunnel` for MCP conventions and tools.
+> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it — it documents MCP prefix selection and host-specific gotchas (local-app login/auth, patterns for testing locally-built code through subtext tools, screenshot strategy, and similar).
 
 Drive the local app through live browser MCP tools to reproduce a user flow. When you encounter sightmap gaps, write back so the next run is better.
 
diff --git a/skills/tunnel/SKILL.md b/skills/tunnel/SKILL.md
index 66808826..34db0042 100644
--- a/skills/tunnel/SKILL.md
+++ b/skills/tunnel/SKILL.md
@@ -8,7 +8,7 @@ metadata:
 
 # Tunnel Setup for Hosted Browser
 
-> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it before connecting — it specifies which MCP server prefix to use for live and tunnel tools.
+> **ENVIRONMENT:** If a `subtext-environment` skill is available in the host project, read it before connecting — it specifies which MCP server prefix to use for live and tunnel tools, plus host-specific gotchas (local-app login/auth, patterns for testing locally-built code through subtext tools, and similar).
 
 When the hosted browser needs to load a page from the user's local dev server (e.g. `http://localhost:3000`), a reverse tunnel is required. The hosted browser cannot reach localhost directly — the tunnel proxies requests from the hosted infrastructure back to the user's machine.