BD nanoclaw-repl
Operate and extend NanoClaw, ECC's zero-dependency session-aware REPL, with persistent markdown-backed sessions and slash commands for model switching, skill loading, session branching, cross-session search, history compaction, and export. Use when running or extending scripts/claw.js, or when resuming, branching, compacting, searching, or exporting a NanoClaw session.
Promises to extend NanoClaw, a zero-dependency REPL with markdown-backed sessions and slash commands for model switching and skill loading. Single file with 177 tokens, broken references included. Grades B with safety 100 and quality 74—process score lags at 35. No model runs, no sandbox testing. The skill lists features but offers no evidence they work in practice.
If you already run NanoClaw and want to add functionality, this could work—it's safe and supports many platforms. Don't treat it as plug-and-play, though. Verify the broken links are fixed and test commands yourself before production use.
Operate and extend NanoClaw, ECC's zero-dependency session-aware REPL, with persistent markdown-backed sessions and slash commands for model switching, skill…
As a process D 35/100 · Unfinished process — References files that are not bundled: scripts/claw.js
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/claw.js
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/claw.js
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 177 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 371: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 15 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.