Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add daveebbelaar/bama --skill research -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/research/

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.

research Matt Pocock Researches a question through primary sources and saves the findings as a Markdown file in the repository. Use it for API facts, documentation checks, and delegated reading. CX Codex +1 711,295installs research Weizhena This skill does preliminary research on a topic and drafts an outline: a list of items to study plus the fields to capture for each. Useful before an academic review or a tech comparison. CX Codex +1 798installs research Alireza Rezvani research is a Claude Code skill that routes research requests to specialist skills or runs a general search workflow. It shows the routing choice and lets the user override it. CX Codex +1 348installs research JuliusBrussee Gathers verified facts from docs and RFCs into a durable §R research log with sources, preventing agents from hallucinating external APIs. CX Codex +1 810installs research boshu2 research — a skill for Claude Code answers focused questions about code, project history, claims, and recurring patterns with cited evidence. It activates for checks on whether work is really done or a pattern warrants a rule. CX Codex +1 1,500installs ai-research-explore lllllllama ai-research-explore governs deep learning research exploration on top of an existing baseline. It isolates candidate experiments and generates structured comparison reports. CX Codex +1 363,600installs ai-research-reproduction lllllllama ai-research-reproduction is a Claude Code skill for reproducing deep-learning runs from a repository README. It picks a small documented target and saves the evidence bundle to repro_outputs/. CX Codex +1 363,300installs customer-research coreyhaines31 customer-research is a Claude Code skill that extracts insights from customer reviews, interviews, and feedback to reveal what customers need and feel. CX Codex +1 128,400installs amazon-product-research nexscope-ai amazon-product-research evaluates product demand, competition, and FBA margins across Amazon marketplaces. It guides sellers through sourcing viability and entry risks before buying inventory. CX Codex +1 78,400installs firecrawl-deep-research firecrawl firecrawl-deep-research — a skill for Claude Code, Codex, Cursor, GitHub Copilot, and Gemini CLI that pulls evidence from the open web and delivers a structured analytical report with an executive summary, findings, and full sources. CX Codex +1 36,200installs firecrawl-research-papers firecrawl firecrawl-research-papers is a Claude Code skill that finds and synthesizes academic literature into structured reviews from PubMed, bioRxiv, medRxiv, and arXiv. CX Codex +1 34,200installs

From the same set21

The whole set →
improve-loop improve-loop — a Claude Code skill that works through a macOS app’s stories in docs/STORIES.md. It builds the app, checks screen snapshots against references, and commits completed work. CX Codex +1 1,000installs agent-cli agent-cli — a skill for Claude Code, Codex and Cursor that adds a command line and MCP server to a macOS app so agents can control it via a local socket. CX Codex +1 1,000installs build-and-verify build-and-verify — a Claude Code skill that builds SwiftUI macOS apps and checks page snapshots in light and dark appearance. The agent invokes it after UI changes, failed builds, or requests to run or inspect the app. CX Codex +1 1,000installs performance performance — a skill for Claude Code that measures CPU, memory, and energy usage in macOS apps. It identifies causes of freezes and helps offload tasks from the main thread to the GPU. CX Codex +1 1,000installs improve-architecture The improve-architecture Claude Code skill reviews a macOS Swift codebase and plans refactors that preserve existing behavior. It activates before a major feature, at a milestone, or when bugs keep returning in one area. CX Codex +1 1,000installs app-brief The app-brief skill for Claude Code and Cursor generates a one-page docs/BRIEF.md file for a new macOS app before writing code. CX Codex +1 1,000installs design-from-app design-from-app — a Claude Code skill that rebuilds any app interface as a native SwiftUI design kit using reference screenshots. CX Codex +1 1,000installs os-integrations The os-integrations Claude Code skill maps macOS APIs to system-level features and their required permissions. It applies when adding global shortcuts, screen capture, or controls for other apps’ windows. CX Codex +1 1,000installs

Project sponsors

Companies that keep this analytics open