SKILLEMALL.ai

BC Cybercentry Solidity Code Verification

Cybercentry Solidity Code Verification on ACP - Fast, automated security analysis of Solidity smart contract code. 99.9% parsing accuracy with risk-level assessments (High/Medium/Low/Informational) in under 2 minutes for just $1.00 per scan.

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

Cybercentry Solidity Code Verification on ACP - Fast, automated security analysis of Solidity smart contract code.

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

AnalyzerGitHubSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
99
Quality 40%
59
Run on models
none yet
Process rating
C
60/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.
  2. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-password-literal SKILL.md:120
    Hard-coded password / key literal (may be an example) (placeholder value)
    string private apiKey = "sk-a…...";  // NEVER INCLUDE
    placeholder

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")
  • warning body-long SKILL.md body ≈ 5100 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 60/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. 20 mutating operations with no state check
  • 40Consistency. Frontmatter name (Cybercentry Solidity Code Verification) differs from the folder (cybercentry-solidity-code-verification)
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 5100 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 86 steps
  • low 15 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 241: enough signal without eating the budget
  • +4Structure: 43 headings
  • +3Step-by-step instructions: 86 items
  • +3Output format is stated explicitly
  • +4Has examples (16 code blocks)

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