SKILLEMALL.ai
GitHub ↗ RU Sign in

DC onemind-skill

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: OneMind v1.0.0 8 files · 1 script body ≈ 1 523 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ProcedureInfrastructuretype 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
D
55/100
safety, quality, tests
Safety 60%
92
Quality 40%
0
Run on models
none yet
Process rating
C
57/100
Has gaps
When it triggers w 12
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 · 8

✓ No critical or high findings

Medium and low: 8
  • low Secrets in code secret-labelled-token SKILL.md:46
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)
    apikey: eyJh…...
    placeholder
  • low Secrets in code secret-password-literal SKILL.md:46
    Hard-coded password / key literal (may be an example) (placeholder value)
    apikey: eyJh…...
    placeholder
  • low Secrets in code secret-high-entropy-token SKILL.md:234
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    - **Token Mint:** `mnte…Tr3` (Solana SPL)
    detector
  • low Obfuscation obf-base64-blob TEST_REPORT_V2.md:32
    Long base64-looking blob (test fixture / example file; quoted — discussed, not commanded)
    {"access_token":"eyJh…iOi
    fixturequoted
  • low Exfiltration net-credential-use TEST_REPORT.md:9
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; test fixture / example file)
    curl -s "https://ccyuxrtrklgpkzcryzpj.supabase.co/rest/v1/chats?id=eq.87&select=…" -H "apikey: ${ANON_KEY}" -H "Authorization: Bearer ${ANON_KEY}"
    known servicefixture
  • low Exfiltration net-credential-use TEST_REPORT.md:22
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; test fixture / example file)
    curl -s "https://ccyuxrtrklgpkzcryzpj.supabase.co/rest/v1/chats?is_active=…&select=…&limit=20" -H "apikey: ${ANON_KEY}" -H "Authorization: Bearer ${ANON_KEY}"
    known servicefixture
  • low Exfiltration net-credential-use TEST_REPORT.md:54
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; test fixture / example file)
    curl -s "https://ccyuxrtrklgpkzcryzpj.supabase.co/rest/v1/rounds?chat_id=eq.87&select=*&limit=1&order=…" -H "apikey: ${ANON_KEY}" -H "Authorization: Bearer ${ANON_KEY}"
    known servicefixture
  • low Exfiltration net-credential-use TEST_REPORT.md:67
    Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; test fixture / example file)
    curl -s "https://ccyuxrtrklgpkzcryzpj.supabase.co/rest/v1/propositions?chat_id=eq.87&select=*&limit=10" -H "apikey: ${ANON_KEY}" -H "Authorization: Bearer ${ANON_KEY}"
    known servicefixture

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 57/100

  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1523 tokens

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 0: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 11 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: suspicious
This skill is not clearly malicious, but it deserves review because it directs agents to create and modify live OneMind records while its documentation shows weak scoping, credential-handling, and authorization concerns.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026