SKILLEMALL.ai
GitHub ↗ RU Sign in

AC uxr-observer

Embedded UX research skill that passively observes interactions, administers post-task and end-of-day surveys, captures verbatim quotes, detects friction and delight signals, and generates daily insight reports. All data stays local.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 4 238 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Embedded UX research skill that passively observes interactions, administers post-task and end-of-day surveys, captures verbatim quotes, detects friction and…

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

ProcedureData and analyticstype 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
52/100
Has gaps
Inputs and preconditions w 11
0
When it triggers w 12
20
Result and completion w 14
40
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 · 0

✓ No critical or high findings

Files scanned: 5. 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")

Process rating: all ten parameters 52/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (uxr-observer) differs from the folder (observer)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 70Execution cost. Instruction body is 4238 tokens
  • 100Steps. 65 steps
  • 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 17 top-level sections: this looks like several domains in one skill
  • 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
  • +2Single-language instructions
  • +3Description length 233: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 65 items
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)
  • +3All 3 scripts are documented
  • +1License stated

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