Menu
Conducts deep research on a topic and creates detailed reference documentation with source attribution and best practices.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Helps users connect and use a service in Rebel when it isn't already in the built-in connector catalog. Acts as an expert advisor — runs the full build-vs-buy check (catalog, MCP Registry, community) before scaffolding a custom MCP server and guiding research, implementation, security review, and contribution.
Add, update, or remove connectors (MCP servers) in Rebel. Searches the built-in connector catalog first before suggesting custom builds. Handles setup, configuration, and security review for community connectors.
Capture citable sources (meetings, documents, files, media, web content) as structured files in memory/sources/ with provenance metadata for traceability.
Rules for writing error messages, toasts, banners, and recovery copy in Rebel's voice — dry, calm, helpful, and never apologetic. Use whenever you add or rewrite any user-facing error string.
Guides users through adding new tools or capabilities to an existing connector (MCP server). Handles eligibility, workspace setup, connector research, implementation via Software Engineer workflow, local testing, and PR submission with an extension-specific template.
Help users celebrate impactful wins and surface important learnings by analyzing their recent communications and activities.
| name | write-deep-dive-as-doc |
| description | Conducts deep research on a topic and creates detailed reference documentation with source attribution and best practices. |
| last_updated | "2025-10-26T00:00:00.000Z" |
| agent_type | main_agent |
Before starting: Use semantic search (@files) or browse help-for-humans/ and skills/ to see if documentation on this topic already exists.
Do a deep dive on the web about the topic that the user has asked about. If you need more clarification about the requirements to focus the search fruitfully, ask questions (ideally upfront). If you need more context from files, investigate for relevant code & docs.
Before you start, run date to get today's date, in case you need to assess how recent the search results are.
Then write this up as a detailed reference doc, following the instructions in write-help-evergreen-doc.md. Include URL links/references (as well as mentions of your own code/docs etc), so you can track down the original sources later if you need to.
Frontmatter: All documentation files must include YAML frontmatter with at least a one-line description field (may include other optional fields like use_cases, last_updated, tools_required, dependencies, agent_type).
Before diving into research, ask questions:
Follow write-help-evergreen-doc.md format as appropriate, e.g.:
IMPORTANT: Include "See also" section at top of document (after overview/intro) with all research sources:
Remember: The goal is to create a reference that will explain, be up-to-date, help with decision-making, save time, and/or prevent mistakes/issues/surprises. Be proactive. Focus on the information that would be most valuable given the user's intent. Highlight anything worthy of remark.
