SKILLEMALL.ai

AD openclaw-twitter-post-engage

Search X/Twitter profiles, tweets, trends, and approved engagement actions through the AISA relay. Use when: the user asks for Twitter/X research, posting, likes, follows, or related workflows without sharing passwords. Write actions require OAuth approval plus an explicit final confirmation artifact before execution.

ClawHub Agent Skills author: AIsa v1.0.3 MIT-0 8 files body ≈ 968 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 42/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
D
42/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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 · 0

    ✓ No critical or high findings

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "homepage"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "primaryEnv"
    • note frontmatter-key unknown frontmatter key "requires"

    Process rating: all ten parameters 42/100

    • 0Result and completion. Does not say what the result is
    • 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
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (openclaw-twitter-post-engage) differs from the folder (openclaw-twitter-post-engage-slot3)
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 100Steps. 29 steps
    • 100Execution cost. Instruction body is 968 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
    • +2Single-language instructions
    • +3Description length 319: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 29 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 3 scripts are documented
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This is a coherent Twitter/X relay skill, but it can change a public account and exposes its AISA API key in normal command output.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026