SKILLEMALL.ai
GitHub ↗ RU Sign in

AB socialclaw-cli

Run SocialClaw as an agentic control plane for Meta operations through the installed social CLI. Use when the user asks for multi-step execution, approvals, ops automation, or command generation across auth, query, post, Instagram, WhatsApp, Marketing API, agent mode, and gateway/studio workflows. Translate natural-language intents into explicit, risk-gated social commands with confirmation-aware execution.

modbender/skill-library-mcp Agent Skills author: modbender MIT 9 files · 1 script body ≈ 594 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Run SocialClaw as an agentic control plane for Meta operations through the installed social CLI.

As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

IntegrationWhatsAppAI and agentstype 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
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
B
66/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
50
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: 9. 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 66/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 30 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 594 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)
    • +4No input/output examples
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 410: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 30 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (6 of 6)

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