docs(skills): use neutral skill wording

steipete · steipete · commit bf519333588d · 2026-05-17T11:04:04.000+01:00
diff --git a/skills/node-inspect-debugger/SKILL.md b/skills/node-inspect-debugger/SKILL.md
@@ -6,7 +6,7 @@ metadata: { "openclaw": { "emoji": "🪲", "requires": { "bins": ["node"] } } }
 
 # Node Inspect Debugger
 
-Use when logs are too weak for a Node.js bug: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths.
+Use for Node.js debugging that needs inspector access: hidden locals, async hangs, flaky tests, child processes, startup races, memory growth, or CPU hot paths.
 
 Default to `node inspect` first. Use Chrome DevTools Protocol only when you need scripted breakpoints, automated state capture, heap snapshots, or CPU profiles.
 
diff --git a/skills/spike/SKILL.md b/skills/spike/SKILL.md
@@ -14,7 +14,7 @@ Loop
 
 1. Question: state the concrete feasibility question.
 2. Research: read enough docs/source to choose credible approach.
-3. Build: create the smallest runnable artifact that proves or kills the idea.
+3. Build: create the smallest runnable artifact that validates or invalidates the idea.
 4. Stress: try one edge case or failure mode.
 5. Verdict: `VALIDATED`, `PARTIAL`, or `INVALIDATED`.
 
@@ -46,6 +46,6 @@ Recommendation: ship / adjust / avoid, with the next production step.
 
 Rules
 
-- A failed spike is useful when it kills a bad path with evidence.
+- An invalidated spike is useful when it rules out a path with evidence.
 - Do not merge spike code into production without rewriting it normally.
 - If external dependencies are evaluated, check health: recent release/commit, docs, license, install friction.
