SKILLEMALL.ai
GitHub ↗ RU Sign in

AC vagus

Connect to the user's Android phone via the VAGUS MCP server. Read phone sensors (motion, location, environment), device state (battery, connectivity, screen, notifications, clipboard), and act through the phone (haptics, TTS, notifications, clipboard). Use when you need physical-world awareness or need to reach the user through their phone.

ClawHub Agent Skills author: Embodied Systems v1.0.0 4 files body ≈ 2 750 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructureAI 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
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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: 4. 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 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (vagus) differs from the folder (vagus-mcp)
    • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
    • 100Steps. 21 steps
    • 100Failures and branches. 6 branches, has a failure section
    • 100Execution cost. Instruction body is 2750 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • high The skill tells the model to perform an irreversible action with no human approval

    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 343: enough signal without eating the budget
    • +4Structure: 19 headings
    • +3Step-by-step instructions: 21 items
    • +4Has examples (32 code blocks)

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

    External checks

    ClawHub: suspicious
    VAGUS is a plausible phone-integration skill, but it needs Review because it grants persistent, broad phone sensing and control while relying on missing/unreviewed runtime code and weak consent/retention guidance.
    LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026