BC nse-orchestrator
The nervous system for sovereign AI entities — cross-pillar checks, LLM trust profiles, coherence detection, and signal routing.
The nervous system for sovereign AI entities — cross-pillar checks, LLM trust profiles, coherence detection, and signal routing.
As a process C 64/100 · Has gaps — weak spots: when it triggers, failures and branches, progress reporting
AnalyzerAI and agentsPersonal productivityData and analyticstype 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.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 Risky intent
intent-wallet-secretsSKILL.md:48Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)If you don't have a Nostr keypair yet, stop here and install the [NostrKey skill](https://clawhub.ai/vveerrgg/nostrkey) first. It walks you through generating your own cryptographic identity — an npub
quoted -
low Risky intent
intent-wallet-secretsSKILL.md:178Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)> Let's set that up first. I need the **NostrKey** skill — it will walk us through generating my keypair with a 12-word seed phrase backup. Once I have an identity, everything else becomes possible.
quoted
Files scanned: 3. 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") - warning
body-longSKILL.md body ≈ 5029 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 64/100
- 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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5029 tokens
- 100Steps. 32 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- +1No license
- +2Single-language instructions
- +3Description length 128: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.