Research a person's public track record and give a short credibility assessment. Use only when the user explicitly invokes /who-is-this.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read the deepapi skill first. All search and scraping goes through DeepAPI. Never use built-in search, fetch, or a browser.
Accept a name, handle, URL, or profile screenshot. If missing, ask once; never guess a person.
Verify matching bio, company, location, and photo before deeper research. If identity is ambiguous, stop and ask.
Find their X, LinkedIn, and GitHub first (dedicated endpoints, not site: search). Then run these in parallel:
POST /v1/scrape/github/profile with includeRepos: true, plus recent PRs (POST /v1/scrape/github/search, type: "pulls", query: "author:<username>", sort: "updated").POST /v1/scrape/linkedin/posts, maxItems: 10. Also scrape the LinkedIn profile if you have the slug.POST /v1/research/deep on who they are, what they have actually done, and whether the public story holds.POST /v1/scrape/twitter/search with the handle, sort: "latest", maxItems: 50. Also pull POST /v1/scrape/twitter/user.Follow DeepAPI polling. If a platform is missing or private, say so. Do not invent a profile.
Keep only the 3 facts that best explain who the person is; omit the rest.
Ignore congrats, logo spam, paid "king of X" press, and follower-count flexing.
Maximum 100 words after the header. Use short, plain-English sentences. No tables, sub-bullets, tweet dumps, or research narration.
**Full name** — [@handle](https://x.com/handle) · [LinkedIn](url) · [GitHub](url) · [Site](url)
**Who:** One sentence. Where they are and what they do now.
**Track record:** Max 3 bullets. Only what explains who they are. Dates. Label claims vs verified.
**Verdict:** One line. The archetype, whether the story holds, and why.
Fictional example:
**Jane Doe** — [@janedoe](https://x.com/janedoe) · [LinkedIn](https://linkedin.com/in/janedoe) · [GitHub](https://github.com/janedoe)
**Who:** Berlin solo founder of Acme, an open-source Postgres proxy.
**Track record:**
- 2024–now: Acme founder. 2.1K stars (verified); no revenue (her claim).
- 2019–2024: Backend engineer at Zalando and N26.
- Claims "50K users"; unverified.
**Verdict:** Solo builder with real code; user numbers remain unverified.
Omit a missing profile link instead of faking it.
Follow-ups: 1–3 sentences. Re-scrape only if the first pass missed that platform.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
日本語の概要は準備中です。原文の説明を表示しています。
Keep a Mac awake for a set duration or while a process runs. Use only when the user explicitly invokes /anti-sleep.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify a feature, change, or refactor through questions, then write a build prompt for another agent. Use for /ask-then-build or requests to ask questions before producing an implementation prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Use this when controlling bb. The bb CLI inspects and manages threads, environments, projects, machines, providers, skills, plugins, settings, terminals, and other BB services.
日本語の概要は準備中です。原文の説明を表示しています。
Build, install, and debug bb plugins. Use when the user wants a bb plugin, a sidebar panel, a bb CLI subcommand, an agent tool, a theme, a provider, or to extend bb itself. For running threads and the core bb CLI, use bb-cli instead.
日本語の概要は準備中です。原文の説明を表示しています。
Fire the moment the user proposes a build. Instantly surface the 1-3 consequential choices hidden in their idea. Can also be invoked with /before-building.
日本語の概要は準備中です。原文の説明を表示しています。