mcpbeat

Lamina Research

aryaniyaps/lamina-research

Plan and synthesize evidence-grounded product research. Use when deciding what evidence is needed, designing actor walkthroughs, grounding claims in a repository or live product, analyzing user-provided references, modeling users and tasks, or communicating findings without inventing data. Use lamina-evaluation instead to judge a built product, and lamina-ux to design interaction behavior.

3k tokens
context cost
the whole folder, loaded on every use
11
files
instructions only
0
copies elsewhere
how many repositories repackaged it
111
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/aryaniyaps/lamina --skill lamina-research

What comes with it

8 192 bytes besides the instruction
references/competitive-analysis.md
references/field-research.md
references/interview-design.md
references/interview-documentation.md
references/research-communication.md
references/research-planning.md
references/research-scoping.md
references/research-synthesis.md
references/task-analysis.md
references/user-modeling.md

The instruction itself

4 sections, as written by the author

Lamina Research

Reference-loading protocol

  • Match the request's primary research decision to one row below.
  • Open that linked reference before answering. Add another only when a second

decision materially changes the answer; do not preload the directory.

  • Start the response with Using lamina-research: <topic path(s)> so the

selected evidence lens is auditable.

Topic index

| Decision signal | Read | Adds |

|---|---|---|

| Need to plan who or what a verification pass will exercise | Simulation Planning | actors, probes, parallel groups, and success criteria |

| Need to distinguish known evidence, assumptions, and evidence gaps | Evidence Scoping | source inventory and confidence labels |

| Need to merge several walkthrough results into non-duplicative findings | Simulation Synthesis | clustering, root causes, severity, and traceability |

| Need to hand research findings to a designer or implementer | Findings Communication | reproducible evidence and actionable finding structure |

| Need to inspect an existing repository, running product, capture, or ticket | Live Product Grounding | grounded surface and behavior claims |

| Need to define what each actor should attempt in a walkthrough | Actor-Walk Script Design | goals, starting state, stress probes, and observable success |

| Need to record a walkthrough so another person can reproduce it | Walkthrough Evidence | per-step expected/observed evidence |

| Need to learn from a user-supplied competitor, screenshot, or reference | Reference Patterns | borrowed patterns and deliberate differences without market theater |

| Need to define evidence-backed Personas, Actors, permissions, or constraints | User Modeling | provenance-aware user and authority models |

| Need to decompose an actor goal into operations and workflow steps | Task Analysis | outcome-oriented task structure and working sets |

Working rule

Use the smallest sufficient reference set. Common pairs are evidence scoping +

live grounding before a study, and actor-walk design + walkthrough evidence for

a reproducible session. Preserve permissions, states, failures, recovery,

relationships, and evidence limits. Route elsewhere only when another

capability's decision materially changes the research plan.

How to use it

Copy the folder

Take aryaniyaps/lamina-research from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.