SKILLEMALL.ai
GitHub ↗ RU Sign in

CC forkzoo

Adopt and manage GitHub-native digital pets (tamagotchis) that evolve daily with AI. Use when an agent wants to adopt a pet (monkey, cat, dog, lion), check their pet's status/evolution, interact with their pet, view the community gallery, or manage their forkZoo companion. Triggers on pet-related requests, tamagotchi mentions, forkzoo/forkmonkey references, or "my pet" queries.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files · 4 scripts body ≈ 744 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Adopt and manage GitHub-native digital pets (tamagotchis) that evolve daily with AI.

As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationGitHubAI 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
C
71/100
safety, quality, tests
Safety 60%
65
Quality 40%
81
Run on models
none yet
Process rating
C
62/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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

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

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

    ✓ No critical or high findings

    Medium and low: 7
    • medium Exfiltration net-credential-use scripts/adopt.sh:39
      Credential used in a network call (verify the destination is the intended service)
      GITHUB_USER=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/interact.sh:16
      Credential used in a network call (verify the destination is the intended service)
      GITHUB_USER=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/interact.sh:21
      Credential used in a network call (verify the destination is the intended service)
      REPOS=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/status.sh:16
      Credential used in a network call (verify the destination is the intended service)
      GITHUB_USER=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/status.sh:24
      Credential used in a network call (verify the destination is the intended service)
      REPOS=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/status.sh:43
      Credential used in a network call (verify the destination is the intended service)
      STATS=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \
    • medium Exfiltration net-credential-use scripts/status.sh:49
      Credential used in a network call (verify the destination is the intended service)
      STATS=$(curl -s -H "Authorization: token $GITHUB_TOKEN" \

    Files scanned: 5. 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 62/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. 1 mutating operations with no state check
    • 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. 31 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 744 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)
    • +3Output format is not stated: the model decides each time
    • -31 of 4 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 380: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 31 items
    • +4Has examples (3 code blocks)

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