メニュー
Use subagents to throw more compute at hard problems, keep the main context window clean, and auto-approve safe permissions via hooks. Use when a task is complex, exploratory, or can be parallelized across multiple independent workstreams.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.
Act as a Senior Conversion Strategist to write complete website copy — hero, features, social proof, FAQ, and footer — with persuasion triggers, power words, and character counts. Use when writing or rewriting copy for a landing page, SaaS site, or product launch. Output populates directly into Figma Make layouts.
Run analytics queries against any database using plain English — BigQuery (bq CLI), PostgreSQL, MySQL, SQLite, or any DB with a CLI/MCP/API. Use when you need to pull metrics, analyze data, or answer business questions without writing SQL.
Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate. Use when you have a systems-architect, visual-system-architect, or conversion-copy output and need to convert it into Figma Make–compatible prompts covering hero, features, social proof, CTA, and mobile views.
Autonomously fix bugs from any source — Slack threads, failing CI tests, docker logs, or a plain description. Use when you have a bug report or failing test and want Claude to investigate and fix without step-by-step guidance.
Adversarial code review before a PR — Claude asks hard questions until you pass the test. Also supports elegant rewrites ("scrap this and implement the elegant solution") and spec-driven development. Use before opening any pull request.
| name | subagents |
| description | Use subagents to throw more compute at hard problems, keep the main context window clean, and auto-approve safe permissions via hooks. Use when a task is complex, exploratory, or can be parallelized across multiple independent workstreams. |
| license | MIT |
| compatibility | Designed for Claude Code |
| metadata | {"author":"rajit","version":"1.0"} |
| allowed-tools | Agent |
Invoke this skill when a task is complex, exploratory, or parallel in nature. Subagents keep the main context clean and focused.
Offload independent tasks to separate subagents running simultaneously:
use 5 subagents to explore the codebase
→ Explore entry points and startup
→ Explore React component structure
→ Explore tools implementation
→ Explore state management
→ Explore testing infrastructure
Offload heavy research or analysis to a subagent so the main agent's context stays focused on the implementation.
Route permission requests to a smarter model via a hook:
# More compute on a hard problem
"Refactor the auth system. Use subagents."
# Parallel exploration
"Use 5 subagents to map out every API endpoint and their dependencies"
# Background agent
ctrl+b → runs current task in background agent