research-repository

Organizes research findings into a tagged, searchable repository of insights, studies, and raw data.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill research-repository
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-repository
Source: https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill research-repository

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research findings often disappear into shared drives and project folders, causing teams to repeat studies and lose accumulated evidence. This Skill designs the structure, tagging conventions, and maintenance rituals that keep research findable and reusable across teams.

Core Features & Use Cases

  • Three-Layer Architecture: Structures repositories around insights (reusable findings), studies (context), and raw data (evidence), with insights as the primary entry point.
  • Controlled Tagging System: Defines tag dimensions for topic, feature area, user segment, sentiment, and status, with rules to prevent tag inflation.
  • Maintenance Rituals: Establishes quarterly reviews, superseding workflows, and research digests so the repository stays current.
  • Use Case: A product team keeps re-running onboarding studies because past findings are buried in old decks. Use this Skill to design a Notion or Airtable repository where every insight is tagged, confidence-rated, and searchable by segment and topic.

Quick Start

Ask the agent to design a research repository structure with tagging conventions and insight templates for your team's existing studies.

Frequently Asked Questions about research-repository

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a UX research repository?

Structure the repository in three layers: insights as the primary searchable unit, studies providing context, and raw data as evidence. Define a controlled tagging vocabulary before populating, and assign a named owner to maintain it.

What tools work best for a research repository?

Common options include Notion for flexible structure, Airtable for filtering and views, Dovetail and EnjoyHQ for purpose-built research tagging, and Confluence for Jira integration. Structure and tagging discipline matter more than the tool choice.

How should research insights be tagged?

Tag across dimensions like topic, feature area, user segment, sentiment, and status, using lowercase plural terms from a controlled vocabulary. Limit each insight to 5-8 tags and reconcile the vocabulary quarterly.

Why do research repositories fail?

Repositories fail when findings are organized by team rather than topic, reports are long and unstructured, tagging is inconsistent, and no one owns maintenance. Insights and raw data also get mixed, making conclusions hard to distinguish from observations.

When should I use affinity diagramming instead of a repository?

Use affinity diagramming when synthesizing findings from a single study. A research repository is for organizing insights across many studies so they accumulate and stay findable over time.