liuyu/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-06-06 05:51:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs(skills): use neutral skill wording

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-17 10:56:22 +01:00
parent 7e2d6ef06f
commit bf51933358
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
skills/node-inspect-debugger/SKILL.md
View File

@@ -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.

4
skills/spike/SKILL.md
View File

@@ -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.