SKILLEMALL.ai
GitHub ↗ RU Sign in

CB scrape

Pull data from a web page through the Aside browser — your real, already signed-in sessions. (gstack)

The skillemall take

This skill promises to scrape data from web pages using the Aside browser with already authenticated sessions. Single file, no scripts. Scores: safety 95, quality 55, process 70—leaning toward not breaking things rather than reliable operation.

One medium-severity finding, no critical errors. Wide platform support: Claude, Cursor, Gemini, DeepSeek, and eight others. Code spans 6928 tokens. No sandbox or model testing runs.

Install if you specifically need scraping through an open authenticated browser and accept below-average implementation quality. Without real-world testing, the risk is higher than usual.

garrytan/gstack Agent Skills author: garrytan MIT 1 file body ≈ 6 929 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Pull data from a web page through the Aside browser — your real, already signed-in sessions.

As a process B 70/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
79/100
safety, quality, tests
Safety 60%
95
Quality 40%
55
Run on models
none yet
Process rating
B
70/100
Nearly there
When it triggers w 12
20
Inputs and preconditions w 11
30
Running it twice w 4
30
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.

Broad scope 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read AskUserQuestion

Files scanned: 1. 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")
  • warning body-long SKILL.md body ≈ 6929 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "preamble-tier"
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 70/100

  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 11 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 6929 tokens
  • 85Steps. 30 steps, 1 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 20 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (16 tags): a typed call is more reliable

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 101: 120–800 characters recommended
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 30 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)

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