research · daveebbelaar — Claude Code skill: what it does, how to install
This Claude Code skill researches a macOS app idea before development. It sends parallel subagents to compare products, user feedback, features, and macOS APIs.
MIT 1,000 installs ★ 1,933 updated 2026-11-05
npx skills add daveebbelaar/bama --skill research -a claude-codeWhat research does
The skill helps shape the first version of a macOS app. It studies apps in a chosen category, gathers praise and complaints from reviews, compares leading products, and checks the macOS APIs, permissions, and limits tied to the idea. Suitable research tracks run in parallel; market and review research always run.
Results go to docs/research/<topic>.md, with findings, a likes-and-dislikes table, a feature matrix, and decisions. Claims are tagged as source-verified, based on knowledge, or unverified and needing a test. If one app becomes the reference, the skill hands off to clone and then app-brief; when the app, browser, or computer-use tools cannot be accessed, it adds links to help pages and screenshots instead.
What it helps with
- compare apps in a category before development
- find recurring praise and complaints in user reviews
- choose first-version features from a competitor comparison
- identify macOS APIs and permissions an app needs
Example prompts for the agent
- Research task apps for Mac and identify features for a first release.
- Compare note-taking app reviews and find recurring complaints.
- Find the macOS APIs needed for an app with global keyboard shortcuts.
How to install research
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill research -a claude-code2Manually: put the files in place
~/.claude/skills/research/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/research/
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill research -a codex2Manually: put the files in place
.agents/skills/research/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill research -a cursor2Manually: put the files in place
.cursor/skills/research/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daveebbelaar/bama skills/plan/research2Manually: put the files in place
.github/skills/research/SKILL.md1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill research -a gemini-cli2Platform CLI
gemini skills install https://github.com/daveebbelaar/bama --path skills/plan/researchManually: put the files in place
.devin/skills/research/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill research -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about research
How do I install research in Claude Code?
Run npx skills add daveebbelaar/bama --skill research -a claude-code. The skill file is installed at ~/.claude/skills/research/SKILL.md.
What does research do?
It investigates macOS apps before development by comparing features and user feedback, then examining relevant system APIs, permissions, and limits. Findings are saved under docs/research/.
How does research label its findings?
Each claim is marked as verified from a source, based on knowledge, or unverified and needing a test. Decisions must cite a verified claim or a planned test.
Source text
SKILL.md · MIT
---
name: research
description: Online research for a macOS app before building it, run as parallel researcher subagents, saved to docs/research/. Use when the user asks what to build, which features matter, how the best apps in a category work, how a macOS API or integration works, or wants a feature comparison.
argument-hint: "<app category or question>"
---
# Research
Research answers three questions before code exists: what the best apps in
the category do, what users love and hate about them, and how macOS lets
you build it. The output feeds `app-brief` and `user-stories`.
## 1. Frame
Write the question in one line, and the decision it informs ("which
features go in version one", "Carbon hotkeys or an event tap"). If the user
gave only a category, the question is "what makes the best <category> app
on the Mac".
## 2. Fan out
Start one subagent per track, in parallel, with the brief below. Pick the
tracks that fit. Four is typical. Market and Reviews always run. Reviews
covers many apps: give each subagent 3 or 4 apps, or the 600 words run out.
| Track | Finds |
| --- | --- |
| Market | The 5 to 8 best apps in the category, their price, platform, and headline features |
| Reviews | Per app: what people like and what they dislike, from App Store and Mac App Store reviews, Reddit, Hacker News, forums, and "switched from X" posts |
| Features | The full feature list of the 2 or 3 leaders, from docs, changelogs, and help pages |
| Design | Screens, interaction details, and keyboard shortcuts of the leaders |
| Platform | The macOS APIs, permissions, and limits each feature needs, and what other apps on this Mac already use (global shortcuts, URL schemes, bundle ids) |
Subagent brief (fill in the brackets):
```text
Research [track] for a native macOS app that [one-line idea].
Question: [the question]. Decision it informs: [decision].
Search the web. Prefer primary sources: official docs, changelogs, Apple
developer docs, WWDC sessions, the app's own help pages. Use reviews and
forums for opinions only. If a source is blocked, say so and use another
(Hacker News, App Store reviews, Mac forums). Do not write any files.
Tag every claim: [V] verified in a source (give the URL), [K] from your
own knowledge, [U] unverified, must be tested.
Return at most 600 words: a findings list, a table where it helps, and
the 3 things that matter most for the decision. No intro, no summary.
```
## 3. Merge
Write one file per question: `docs/research/<topic>.md`.
```markdown
# <Topic>
Research for <AppName>. Done <YYYY-MM-DD>.
[V] verified in a source, [K] from knowledge, [U] unverified, test first.
## Findings
- ... [V](url)
## Likes and dislikes
| App | People like | People dislike | Sources |
| --- | --- | --- | --- |
| App A | <3 to 5 points, most mentioned first> | <3 to 5 points> | <urls> |
Patterns: <likes that repeat across apps (must have), dislikes that repeat
(our chance to do better)>
## Feature matrix
| Feature | App A | App B | App C | Version one? |
## Decisions
1. <decision>, because <finding>. Planned test: <test, for a [U] finding>.
## Open questions
- <[U] claim and how to test it>
```
Keep the feature matrix: `user-stories` turns its "Version one?" column
into stories. Every "People like" point maps to a decision or to an
"accepted gap" line in the brief, so nothing loved is dropped by accident.
Check whether a system store (EventKit for reminders and calendars,
CloudKit) gives sync and phone capture for free. Turn each `[U]` that a decision depends on into a test before
you trust it (a probe script, a self-test step, or a preview field in the
reference app).
## 4. Hand off
Call the Skill tool with `clone` if one app stands out as the reference
and you can open it. If it is not installed, or computer use and a browser
are not available, link its public help pages and screenshots in the
research file instead. Then call the Skill tool with `app-brief`.
Done when every track returned, the file has a likes and dislikes table
for every app in the market list, a feature matrix, and a decision list,
and every decision cites a `[V]` or a planned test.
© daveebbelaar · MIT · daveebbelaar/bama
Similar skills
SKILL.md skills catalog →research by other authors comes first.