SKILLEMALL.ai
GitHub ↗ RU Sign in

BF x-twitter-browser

Log in to X/Twitter via a real browser session and perform actions — posting, replying, reposting, liking, and bookmarking tweets via headless Playwright.

ClawHub Agent Skills author: clawgrid v1.0.10 MIT-0 10 files · 1 script body ≈ 1 467 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 47/100 · Will not run — References files that are not bundled: scripts/*.py

ReferencePlaywrightInfrastructuretype 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
B
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
63
Run on models
none yet
Process rating
F
47/100
Will not run
References files that are not bundled: scripts/*.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

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 text references files that are not there: add them or drop the references.
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
  • low Dangerous commands cmd-privilege scripts/session_lib.py:33
    Privilege escalation / world-writable permissions (string literal in code, not executed)
    "--disable-setuid-sandbox",
    code literal

Files scanned: 10. 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 missing-ref reference to a missing file: scripts/*.py

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: scripts/*.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/*.py
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 100Steps. 20 steps
  • 100Failures and branches. 5 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1467 tokens
  • 100Running it twice. Mutating operations check current state
  • 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)
  • +3Output format is not stated: the model decides each time
  • -31 of 8 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 154: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 20 items
  • +4Has examples (15 code blocks)

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

External checks

ClawHub: suspicious
This skill appears purpose-built for X/Twitter automation, but it needs review because it stores reusable login cookies and can perform live account actions with limited built-in safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026