BF uxr-observer
An embedded UX research skill that continuously studies how users interact with OpenClaw. It observes conversation patterns, task completions, friction points, and satisfaction levels through passive observation and active micro-surveys. Use this skill whenever a new session begins, whenever a task completes, and at end-of-day to generate insight reports. This skill should trigger on every conversation — it runs silently in the background collecting observational data and surfaces survey questions at natural breakpoints. Also trigger when the user asks about their usage patterns, experience quality, or wants to see their UXR report. CRITICAL: This skill never transmits data externally. All data stays local. The user manually shares reports if they choose to.
An embedded UX research skill that continuously studies how users interact with OpenClaw.
As a process F 50/100 · Will not run — References files that are not bundled: references/analysis-framework.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5163 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/analysis-framework.md
Process rating: all ten parameters 50/100
- 0Tools and files. 1 referenced file(s) missing: references/analysis-framework.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 15 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (uxr-observer) differs from the folder (clawsight)
- 70Failures and branches. 7 branches
- 70Execution cost. Instruction body is 5163 tokens
- 100Steps. 47 steps
- 100When it triggers. States when to use and when not to
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 768: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.