Find Release
flutter/flutter
A skill to find the lowest Dart and Flutter release containing a given commit.
Build a repository that makes findings findable, reusable, and cumulative across teams.
MITAuto-check passed
Install Research Repository
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills research-repository --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-research/skills/research-repository .claude/skills/research-repository && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .claude/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repositoryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills research-repository --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-research/skills/research-repository .agents/skills/research-repository && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .agents/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills research-repository --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-research/skills/research-repository .cursor/skills/research-repository && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .cursor/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path design-research/skills/research-repository--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills research-repository --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-research/skills/research-repository .gemini/skills/research-repository && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .gemini/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills research-repositoryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-research/skills/research-repository .github/skills/research-repository && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .github/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill research-repository -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills research-repository --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-research/skills/research-repository .opencode/skills/research-repository && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "research-repository" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-research/skills/research-repository into .opencode/skills/research-repository/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-repository", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
research-repository- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 728 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a repository that makes findings findable, reusable, and cumulative across teams.
- Works in 3 steps: Insights: discrete, standalone findings… → Studies: the research projects that… → Raw data: transcripts, recordings,…
- The same research keeps getting redone
- SKILL.md covers What You Do, Why Repositories Fail, Repository Architecture and Tagging System, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Research Repository is an agent skill from Owl-Listener/designer-skills. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- The same research keeps getting redone
Example prompts
- “/research-repository”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Insights: discrete, standalone findings ("Users don't understand the difference between X and Y") — the most reusable unit
- Studies: the research projects that produced insights (interview series, usability test, survey) — provides context for evaluating insight…
- Raw data: transcripts, recordings, survey exports — the evidence behind insights; not the primary search target
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Research Repository loads about 1.4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 728 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 728 words, ~1,374 tokens.
Download SKILL.mdSave it as
.claude/skills/research-repository/SKILL.md (or your agent's skills folder).- name
- research-repository
- description
- 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`.
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
- Insights: discrete, standalone findings ("Users don't understand the difference between X and Y") — the most reusable unit
- Studies: the research projects that produced insights (interview series, usability test, survey) — provides context for evaluating insight validity
- Raw data: transcripts, recordings, survey exports — the evidence behind insights; not the primary search target Design the repository so insights are the primary entry point — not studies, not raw data.
Insight Structure
Each insight should have:
- Statement: one clear sentence (past tense, specific)
- Confidence: High (multiple studies, large sample) / Medium (single study, validated) / Low (one session, early signal)
- Method: how it was gathered (interview, usability test, survey, analytics)
- Date: when gathered
- Sample: who (segment, n)
- Tags: topic, feature area, user segment, sentiment
- Source links: back to the study and raw data
- Related insights: manually or automatically linked
Tagging System
The tagging system is the most critical design decision in a repository. Define tags before populating:
Tag Dimensions
- Topic/theme: navigation, onboarding, pricing, notifications, mobile, accessibility…
- Feature or product area: checkout, dashboard, settings, home feed…
- User segment: new users, power users, enterprise, mobile-only, specific personas…
- Sentiment: pain, delight, confusion, trust…
- Recency signal: evergreen vs time-bound findings
- Status: validated, superseded, conflicting
Rules
- Define the controlled vocabulary before anyone starts tagging
- Tags are plural and lowercase:
onboardingnotOnboardingoronboard - Limit to 5–8 tags per insight to prevent tag inflation
- Review and reconcile tags quarterly
Repository Culture and Maintenance
A repository is only as good as the habits around it:
Adding research
- Every study produces a structured summary with tagged insights before it's considered "done"
- Insights are added within one week of study completion
- Raw data (transcripts, recordings) is stored linked to the study record
Show full SKILL.md (306 more words)Show less
Keeping it current
- Quarterly review: mark outdated insights as superseded when new evidence contradicts them
- Link new findings to insights they reinforce or contradict — build the evidence chain
- Archive (don't delete) superseded insights — the history of what you thought and why is valuable
Making it useful
- Weekly or monthly "research digest" to the team highlighting new insights
- Link repository insights in product briefs, design rationale, and PRDs
- When starting new research, search the repository first — what's already known?
Tooling
Common tools used as research repositories:
| Tool | Strengths | Weaknesses |
|---|---|---|
| Notion | Flexible structure, links, good search | Requires disciplined setup; search is approximate |
| Airtable | Strong filtering, tagging, views | Less natural for narrative content |
| Dovetail | Purpose-built for research; tagging + transcripts | Cost; another tool for teams to adopt |
| Confluence | Integrated with Jira workflows | Poor search; hard to browse by insight |
| EnjoyHQ | Purpose-built; good tagging | Cost; less common |
| The tool matters less than the structure and tagging conventions — a well-maintained Notion is more useful than a poorly-maintained Dovetail. |
Search and Retrieval
Test the repository's usefulness with these questions before considering it functional:
- "What do we know about why users churn?" → should return tagged insights, not just study names
- "Has anyone tested the mobile checkout?" → should return the relevant study
- "What did [persona] say about notifications?" → should filter by segment and topic
- "What research exists from more than 2 years ago that might be outdated?" → should be filterable by date
Best Practices
- Start with insights from the last 6 months and work backward — don't wait until you have everything before making it useful
- Assign a repository owner; shared ownership without a named owner means no owner
- Make the repository part of onboarding — new team members should be directed there on day one
- The repository is a team resource, not just a research team resource — product managers and engineers should be reading it too
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in design-research/skills/research-repository of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Research Repository next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Research Repository this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Find Releaseflutter/flutter | 180k | — | ~545 | Automated safety check: Pass | BSD-3-Clause | |
| Fd Findpenpot/penpot | 61k | — | ~882 | Automated safety check: Pass | MPL-2.0 | |
| Cumulative Layout Shiftthedaviddias/Front-End-Checklist | 74k | — | ~438 | Automated safety check: Pass | MIT | |
| Find Matching Tenderssickn33/agentic-awesome-skills | 47k | 1 repos | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Finding Replay For IssuePostHog/posthog | 40k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Fd Find
penpot/penpot
A fast and user-friendly alternative to 'find' - simple syntax, smart defaults, respects gitignore.
Cumulative Layout Shift
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Minimize cumulative layout shift.
Find Matching Tenders
sickn33/agentic-awesome-skills
Find open AU/NZ government tenders matching what a company does, ranked by fit with why and gap analysis.
- Official
Finding Replay For Issue
PostHog/posthog
Finds the most informative session recording linked to an error tracking issue.
Find In Notion
superset-sh/superset
Find what the workspace already says before you answer or write — search Notion, tell the canonical page from the stale copy, and cite what you used.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Questions about Research Repository
What does Research Repository do?
Build a repository that makes findings findable, reusable, and cumulative across teams. Research Repository is an agent skill from Owl-Listener/designer-skills. Build a repository that makes findings findable, reusable, and cumulative across teams.
When should I use Research Repository?
Research Repository fits situations like: the same research keeps getting redone.
How do I install Research Repository in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill research-repository -a claude-code`. Or copy the skill folder (design-research/skills/research-repository in Owl-Listener/designer-skills) into .claude/skills/research-repository in your project. Claude Code loads it when a task matches its description.
How do I install Research Repository in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill research-repository -a codex`. Or copy the skill folder (design-research/skills/research-repository in Owl-Listener/designer-skills) into .agents/skills/research-repository in your project. Codex loads it when a task matches its description.
Can I use Research Repository in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill research-repository -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/research-repository, .gemini/skills/research-repository, .github/skills/research-repository and .opencode/skills/research-repository in your project.
What does Research Repository need to run?
SKILL.md names no scripts, command-line tools or credentials: Research Repository is instructions for the agent only.
Does Research Repository access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Research Repository safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Research Repository use?
Research Repository is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Research Repository use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Research Repository?
Skills that share tags, products or a category with Research Repository: Find Release (flutter/flutter, 180k stars), Fd Find (penpot/penpot, 61k stars), Cumulative Layout Shift (thedaviddias/Front-End-Checklist, 74k stars) and Find Matching Tenders (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Research Repository?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.