SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Cybercentry Private Data Verification

Cybercentry Private Data Verification on ACP - Real-time Zero-Knowledge Proof generation and text integrity validation. Get cryptographically secure proof_id and proof_url for trustless, privacy-preserving validation at just $1.00 per verification.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 4 392 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Cybercentry Private Data Verification on ACP - Real-time Zero-Knowledge Proof generation and text integrity validation.

As a process C 58/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency

AnalyzerGitHubAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
96
Quality 40%
69
Run on models
none yet
Process rating
C
58/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 4

✓ No critical or high findings

Medium and low: 4
  • low Secrets in code secret-high-entropy-token SKILL.md:202
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "text": "User holds NFT contract 0x74…3D7",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:205
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "wallet": "0x89…3e7",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:206
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "nft_contract": "0x74…3D7",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:333
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "contract_address": "0x74…3D7",
    quoted

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 58/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
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (Cybercentry Private Data Verification) differs from the folder (cybercentry-private-data-verification)
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4392 tokens
  • 85Steps. 71 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 13 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 248: enough signal without eating the budget
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 71 items
  • +3Output format is stated explicitly
  • +4Has examples (12 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.