SKILLEMALL.ai
GitHub ↗ RU Sign in

CC Sci-Data-Extractor

AI-powered tool for extracting structured data from scientific literature PDFs

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files body ≈ 1 129 tokens Open the sourcegithub.com↗ analyzed 2 d ago

AI-powered tool for extracting structured data from scientific literature PDFs

As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, progress reporting

ProcedureResearchtype 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
73/100
safety, quality, tests
Safety 60%
77
Quality 40%
67
Run on models
none yet
Process rating
C
62/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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.

Dangerous commands 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 skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

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

✓ No critical or high findings

Medium and low: 7
  • medium Exfiltration net-redirectable-api-key extractor.py:46
    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 Dangerous commands cmd-pipe-to-shell-known-host README_ZH.md:58
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -LsSf https://astral.sh/uv/install.sh | sh
  • medium Dangerous commands cmd-pipe-to-shell-known-host README.md:59
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -LsSf https://astral.sh/uv/install.sh | sh
  • medium Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:36
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -LsSf https://astral.sh/uv/install.sh | sh
  • low Exfiltration read-dotenv examples/README.md:86
    Reads a .env file (test fixture / example file)
    cp .env.example .env
    fixture
  • low Exfiltration read-dotenv SKILL.md:63
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv USAGE.md:62
    Reads a .env file
    cp .env.example .env

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 62/100

  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 36 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1129 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)
  • +3Description length 78: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 36 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)

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