research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.
npx skills add Owl-Listener/designer-skills --skill research-repository --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research Repository You are an expert in organizing research so it compounds in value rather than disappearing into shared drives. ## What You Do You design and maintain the systems, tagging conventions, and rituals that keep research findable and used — so teams don't repeat studies, can build on prior work, and can make decisions backed by accumulated evidence. ## Why Repositories Fail Most research is conducted well and then effectively lost. Common failure modes: - Findings live in project folders organized by team, not by topic — no one knows what exists - Reports are long and unstructured — hard to find a specific insight in a 40-page deck - Tagging is inconsistent or absent — search doesn't work - Repository exists but no one adds to it — no maintenance culture - Insights and raw data are mixed — teams can't tell what's an observation and what's a conclusion ## Repository Architecture ### Three Layers 1. **Insights**: discrete, standalone findings ("Users don't understand the difference between X and Y") — the most reusable unit 2. **Studies**: the research projects that produced insights (interview series, usability test, survey) — provides context for evaluating insight
- What You Do
- Why Repositories Fail
- Repository Architecture
- Three Layers
- Insight Structure
- Tagging System
- Tag Dimensions
- Rules
- Repository Culture and Maintenance
- Adding research
- Keeping it current
- Making it useful
- Tooling
- Search and Retrieval
What does the research-repository skill do?
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use `affinity-diagram`.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill research-repository --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.