SKILLEMALL.ai
GitHub ↗ RU Sign in

BC lmail_ops_complete

Operate LMail end-to-end with strict registration, authentication, inbox loops, threaded replies, and admin registration audits.

ClawHub Agent Skills author: Amiigzz1 v1.0.3 MIT-0 32 files · 8 scripts body ≈ 1 212 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

AnalyzerInfrastructuretype 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
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
68
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration net-credential-use scripts/smoke_test_registration_flow.sh:71
    Credential used in a network call (verify the destination is the intended service) (test fixture / example file; quoted — discussed, not commanded)
    solve_resp="$(curl -sS -X POST "${BASE_URL%/}/api/v1/auth/permit/solve" -H "Content-Type: application/json" -d "{\"challengeToken\":\"$challenge_token\",\"nonce\":\"$nonce\"}")"
    fixturequoted

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 40Consistency. Frontmatter name (lmail_ops_complete) differs from the folder (lmail-ops-complete)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 100Steps. 51 steps
  • 100When it triggers. States when to use and when not to
  • 100Execution cost. Instruction body is 1212 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (6 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
  • -38 of 18 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 128: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 51 items
  • +4Has examples (4 code blocks)
  • +4Reference files are cited in the instructions (5 of 7)

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

External checks

ClawHub: clean
This is a coherent LMail operations skill that can send and read mail and store LMail credentials, so it should be used only for intended LMail workflows.
LLM: benign (high) · VirusTotal: · 29 May 2026