CC birdx
X/Twitter CLI that reads Chrome cookies directly from disk — no browser session required after first auth. Supports reading tweets with viewCount/bookmarkCount, full thread replies, search with engagement metrics, and followers/following lists. Use when you need to fetch Twitter/X data, search tweets, read threads, or get user follower lists without a browser. No Twitter API key needed.
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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.
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".
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- 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.
- 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
-
high Exfiltration
intent-browser-credential-storescripts/birdx.js:292Accesses a browser credential / cookie store_cookies = await loadCookiesFromChrome();
-
high Exfiltration
intent-browser-credential-storescripts/birdx.js:316Accesses a browser credential / cookie storecookies = await loadCookiesFromChrome();
Medium and low: 5
-
medium Secrets in code
secret-labelled-tokenscripts/birdx.js:46Labelled token / key literal (vendor format unknown — verify it is not a live credential)const BEARER = 'AAAA…uTs%3D1Z…TnA';
-
medium Exfiltration
intent-browser-credential-storescripts/birdx.js:146Accesses a browser credential / cookie store (quoted — discussed, not commanded)'Library/Application Support/Google/Chrome/Default/Cookies'
quoted -
medium Exfiltration
intent-browser-credential-storescripts/birdx.js:149Accesses a browser credential / cookie store (quoted — discussed, not commanded)throw new Error(`Chrome Cookies DB not found at ${chromeCookieDb}`);quoted -
medium Exfiltration
intent-browser-credential-storescripts/birdx.js:314Accesses a browser credential / cookie store (quoted — discussed, not commanded)process.stderr.write('Reading cookies from Chrome disk (no browser needed)...\n');quoted -
low Secrets in code
secret-high-entropy-tokenscripts/birdx.js:46High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const BEARER = 'AAAA…uTs%3D1Z…TnA';
quoted
Files scanned: 3. 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 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 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 (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 451 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)
- +1No license
- +2Single-language instructions
- +3Description length 389: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 9 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.