diff --git a/src/resources/extensions/sf/prompts/scan.md b/src/resources/extensions/sf/prompts/scan.md
index 24871908d..49eb0b164 100644
--- a/src/resources/extensions/sf/prompts/scan.md
+++ b/src/resources/extensions/sf/prompts/scan.md
@@ -12,6 +12,7 @@ You are performing a focused codebase scan.
 
 ## Instructions
 
+0. {{skillActivation}}
 1. Explore the codebase to understand its structure, technology choices, and patterns
 2. For each document listed above, produce a well-structured Markdown file in `{{outputDir}}/`
 3. Use the document schemas below as a guide for each output file
@@ -79,5 +80,3 @@ For this scan, only these documents are relevant: **{{documents}}**. Refer only
 ### Report sf-internal observations
 
 This unit produces observations as its primary output — be especially diligent about filing sf-internal friction you notice along the way. If during this unit you observe sf-the-tool friction — ambiguous prompts, missing context, misleading instructions, surprising behavior, prompt-quality issues, or improvement ideas — file them via `sf_self_report` before sealing the unit. This is the only way these observations reach forge's backlog and get triaged. Over-reporting is preferred to under-reporting; dedup happens later. Do NOT use this to file bugs in the user's project; only sf-the-tool itself. Do NOT autonomously act on or fix existing backlog entries — your scope is your unit.
-
-{{skillActivation}}