SKILLEMALL.ai

AC debox-community

Manage DeBox communities, DAOs, and NFT groups. Use when you need to verify group membership, check voting/lottery participation, query group info, or validate user eligibility for DAO/NFT communities. Supports group info lookup, member verification, vote/lottery stats, and praise data queries. Ideal for DAO membership verification, NFT community access control, and community analytics.

ClawHub Agent Skills author: ZanyK4502 v1.0.0 MIT-0 9 files body ≈ 873 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
90
Quality 40%
91
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    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 · 10

    ✓ No critical or high findings

    Medium and low: 10
    • low Secrets in code secret-high-entropy-token package-lock.json:114
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…byA+l3XtsAj+Q8tf…oOo+X6HZ…Q8A==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:162
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…bSm+x6ETixtKZBh/qbRE…8Sr/Wcyx…yGA==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:210
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…UzJ+En8KcVm9Lk5+uGUQ…GXw==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:242
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…595+ujv0…pwV/GONa…zQo/1O6zRIkh0m/8+5Bjr…SZw==",
      detector
    • low Secrets in code secret-high-entropy-token package-lock.json:330
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
      "integrity": "sha5…bUj+rBev…oyX+04WG…4jg==",
      detector
    • low Secrets in code secret-password-literal references/api.md:38
      Hard-coded password / key literal (may be an example) (placeholder value)
      curl -X GET -H "X-API-KEY: t2XAlEF6..." \
      placeholder
    • low Secrets in code secret-password-literal references/api.md:75
      Hard-coded password / key literal (may be an example) (placeholder value)
      curl -X GET -H "X-API-KEY: t2XAlEF6..." \
      placeholder
    • low Secrets in code secret-password-literal references/api.md:105
      Hard-coded password / key literal (may be an example) (placeholder value)
      curl -X GET -H "X-API-KEY: t2XAlEF6..." \
      placeholder
    • low Secrets in code secret-password-literal references/api.md:140
      Hard-coded password / key literal (may be an example) (placeholder value)
      curl -X GET -H "X-API-KEY: t2XAlEF6..." \
      placeholder
    • low Secrets in code secret-password-literal references/api.md:178
      Hard-coded password / key literal (may be an example) (placeholder value)
      curl -X GET -H "X-API-KEY: t2XAlEF6..." \
      placeholder

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    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
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (debox-community) differs from the folder (debox-community-zanyk)
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 4 steps
    • 100Execution cost. Instruction body is 873 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 389: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 4 items
    • +4Has examples (13 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    The skill mostly does what it claims for DeBox community checks, but it ships an API-key-like config file and under-explains privacy and credential risks.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026