Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

2 Research

ASecurity

Phase 2 — Parallel research across 4 dimensions. Outputs: home_plans/<project>/research/*.md

8 stars
0 votes
0 copies
0 views
Added 9/20/2026
ai-agentsgodocumentation

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add tstapler/dotfiles --skill 2-research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2 Research?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for 2 Research
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tstapler-2-research/badge)](https://www.skillsdirectory.com/skills/tstapler-2-research)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
description: "Phase 2 — Parallel research across 4 dimensions. Outputs: home_plans/<project>/research/*.md"
user-invocable: true
---

# home:2-research

Spawn 4 parallel subagents to research the home project. All research happens in subagents — the coordinator only reads summaries back.

## Instructions

1. **Follow [SETUP.md](SETUP.md)** — identify PROJECT_NAME, and mark this stage's task `in_progress` if a task tool is available (Check 3).

2. **Entry gate**: Read `home_plans/<PROJECT_NAME>/scope.md`. Halt if missing — run `/home:1-scope` first.

3. **Dispatch 4 research agents in parallel using the `Agent` tool** (all 4 in a single message — do not run sequentially):

   Each agent must include:
   - The full text of `scope.md`
   - Its specific research question
   - An instruction to **write its output directly to the target file** and return a 3-bullet summary
   - **The `meta-research-workflow` skill's Source Documentation Requirements**: cite a full URL and title for every non-obvious factual claim (price, code requirement, safety statistic, common failure mode); no fact without attribution; end the file with a `## Sources` list of every URL cited.

   **Agent 1 — Methods** → writes `home_plans/<PROJECT_NAME>/research/methods.md`:
   > Research the best approach(es) for this home project. What are the standard DIY methods? When does it make sense to hire a professional versus DIY? What specific techniques, tools, or skills are required? What does a professional approach look like versus a competent DIYer? What YouTube channels, subreddits (r/DIY, r/HomeImprovement, r/Plumbing, etc.), or resources are most authoritative for this type of project? Follow the `meta-research-workflow` skill's sourcing requirements. Write your findings to `home_plans/<PROJECT_NAME>/research/methods.md` with a trailing `## Sources` list, then return a 3-bullet summary.

   **Agent 2 — Materials** → writes `home_plans/<PROJECT_NAME>/research/materials.md`:
   > Research the materials, products, and supplies needed for this project. What specific products are community-recommended (not just brand-sponsored)? What are the quality tiers and price ranges? What quantities will be needed? What are the best places to purchase (Lowe's, Home Depot, Amazon, specialty suppliers)? Are there any products to avoid based on common complaints? Follow the `review-longevity-research` skill for how to dig up community reviews and longevity signals, and the `meta-research-workflow` skill's sourcing requirements for every price/quality claim.
   >
   > **Before writing new wiki content**, `Grep`/`Glob` `logseq/pages/` for existing pages on each retailer, product, or part you plan to recommend. If a page already exists, read it and do not duplicate it — only add genuinely new information you learned (a better price, a new caveat, a better source) as an update to that existing page, and reuse it in your links.
   >
   > For each retailer, specific product, or reusable part that does **not** already have a wiki page and is distinctive enough to plausibly recur in future home projects (skip one-off consumables like a single tube of caulk), create a page at `logseq/pages/<Name>.md` following the **Product & Retailer Zettel Template** in the `knowledge-synthesis` skill (core definition, price/quality tier, source URL, links to the retailer and related products, tags including `#[[Products]]`).
   >
   > Write your findings to `home_plans/<PROJECT_NAME>/research/materials.md`, using `[[Product Name]]` wiki-links for anything with a wiki page, with a trailing `## Sources` list, then return a 3-bullet summary plus a list of any new or updated wiki pages.

   **Agent 3 — Logistics** → writes `home_plans/<PROJECT_NAME>/research/logistics.md`:
   > Research the logistical requirements for this project. Are permits required, and if so, what type and approximate cost? What building codes or regulations apply (electrical codes, plumbing codes, structural requirements)? What inspections are required? If hiring a contractor, what licenses should they hold, and what does fair market pricing look like? What is the realistic timeline including drying times, cure times, delivery lead times, and contractor scheduling? Follow the `meta-research-workflow` skill's sourcing requirements for every code/permit claim. Write your findings to `home_plans/<PROJECT_NAME>/research/logistics.md` with a trailing `## Sources` list, then return a 3-bullet summary.

   **Agent 4 — Risks** → writes `home_plans/<PROJECT_NAME>/research/risks.md`:
   > Research the safety hazards, common mistakes, and hidden costs for this type of project. What are the most frequent DIY errors that make the job harder or cause damage? What safety precautions are non-negotiable? What hidden costs or surprises commonly blow budgets? What "while you're in there" work is commonly discovered and how much does it add? What are the failure modes if this is done incorrectly? Follow the `review-longevity-research` skill for mining common-failure-mode clusters from community sources, and the `meta-research-workflow` skill's sourcing requirements for every claim. Write your findings to `home_plans/<PROJECT_NAME>/research/risks.md` with a trailing `## Sources` list, then return a 3-bullet summary.

4. **Wait for all 4 agents to complete.** Do not summarise until all have returned.

5. **Exit gate**: verify all 4 files exist under `home_plans/<PROJECT_NAME>/research/` and are non-trivial (each has real content and a `## Sources` list, not a stub). Mark this stage's task `completed` if a task tool is available, then synthesise the 4 agent summaries:
   ```
   ✅ Phase 2 complete — research written to home_plans/<PROJECT_NAME>/research/

   Key findings:
   - Methods: <1-line summary>
   - Materials: <1-line summary and rough cost estimate>
   - Logistics: <permits required? contractor licensing? timeline?>
   - Top risk: <1 critical pitfall to watch>
   - New/updated wiki pages: <list from Agent 2, or "none">

   Next step: /home:3-plan
   ```

Attribution

tstaplertstapler
View sourceMore from tstapler →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

1023331 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3331 votes

catchup

Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.

611 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →