User research and discovery
Public agent skills from SylphxAI — standards, product procedures, and one-command sync for Codex, Claude Code, and Grok Build
npx -y skills add SylphxAI/skills --skill user-research-and-discoveryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Plan, run, and synthesize qualitative user research into a User Research Protocol and Findings. Use for goals, behavior, context, and barriers evidence. Not market sizing, continuous feedback ops, analytics instrumentation, or causal experiments.
SKILL.md
3.5 KB, as published. Nobody here has run it
User Research and Discovery
Produce decision-relevant user evidence without turning a convenient sample, memorable quotation, or researcher's interpretation into a population claim. Read references/research-method.md before selecting participants, collecting data, or interpreting findings.
Workflow
- Bind the study to a decision, target users, context, known evidence, assumptions, unknowns, and evidence that could change the decision.
- Choose the smallest method mix that can observe the relevant behavior or elicit the relevant experience. Prefer observation of real work over stated preference when the research question concerns behavior.
- Define a purposive recruitment matrix across material behaviors, access needs, experience, context, and risk. State excluded groups and coverage limits; do not call a qualitative sample representative.
- Establish consent, privacy, recording, compensation, safeguarding, accessibility, retention, withdrawal, and sensitive-topic handling before recruitment. Collect only data required by the study.
- Write and pilot a protocol. Use neutral prompts, realistic tasks, consistent probes, and explicit stopping or escalation rules. Do not coach participants toward the intended design.
- Preserve traceability from session evidence to observations, interpretations, themes, and recommendations. Separate what a participant did or said from what the researcher inferred.
- Analyze iteratively across participants. Search for negative cases, contradictory segments, researcher effects, non-response, proxy-user error, and alternative explanations. Do not manufacture saturation from repetition in a narrow sample.
- Connect findings to the original decision. Rank findings by consequence, evidence coverage, and confidence; state unresolved questions and the next evidence needed.
Artifact
Produce a User Research Protocol and Findings:
- decision, research questions, users, context, scope, and prior evidence;
- method, recruitment matrix, inclusion and exclusion, consent, privacy, accessibility, retention, and study materials;
- session ledger with evidence locators and material deviations;
- findings with supporting and disconfirming observations, affected groups, coverage, confidence, and limitations;
- design or service implications, non-claims, unresolved risks, and decision handoff.
If only the protocol or only the findings are requested, produce that section without inventing the missing study phase.
Boundaries
- Use
market-research-synthesisfor category, competitor, pricing, or demand evidence from market sources. - Use
product-feedback-learning-loopfor recurring post-use feedback intake, triage, prioritization, and closure. - Use
product-analytics-instrumentation-reviewfor event definitions, telemetry coverage, and quantitative behavioral measurement. - Use
product-experiment-reviewfor randomized, holdout, switchback, or staged product experiments; usecausal-inference-analysisfor causal effect claims. - Do not generalize prevalence from qualitative evidence. Hand a prevalence question to an appropriately sampled quantitative study.