Layers Observed Behaviour
- 1.6k installs
- 282 repo stars
- Updated May 30, 2026
- jamiemill/layers-skills
layers-observed-behaviour is an agent skill that plans user research studies and synthesizes raw observations into confidence-rated behavioral findings for developers validating what users actually do.
About
layers-observed-behaviour is a Layers skill from jamiemill/layers-skills that provides techniques for planning user research and synthesizing material into grounded, confidence-rated findings about actual user behavior. It assumes /layers-intro has been loaded and operates as a technique library rather than a rigid script. The observed behaviour layer represents what users actually do, distinct from assumptions or desired behavior. The skill detects two situations: Plan when no research exists yet and a study must be designed, and Synthesise when research material already exists and needs structured findings. Developers reach for layers-observed-behaviour when product decisions need evidence-backed behavioral insights instead of stakeholder opinions alone.
- Distinguishes between Plan mode (no research yet) and Synthesise mode (existing research material)
- Forces grounding in raw data with explicit observed/inferred/assumed confidence markers
- Requires verbatim quotes for every observed claim
- Guides what specific questions to answer about users and what evidence is already available
- Prevents mixing interpretation with observation by keeping this layer closest to reality
Layers Observed Behaviour by the numbers
- 1,565 all-time installs (skills.sh)
- +128 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #378 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/jamiemill/layers-skills --skill layers-observed-behaviourAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 282 |
| Security audit | 3 / 3 scanners passed |
| Last updated | May 30, 2026 |
| Repository | jamiemill/layers-skills ↗ |
How do you synthesize user research into behavioral findings?
Plan user research studies and synthesize raw observations into confidence-rated findings about actual user behavior.
Who is it for?
Developers or designers with pending or completed user research who need structured study plans or evidence-rated behavioral synthesis.
Skip if: Teams that only need visual UI mockups, component code, or analytics dashboard SQL without qualitative research workflows.
When should I use this skill?
The user needs to plan user research or synthesize observations into confidence-rated findings about what users actually do.
What you get
Research study plans, synthesized observation notes, and confidence-rated findings about actual user behavior.
- Research study plan
- Confidence-rated findings
- Behavioral synthesis notes
Files
/layers-observed-behaviour
Assumes `/layers-intro` has been loaded. This skill is a library of techniques, not a script — see "How to use these skills" there.
The observed behaviour layer is the closest we can get to reality — what users actually do, not what we think they do or wish they would. Everything above it is interpretation; this layer is the source.
It splits into two situations. Detect which applies and say so:
- Plan — no research yet; design a study.
- Synthesise — research material exists; make sense of it.
With partial research, synthesise what exists first, then plan to fill the gaps.
---
The decisions this layer makes
- What specific questions we most need to answer about our users
- What evidence already exists, and how reliable it is
- How to gather what's missing
- What patterns hold with confidence vs. what remains assumption
---
Disciplines — what keeps observation honest
- Stay close to raw data. Observations should be specific and near the source — what users said, did, felt — not summarised into conclusions.
- Ground in something seen or heard, not in team beliefs.
- Mark confidence: observed / inferred / assumed. If you mark something observed, the verbatim that supports it should be quotable in the same note — an observed claim with no quotable evidence is really inferred.
- Name research gaps explicitly rather than papering over them.
- Workarounds are signal. A need real enough to motivate improvisation is a strong one.
---
Techniques
To plan a study
| Technique | Use it when |
|---|---|
| Define the learning goal | Always start here. Push past "understand users better" to 2–3 specific questions — "what triggers someone to refer a friend, and what makes them hesitate." |
| JTBD interviews | Understanding triggers, motivations, anxieties. Interview about a real past experience, not hypotheticals. Guide: opening ("tell me about the last time you…"), timeline (what triggered it, what you tried), motivations (what you hoped, what worried you), closing. |
| Contextual inquiry / observation | What users say differs from what they do — watch real work for tacit behaviour. |
| Diary studies | Behaviour is distributed over time or infrequent — users self-report as events occur. |
| Support ticket / review analysis | Existing product with accumulated signal — pain points at scale without recruiting. |
| Analytics review | What users do (not why). Complements qualitative; doesn't replace it. |
| Usability observation | Where people struggle or succeed with an existing product. |
For interviews, plan synthesis up front: one observation per note, tagged with the question it speaks to, raw quotes over summaries. (6–10 qualitative interviews usually reach saturation.)
To synthesise material
| Technique | Use it to |
|---|---|
| Extract observations | Pull out concrete things users said, did, or felt — no interpretation yet. From memory, prompt: most surprising thing? what recurred? what did they struggle with unexpectedly? |
| Pattern grouping | Group observations by recurring situations, common motivations, shared anxieties, and workarounds. |
| Candidate job stories | When [situation], I want to [motivation], so I can [outcome]. Check the "When" is specific and the "want" is a motivation not a solution; mark confidence. |
| Gap-flagging | What do the observations not yet answer? These become a follow-up Plan session. |
---
Working with the designer
First find out what exists — interviews, recordings, tickets, analytics — and state the mode. Listen for nouns (candidate domain objects) and the natural language users use; that feeds the domain layer.
Offer the technique that fits: in Plan, the method matched to the learning goal; in Synthesise, extraction → patterns → candidate stories. Do the next useful thing, not a full battery.
Capture only the residue — key raw observations, the patterns with their supporting evidence, candidate job stories with confidence ratings, and the named research gaps.
Candidate job stories are ready to refine at /layers-user-needs.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick layers-observed-behaviour over generic PM skills when qualitative behavioral research planning and confidence-rated synthesis is the deliverable.
FAQ
What modes does layers-observed-behaviour support?
layers-observed-behaviour detects Plan mode when no research exists yet and Synthesise mode when research material is ready to convert into confidence-rated behavioral findings.
What prerequisite skill does layers-observed-behaviour require?
layers-observed-behaviour assumes /layers-intro has been loaded first and functions as a technique library rather than a fixed step-by-step script.
Is Layers Observed Behaviour safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.