build-research-repository

Atomize research findings into tagged, sourced, reusable insight nuggets with governance gates.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill build-research-repository-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-research-repository
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/build-research-repository
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill build-research-repository-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research findings typically die in a readout deck, forcing teams to re-run studies that were already answered. This Skill turns each finding into an atomic, tagged, traceable nugget and governs the repository so insight compounds across projects instead of resetting every study. ## Core Features & Use Cases - Atomic nugget format: Every insight is stored as observation + 4-axis tags (theme, persona, product area, JTBD) + mandatory source, with confidence, evidence, decision link, and status fields. - Two governance gates: Gate 1 queries the repository before any new study to avoid re-research; Gate 2 files nuggets at the end of every synthesis so no finding goes unfiled. - Situational storage: Routes visual content to Figma/FigJam and written content to Docs/Markdown under one shared controlled tag taxonomy. - Use Case: Before recruiting for a new chatbot study, query the repo by persona and JTBD, find an existing nugget proving the stylist-trust barrier, and narrow the study to only the genuinely unknown questions. ## Quick Start Ask the AI to atomize the findings from your latest research synthesis into tagged, sourced nuggets and check the repository for existing evidence before planning the next study.

Frequently Asked Questions about build-research-repository

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

FAQPage Schema
How do I build a UX research repository?

Store each finding as an atomic nugget containing one self-contained observation, tags on four axes (theme, persona, product area, JTBD), and a mandatory source with participant, study, date, and context. File nuggets at the end of every synthesis and query the repository before starting any new study.

What is an atomic research nugget?

An atomic research nugget is a single self-contained finding packaged with tags and a traceable source, based on Tomer Sharon's atomic research model. A nugget missing its source is treated as opinion, not evidence, and is not filed.

How do I tag research findings for reuse?

Tag every nugget on four axes: theme or topic, persona or segment, product or feature area, and job-to-be-done. Keep the vocabulary controlled per axis so two people tagging the same nugget land on identical tags, and define any new tag with a one-line definition.

Should research repositories live in Figma or documents?

Route by content type: visual and spatial material like affinity clusters and journey maps goes to Figma or FigJam, while written findings, quotes, and transcripts go to Docs or Markdown. The tag taxonomy must be identical across both homes so cross-content queries return everything.

When should I not reuse an existing research finding?

Treat a stored nugget as a miss when its confidence is too low for the decision, its segment or context does not match the new question, or the thing it describes has been redesigned since filing. Mark invalidated nuggets as Superseded rather than deleting them to preserve the audit trail.