SKILLEMALL.ai
RU Sign in

DC lunchtable-tcg

Play LunchTable-TCG, a Yu-Gi-Oh-inspired online trading card game with AI agents

Not recommendedcritical or high security findings · low grade D
ClawHub Agent Skills author: Dexploarer v1.0.0 27 files · 2 scripts body ≈ 4 384 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

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

ProcedureInfrastructureAI 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
D
59/100
safety, quality, tests
Safety 60%
53
Quality 40%
67
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Exfiltration
If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 14

  • high Exfiltration exfil-webhook-url scenarios/webhook-setup.md:47
    Webhook / callback URL commonly used for exfiltration (verify the destination)
    1. Visit https://webhook.site
Medium and low: 13
  • medium Exfiltration net-redirectable-api-key examples/advanced-agent.ts:29
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key examples/basic-agent.py:44
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key examples/basic-agent.ts:26
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration exfil-webhook-url examples/README.md:126
    Webhook / callback URL commonly used for exfiltration (verify the destination) (test fixture / example file)
    [2026…02Z] ℹ️ Webhook URL: https://abc1….io/webhook
    fixture
  • low Exfiltration net-credential-use .clawhub.json:53
    Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)
    "command": "curl -X GET https://lunchtable.cards/api/agents/me -H \"Authorization: Bearer $LTCG_API_KEY\"",
    vendor-hostquoted
  • low Exfiltration exfil-webhook-url examples/README.md:87
    Webhook / callback URL commonly used for exfiltration (verify the destination) (security demo / example; test fixture / example file)
    # Copy the https URL (e.g., https://abc1….io)
    demofixture
  • low Exfiltration exfil-webhook-url scenarios/webhook-setup.md:48
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    2. You'll get a unique URL like `https://webhook.site/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`
    placeholder
  • low Exfiltration exfil-webhook-url scenarios/webhook-setup.md:61
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    "url": "https://webhook.site/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    placeholder
  • low Exfiltration exfil-webhook-url scenarios/webhook-setup.md:72
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    "url": "https://webhook.site/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    placeholder
  • low Exfiltration exfil-webhook-url scenarios/webhook-setup.md:349
    Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)
    3. You'll see: `https://xxxx-xxx-xxx-xxx.ngrok.io`
    placeholder
  • low Secrets in code secret-high-entropy-token SKILL.md:41
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "apiKey": "ltcg…456",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:53
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    export LTCG_API_KEY="ltcg…456"
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:544
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    -H "Authorization: Bearer ltcg…456"
    quoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "emoji"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "repository"
  • note frontmatter-key unknown frontmatter key "requires"

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 70Execution cost. Instruction body is 4384 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 120 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress

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 80: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 120 items
  • +4Has examples (23 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This skill is a coherent game-integration skill, but its examples and docs expose API keys and webhook-driven gameplay in ways users should review before installing or running.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026