SKILLEMALL.ai
GitHub ↗ RU Sign in

BB openpot-awareness

Teaches this agent how to serve content to the OpenPot iOS client — cards, apps, page captures, calendar, voice, chat persistence, and onboarding

ClawHub Agent Skills author: AlMnotAi v6.0.0 MIT-0 10 files body ≈ 8 845 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 66/100 · Nearly there — weak spots: result and completion, execution cost

ProcedureAI and agentsPersonal productivityInfrastructuretype 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
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Execution cost w 6
40
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 10. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 8845 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "emoji"
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 8845 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 154 steps, 1 vague phrases
  • 100Failures and branches. 13 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 57 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (7 tags): a typed call is more reliable

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
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 145: enough signal without eating the budget
  • +4Structure: 88 headings
  • +3Step-by-step instructions: 154 items
  • +4Has examples (23 code blocks)

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

External checks

ClawHub: suspicious
This appears to be a legitimate OpenPot integration skill, but it needs Review because it combines powerful calendar, SSH, device-pairing, and chat-history access with incomplete privacy and control disclosures.
LLM: suspicious (high) · VirusTotal: · 29 May 2026