Deep research on a topic — use when investigating unfamiliar domains, answering complex questions requiring multiple sources, or when an evaluation flags something for deeper analysis
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
This legacy Tier-2 entry delegates the research method to
.claude/skills/web-research/SKILL.md. Load and follow that skill. Preserve the
structured output below when a caller requires it.
Conduct thorough research on a topic, producing a structured summary with sources and actionable takeaways for Genesis.
topic: <research question>
date: <YYYY-MM-DD>
summary: <3-5 sentence overview>
key_findings:
- finding: <finding>
confidence: high | medium | low
source: <source reference>
action_items:
- <concrete next step>
open_questions:
- <what remains unknown>
docs/architecture/genesis-v3-vision.md — For relevance filteringdocs/architecture/CURRENT.md — the live subsystem map (what Genesis has
today, with freshness stamps); consult before claiming a gap. Enumerate,
don't spot-check.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap
The English summary is being prepared. Showing the original description.
Canonical guide to Genesis browser automation - layers (Camoufox, Chromium, the user's Chrome over CDP, TinyFish, desktop), per-tool timeouts, safety gates, verify-after-act, what a click checks (scroll, hit test, covered targets), overlays, iframes, tabs, and failure diagnosis
The English summary is being prepared. Showing the original description.
This skill should be used when a session BUILDS one Genesis item: implementing a change in a worktree through to opening its PR, including rework from a send-back spec. Load `genesis-development` (the shared core) first. Do NOT load it for driving open PRs to merge (`closing-session`), post-merge verification (`validating-merges`), or specifying a change before it is planned (`spec-session`).
The English summary is being prepared. Showing the original description.
Update Claude Code (the CC CLI / "clog code") to a new version, or bump the pinned CC version. Use when the user asks to update Claude Code, bump the CC pin, evaluate a new CC release, or says "clog code update". Routes to the canonical, standardized process in docs/reference/cc-compatibility.md — do NOT re-derive the update mechanism by grepping every time. Do NOT use for general "what changed in CC" trivia with no intent to update.
The English summary is being prepared. Showing the original description.
This skill should be used when a session's job is to DRIVE OPEN PRs TO MERGE rather than to write new code — "close out the open PRs", "review and fix the open PRs", "what's blocking our PRs", "which PRs are mergeable". It owns the In Review column: it reads each PR's gate status, verifies and fixes review findings on PRs OTHER sessions built, replies in-thread, and merges a PR only under the owner's authorization: a per-PR yes, or the owner's request for closing work covering a PR whose every gate passes. Do NOT load it for building a feature and opening its PR — that is a build session (`build-session`).
The English summary is being prepared. Showing the original description.
Code understanding tool selection. Use when exploring architecture, finding definitions, tracing call chains, assessing blast radius of changes, or debugging code paths in the Genesis codebase.
The English summary is being prepared. Showing the original description.