Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
A skill your agent uses when user needs are unclear, assumptions need validation, or the design brief identifies gaps in understanding — plans what to learn, which methods to use, and from whom
Install Research Planning
$ npx skills add Owl-Listener/designpowers --skill research-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers research-planning --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/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/research-planning .claude/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .claude/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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/designpowers/tree/main/skills/research-planningType 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/designpowers --skill research-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers research-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/research-planning .agents/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .agents/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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/designpowers --skill research-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers research-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/research-planning .cursor/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .cursor/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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/designpowers.git --path skills/research-planning--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/designpowers --skill research-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers research-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/research-planning .gemini/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .gemini/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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/designpowers research-planningInstalls 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/designpowers --skill research-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/research-planning .github/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .github/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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/designpowers --skill research-planning -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/designpowers research-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/research-planning .opencode/skills/research-planning && 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-planning" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/research-planning into .opencode/skills/research-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research-planning", 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-planning- GitHub stars
- 251
- Token cost
- ~918 tokens
- SKILL.md length
- 371 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when user needs are unclear, assumptions need validation, or the design brief identifies gaps in understanding — plans what to learn, which methods to use, and from whom
- Works in 6 steps: Identify Knowledge Gaps → Frame Research Questions → Select Methods → …
- User needs are unclear
- SKILL.md covers When to Use, Process, Integration and What This Skill Does NOT Do
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Research Planning is an agent skill from Owl-Listener/designpowers. Use when user needs are unclear, assumptions need validation, or the design brief identifies gaps in understanding — plans what to learn, which methods to use, and from whom
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- User needs are unclear
- Assumptions need validation
- The design brief identifies gaps in understanding — plans what to learn
- Which methods to use
Example prompts
- “/research-planning”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb00757. 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 (its code samples are markdown).
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 Planning loads about 918 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 371 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/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 371 words, ~918 tokens.
Download SKILL.mdSave it as
.claude/skills/research-planning/SKILL.md (or your agent's skills folder).- name
- research-planning
- description
- Use when user needs are unclear, assumptions need validation, or the design brief identifies gaps in understanding — plans what to learn, which methods to use, and from whom
Research Planning
Research is how we replace assumptions with evidence. This skill structures what you need to learn before committing to a design direction.
When to Use
- The design brief identifies unknowns about users, context, or behaviour
- The team is making decisions based on assumptions rather than evidence
- A design is being created for a new audience or unfamiliar context
- Stakeholders disagree about user needs
Process
Step 1: Identify Knowledge Gaps
Review the design brief and list:
- What do we know about the people who will use this? (Evidence-backed)
- What do we assume? (Believed but unverified)
- What do we not know? (Acknowledged gaps)
Present this to the user. Assumptions and unknowns become research questions.
Step 2: Frame Research Questions
Convert gaps into answerable questions. Good research questions are:
- Specific — "How do users with screen readers navigate multi-step forms?" not "Is the form accessible?"
- Observable — focused on behaviour, not opinion
- Actionable — the answer will change a design decision
Aim for 3-5 research questions. More than that means you need to narrow scope.
Step 3: Select Methods
Match methods to questions:
| Question Type | Recommended Methods |
|---|---|
| "What do people currently do?" | Journey mapping, diary studies, contextual inquiry |
| "Why do people struggle with X?" | Usability testing, think-aloud protocols |
| "What do people need?" | Interviews, jobs-to-be-done analysis |
| "Which approach works better?" | A/B testing, preference testing, card sorting |
| "How does our offering compare?" | Competitive analysis, heuristic evaluation |
| "Who are we designing for?" | Persona development, ability spectrum mapping |
Show full SKILL.md (131 more words)Show less
Step 4: Plan for Inclusion
Every research plan must address:
- Participant diversity — include people with disabilities, different ages, different technical literacy, different languages
- Method accessibility — ensure research methods themselves are accessible (e.g., interview formats that work for people with communication differences)
- Situational contexts — include scenarios of stress, distraction, low bandwidth, unfamiliar environments
Step 5: Write the Research Plan
# Research Plan: [Topic]
## Research Questions
1. [Question]
2. [Question]
3. [Question]
## Methods
| Method | Questions Addressed | Participants | Timeline |
|--------|-------------------|-------------|----------|
| [Method] | Q1, Q2 | [Who and how many] | [When] |
## Inclusion Considerations
[How participant diversity and method accessibility will be ensured]
## Expected Outputs
[What deliverables this research will produce — personas, journey maps, findings report]
## Decision Points
[Which design decisions this research will inform]Save to: docs/designpowers/research/YYYY-MM-DD-<topic>-plan.md
Step 6: User Review
Present the plan. Confirm scope, methods, and timeline are realistic.
Integration
- Called by:
design-discovery - Calls:
inclusive-personas(when persona development is a research output) - Pairs with:
design-strategy(research informs strategy)
What This Skill Does NOT Do
This skill plans research — it does not execute it. Execution happens with real people in the real world. The plan ensures that when research happens, it is structured, inclusive, and actionable.
© 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 skills/research-planning of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Research Planning 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 Planning this skillOwl-Listener/designpowers | 251 | — | ~918 | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| React Doctormakeplane/plane | 61k | 12 repos | ~657 | Automated safety check: Pass | AGPL-3.0 | |
| Impeccablebestofjs/bestofjs | 3.1k | 26 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None |
Similar skills
- Official
React Doctor
makeplane/plane
Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Tailwindcss Development
anonaddy/anonaddy
Always invoke when the user's message includes 'tailwind' in any form.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Related
Categories
Questions about Research Planning
What does Research Planning do?
A skill your agent uses when user needs are unclear, assumptions need validation, or the design brief identifies gaps in understanding — plans what to learn, which methods to use, and from whom. Research Planning is an agent skill from Owl-Listener/designpowers.
When should I use Research Planning?
Research Planning fits situations like: user needs are unclear; assumptions need validation; the design brief identifies gaps in understanding — plans what to learn; which methods to use.
How do I install Research Planning in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill research-planning -a claude-code`. Or copy the skill folder (skills/research-planning in Owl-Listener/designpowers) into .claude/skills/research-planning in your project. Claude Code loads it when a task matches its description.
How do I install Research Planning in Codex?
Run `npx skills add Owl-Listener/designpowers --skill research-planning -a codex`. Or copy the skill folder (skills/research-planning in Owl-Listener/designpowers) into .agents/skills/research-planning in your project. Codex loads it when a task matches its description.
Can I use Research Planning 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/designpowers --skill research-planning -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-planning, .gemini/skills/research-planning, .github/skills/research-planning and .opencode/skills/research-planning in your project.
What does Research Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Research Planning is instructions for the agent only.
Does Research Planning 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 Planning 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 Planning use?
Research Planning 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 Planning use?
About 918 tokens (SKILL.md is roughly 3.7k 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 Planning?
Skills that share tags, products or a category with Research Planning: Web Artifacts Builder (anthropics/skills, 180k stars), React Doctor (makeplane/plane, 61k stars), Impeccable (bestofjs/bestofjs, 3.1k stars) and Figma Design System Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Research Planning?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.