SKILLEMALL.ai
GitHub ↗ RU Sign in

BB steam-gaming-companion

Steam & PC Gaming Companion — full Steam Web API integration for library management, play recommendations, wishlist sale monitoring, achievement tracking, and game info lookup. The first real Steam API skill on ClawHub.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 2 files body ≈ 6 867 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Steam & PC Gaming Companion — full Steam Web API integration for library management, play recommendations, wishlist sale monitoring, achievement tracking, and…

As a process B 71/100 · Nearly there — weak spots: when it triggers, running it twice

IntegrationAI and agentsWriting and documentsOperations and projectstype 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
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
61
Run on models
none yet
Process rating
B
71/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
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: 2. 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 ≈ 6867 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "requires"
  • note frontmatter-key unknown frontmatter key "optional_env"

Process rating: all ten parameters 71/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 6867 tokens
  • 85Steps. 73 steps, 2 vague phrases
  • 100Inputs and preconditions. Inputs and preconditions are listed
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill

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)
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 219: enough signal without eating the budget
  • +4Structure: 58 headings
  • +3Step-by-step instructions: 73 items
  • +3Output format is stated explicitly
  • +4Has examples (41 code blocks)

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