diff --git a/plugins/dotnet-experimental/skills/exp-dotnet-test-frameworks/SKILL.md b/plugins/dotnet-experimental/skills/exp-dotnet-test-frameworks/SKILL.md
index a8f0cb4004..fe4b2dde0f 100644
--- a/plugins/dotnet-experimental/skills/exp-dotnet-test-frameworks/SKILL.md
+++ b/plugins/dotnet-experimental/skills/exp-dotnet-test-frameworks/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: exp-dotnet-test-frameworks
-description: "Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. DO NOT USE directly — loaded by test analysis skills (exp-test-smell-detection, exp-assertion-quality, exp-test-maintainability, exp-test-tagging) when they need framework-specific lookup tables."
+description: "Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. Loaded by test analysis skills (exp-test-smell-detection, exp-assertion-quality, exp-test-maintainability, exp-test-tagging) as framework-specific lookup tables."
 user-invocable: false
 license: MIT
 ---
diff --git a/plugins/dotnet-test/skills/dotnet-test-frameworks/SKILL.md b/plugins/dotnet-test/skills/dotnet-test-frameworks/SKILL.md
index 8eaa2e47a5..cfde1b7dce 100644
--- a/plugins/dotnet-test/skills/dotnet-test-frameworks/SKILL.md
+++ b/plugins/dotnet-test/skills/dotnet-test-frameworks/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: dotnet-test-frameworks
-description: "Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. DO NOT USE directly — loaded by test analysis skills (test-anti-patterns, exp-test-smell-detection, exp-assertion-quality, exp-test-maintainability, exp-test-tagging) when they need framework-specific lookup tables."
+description: "Reference data for .NET test framework detection patterns, assertion APIs, skip annotations, setup/teardown methods, and common test smell indicators across MSTest, xUnit, NUnit, and TUnit. Loaded by test analysis skills (test-anti-patterns) as framework-specific lookup tables."
 user-invocable: false
 license: MIT
 ---
diff --git a/tests/dotnet-test/dotnet-test-frameworks/eval.yaml b/tests/dotnet-test/dotnet-test-frameworks/eval.yaml
index d663cf58c0..a60d44bcbd 100644
--- a/tests/dotnet-test/dotnet-test-frameworks/eval.yaml
+++ b/tests/dotnet-test/dotnet-test-frameworks/eval.yaml
@@ -1,5 +1,6 @@
 scenarios:
   - name: "Cross-framework assertion equivalence mapping"
+    expect_activation: false
     prompt: |
       I have these MSTest assertions in my test file and I need to know their equivalents in both xUnit and NUnit. Please provide a complete mapping for all six:
 
@@ -40,6 +41,7 @@ scenarios:
     timeout: 120
 
   - name: "Identify TUnit framework and its unique attributes"
+    expect_activation: false
     prompt: |
       I inherited a project with this test file and I'm not sure what testing framework it uses.
       Can you identify it and explain the key attributes?
@@ -89,6 +91,7 @@ scenarios:
     timeout: 120
 
   - name: "Replace try-catch with framework-native exception assertions"
+    expect_activation: false
     prompt: |
       My team lead says these tests should use proper exception assertions instead of try/catch.
       Can you refactor each one using its framework's native approach?
@@ -163,6 +166,7 @@ scenarios:
     timeout: 120
 
   - name: "Skip annotations across all four frameworks"
+    expect_activation: false
     prompt: |
       I maintain a solution with test projects using MSTest, xUnit, NUnit, and TUnit.
       I need to temporarily skip some tests in each project with a reason message explaining why.
@@ -192,6 +196,7 @@ scenarios:
     timeout: 120
 
   - name: "Convert NUnit lifecycle methods to xUnit equivalents"
+    expect_activation: false
     prompt: |
       I'm migrating this NUnit test class to xUnit. How should I convert the setup and teardown methods?
 
@@ -252,6 +257,7 @@ scenarios:
     timeout: 120
 
   - name: "Identify integration tests by markers and code patterns"
+    expect_activation: false
     prompt: |
       I have a test solution with hundreds of tests. I need to separate integration tests from
       unit tests for CI pipeline optimization. Here are samples from three projects — which ones