CF twitter-api
A Twitter API alternative and X API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no OAuth and no developer application. Use when the user wants to search tweets by keyword, hashtag, or advanced operators (from:, to:, since:, until:, min_faves:, filter:), scrape a Twitter/X profile by handle, pull a user's tweets, replies, followers, or followings, fetch a single tweet with its replies or retweeters, read a Twitter List's members or tweets, check trending topics by country, or search for X accounts by name. Also covers Twitter data pipelines, competitor monitoring, hashtag tracking, sentiment analysis input, or follower export without the official X API's pricing tiers or app-review process.
As a process F 49/100 · Will not run — References files that are not bundled: ../x-api/SKILL.md, ../fetcher/SKILL.md, ../../task-guides/search-tweets.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 10
✓ No critical or high findings
Medium and low: 10
-
medium Exfiltration
net-credential-usereferences/scenarios.md:23Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:32Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:40Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/scenarios.md:49Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:79Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:123Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:130Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:138Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:147Credential used in a network call (verify the destination is the intended service)curl -H "Authorization: Bearer $FETCHER_API_KEY" \
-
low Exfiltration
net-credential-usereferences/scenarios.md:14Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)Swap the `curl -H "Authorization: Bearer $FETCHER_API_KEY"` prefix for a bare
quoted
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../x-api/SKILL.md - warning
missing-refreference to a missing file: ../fetcher/SKILL.md - warning
missing-refreference to a missing file: ../../task-guides/search-tweets.md - warning
missing-refreference to a missing file: ../../task-guides/export-twitter-followers.md - warning
missing-refreference to a missing file: ../../commands/twitter-search.md - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 49/100
- 0Tools and files. 5 referenced file(s) missing: ../x-api/SKILL.md, ../fetcher/SKILL.md, ../../task-guides/search-tweets.md
- 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. 4 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 13 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1962 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
- +1No license
- +2Single-language instructions
- +3Description length 751: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.