SKILLEMALL.ai
GitHub ↗ RU Sign in

AB omnimemory-full-onboarding

register a new omnimemory saas account when needed, verify otp, create a first-party api key, optionally bind a third-party llm key, then install, configure, repair, and verify the @omni-pt/omnimemory-overlay plugin for openclaw. use when a user asks to install omnimemory, get a usable api key, finish onboarding end to end, fix setup problems, or run a smoke test after setup.

ClawHub Agent Skills author: PT-VU v1.0.2 MIT-0 5 files body ≈ 1 329 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 65/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerInfrastructureAI 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
65/100
Nearly there
When it triggers w 12
20
Inputs and preconditions w 11
30
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 · 0

    ✓ No critical or high findings

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

    • 20When it triggers. No condition that starts the skill
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 4 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 85Steps. 63 steps, 2 vague phrases
    • 100Failures and branches. 6 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1329 tokens
    • 100Progress reporting. Reports progress

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 378: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 63 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (2 of 2)

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

    External checks

    ClawHub: suspicious
    The skill appears purpose-aligned for OmniMemory setup, but it gives an agent broad authority to handle credentials, create accounts/API keys, install a code plugin, mutate persistent config, and enable automatic remote memory capture without enough consent and privacy scoping.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026