SKILLEMALL.ai

AB twitterapi-io

Interact with Twitter/X via TwitterAPI.io — search tweets, get user info, post tweets, like, retweet, follow, send DMs, and more. Covers all 59 endpoints. Use when the user wants to read or write Twitter data.

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files body ≈ 2 312 tokens Open the sourcegithub.com analyzed 3 d ago

Interact with Twitter/X via TwitterAPI.io — search tweets, get user info, post tweets, like, retweet, follow, send DMs, and more. Covers all 59 endpoints. Use…

As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting

IntegrationGitHubAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
99
Quality 40%
91
Run on models
none yet
Process rating
B
69/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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 Exfiltration net-credential-use references/webhook-stream-endpoints.md:14
      Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)
      curl -s "https://api.twitterapi.io/oapi/tweet_filter/get_rules" -H "X-API-Key: $TWITTERAPI_IO_KEY"
      vendor-host

    Files scanned: 7. 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 69/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 8 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 22 steps, 1 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2312 tokens
    • low 12 top-level sections: this looks like several domains in one skill

    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 209: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 22 items
    • +3Output format is stated explicitly
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)

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