explain-topic

Synthesize repository files and web sources into tiered topic briefings.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/alexwox/genesis-template --skill explain-topic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-topic
Source: https://github.com/alexwox/genesis-template/tree/main/.cursor/skills/explain-topic
Command: npx skills add https://github.com/alexwox/genesis-template --skill explain-topic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps users rapidly recall, internalize, and explore a topic by synthesizing what the repository already contains with targeted external research when needed, avoiding duplicated effort and reducing the time to actionable understanding.

Core Features & Use Cases

  • Local-first synthesis: Searches repository files, idea notes, Hormozi assets, and existing skills to produce a concise, coherent narrative that connects decisions, open questions, and implications.
  • Tiered briefing: Always provides a short TLDR first, then deeper analysis on request (full reasoning chains, source citations, and links to relevant files).
  • Hybrid routing: Automatically chooses between repo-only synthesis, external research, or a hybrid approach and clearly labels which claims come from which source.
  • Use Case: Use when asking "/explain retention" or "Catch me up on the Hormozi pricing framework" to get a 2-3 minute synthesis with cited source files and suggested next actions.

Quick Start

Explain the topic "retention" using repository files first, give a 2-3 sentence TLDR, list key decisions and open questions, and state whether web research is needed.

Frequently Asked Questions about explain-topic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize repository files with external web research for a topic summary?

To synthesize repository files with web research, the system searches local documentation first, ranks findings, and performs targeted web research to fill gaps, labeling all sources. This hybrid routing produces a concise, tiered briefing with a TLDR and deeper analysis.

What is the best way to get a quick TLDR and refresher on internal project documentation?

The best way to get a quick TLDR on internal documentation is using a local-first synthesis approach. It scans repository files, idea notes, and existing skills to produce a short 2-3 sentence summary, listing key decisions and open questions before attempting external research.

Can I compare and synthesize topics across local files and external sources?

Yes, you can compare and synthesize across local files and external sources. The system uses hybrid routing to combine repository assets with targeted web research, clearly labeling which claims come from local documentation and which from external web findings.

Does the briefing tool show source citations and links to relevant files?

Yes, the briefing tool shows source citations and links to relevant files. After providing the initial TLDR, it offers deeper analysis on request that includes full reasoning chains, source citations, and direct links to the underlying repository files.

When should I use a tiered briefing instead of just searching my repository directly?

You should use a tiered briefing when you need to rapidly recall and internalize a topic without duplicated effort. It synthesizes scattered repository files into a coherent narrative connecting decisions and implications, automatically filling knowledge gaps with labeled web research.

What are the limitations of using hybrid research for local documentation synthesis?

A limitation of hybrid research is that synthesis quality depends on existing repository contents. If local files lack substantive findings, the system must rely heavily on targeted web research, meaning the briefing may reflect external information rather than internal project decisions.