SKILLEMALL.ai

AC cifer-sdk

Implement quantum-resistant encryption using the CIFER SDK (cifer-sdk npm package). Covers SDK initialization, wallet setup, secret creation, text encryption/decryption, and file encryption/decryption on any supported chain (Ethereum, Sepolia, Ternoa). Use when the user mentions CIFER, cifer-sdk, quantum-resistant encryption, ML-KEM, secret creation, or encrypted payloads/files with blockchain.

ClawHub Agent Skills author: TIP-citron v0.3.1 3 files body ≈ 2 173 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
84
Run on models
none yet
Process rating
C
57/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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Secrets in code secret-high-entropy-token reference.md:40
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      secretsControllerAddress: '0xA6…C30',
      quoted

    Files scanned: 3. 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 57/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
    • 30Running it twice. 3 mutating operations with no state check
    • 40Consistency. Frontmatter name (cifer-sdk) differs from the folder (cifer-security)
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 7 steps
    • 100Execution cost. Instruction body is 2173 tokens
    • 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 397: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 7 items
    • +4Has examples (17 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill is a coherent CIFER SDK guide, but users should review it because it can route plaintext files/messages through an external encryption service without clearly explaining that trust boundary.
    LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026