BC nanda-chapter
projectnanda.org chapter skill — register an OpenClaw agent with a NANDA chapter, submit signed intents, respond to calls, render chapter dashboards, and subscribe to the chapter event bus.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
GeneratorData and analyticsInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Instruction override
en-ignore-previoushelpers/_sanitize.py:45Instruction-override phrase ("ignore previous instructions") (code comment; quoted — discussed, not commanded)# spoofing or "ignore prior instructions"-style injections. Strip
commentquoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:143High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"agent_id": "<your-id>", "name": "<display>", "origin": "openclaw", "public_key": "<base…key>"}quoted
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "capabilities" - note
frontmatter-keyunknown frontmatter key "min_openclaw_version" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4274 tokens
- 100Steps. 48 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (33 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: clean
This skill is a disclosed NANDA chapter integration that stores a local signing identity and uses it for user-confirmed chapter actions.
LLM: benign (high) · VirusTotal: · 29 May 2026