BC civic-nexus
Connect to Civic Nexus MCP for 100+ integrations.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
IntegrationAI and agentsInfrastructuretype 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpnpm-lock.yaml:28High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…7pY+zoMV…h0x/Ptw8…8dg==} -
low Secrets in code
secret-high-entropy-tokenpnpm-lock.yaml:40High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…b00+Gxjx…zRc/oZwU…hzA==} -
low Secrets in code
secret-high-entropy-tokenpnpm-lock.yaml:58High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==} -
low Secrets in code
secret-high-entropy-tokenpnpm-lock.yaml:70High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…Dsc+j03S…0oA==} -
low Secrets in code
secret-high-entropy-tokenpnpm-lock.yaml:172High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…NS8+tHW7…WOF+PEzk…X4Q==}
Files scanned: 6. 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")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (civic-nexus) differs from the folder (civic-nexus-openclaw)
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 7 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 642 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)
- +3Description length 49: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
This appears to be a legitimate Civic Nexus bridge, but it gives an agent broad access to many connected services without clear approval boundaries for sensitive actions.
LLM: suspicious (medium) · VirusTotal: benign · 28 May 2026