research-toolkit

Extract and parse Substack articles with AI analysis

**Core principle:** Every claim is a hypothesis until it survives its own opposite. Your job is not to find pre-existing opposing views — it is to GENERATE the exact opposite of each synthesis and test whether reality supports it.

> "What here is NOT actually working?"

> **Bash is required** for TeamCreate, file existence checks, and git operations.

Hold the contradiction open — do not resolve. Maps where concepts fail against particulars via context-isolated tension tracking. Use when (1) synthesis feels too neat, (2) need what a frame cannot capture, (3) dialectic-spiral resolves when it should hold open. NOT for binary questions, stress-testing claims, or time pressure.

You help prepare tagged stable releases for the ex-cog plugin ecosystem.

Investment intelligence combining power structure analysis with financial data. Composes cui-bono methodology with financial MCP tools for stock analysis, portfolio review, and geopolitical investment impact. Use when (1) should I invest in X, (2) analyze this stock/sector, (3) portfolio review with power awareness, (4) financial data + who benefits analysis. NOT for pure power analysis without financial dimension (use cui-bono skill directly).

Who actually benefits — and at whose expense? Power structure analysis for any domain: geopolitics, corporate behavior, institutional claims, media narratives. Use when (1) who benefits from X, (2) ownership or revolving doors, (3) are these sources independent or echoing one origin, (4) expert has commercial stake in own analysis, (5) multi-polar analysis needed, (6) evaluating institutional claims or frameworks. NOT for stock prices, simple advice, or quick factual lookups.

"What is REALLY at stake here? And for whom?" - STOP. When the matter involves trustworthiness, purchasing decisions, "which is better or more reliable", brand comparisons, marketing claims, corporate behavior, "convince me otherwise", or post-purchase "was this good?" - USE THIS. For technical specs affecting quality (TLC vs QLC, component sourcing) use Light Touch mode. Search and verify even if you think you know. Does NOT trigger for: what to watch/eat/wear, how-to instructions, when/where/who founded, or explicit "just tell me quick."

Am I agreeing because it SOUNDS right, or because it IS right? Recursive adversarial dialectic for testing any claim, finding, or synthesis against its own opposite. Use when convergence feels too easy, when findings need stress-testing, or when any research skill escalates to dialectic depth.

「透镜」 What structure hides in my native grammar? Linguistic frame rotation to escape English-default pattern-recognition. Use when (1) pattern-recognition feels stuck in familiar grooves, (2) abstraction circles without grounding, (3) cross-domain insight feels like same-OS-different-domain, (4) triggers fire (prime hours + why, cat mentions, triple punctuation, water metaphors, embedded digits, high typo density, 7th framework). Includes both cross-language frames (Chinese, Japanese, Sanskrit) AND intra-English language frameworks (E-Prime, Present-Centered, Affirmative, Intransitive).

**Seed question:** *Is this ACTUALLY verified, or did I just say it is?*

What is moving in the macro picture? Geopolitical/macro market indicators. Use when (1) China/US Treasury dynamics, (2) dollar-yield divergence, (3) Brent crude oil / energy price spikes, (4) geopolitical market risk, (5) one-command crisis check, (6) EUR/RON exchange rate monitoring. NOT for stock analysis or fundamentals.

**Seed question:** *Are these sources agreeing independently, or echoing the same origin?*

What does my portfolio actually look like right now? Reads local portfolio snapshots (Tradeville + IBKR) and provides unified analysis. Use when (1) user asks about portfolio, (2) before making investment decisions, (3) when macro indicators change significantly, (4) cross-referencing positions with cui-bono/stonk or macro-monitor analysis.

Where should I start investigating this? Routes research questions to the right methodology based on topic domain, depth needed, and available sources. Use when the research question spans multiple domains or the appropriate methodology is unclear. Not needed when a specific skill (DIP, cui-bono, youtube-research) is already the obvious choice.

**Seed question:** *What is everyone NOT saying about this?*

What are the independent voices actually saying? Extract and analyze long-form content from Substack publications. Use when (1) researching independent journalist perspectives, (2) analyzing a specific Substack publication, (3) building a research corpus from long-form written content, (4) cross-referencing Substack analysis with other sources.

Where does this text need what it excludes? Finds where texts undermine themselves on their own terms via close reading. Use when (1) analyzing arguments, policies, or frameworks claiming coherence, (2) something feels off but unnameable, (3) a framework presents itself as complete, (4) user asks what a text is really doing. NOT for summarization, comprehension, or weaponized dismissal.

How do I get the transcript of this video? Platform-aware extraction for any video source — YouTube, local files, or other platforms. Use when (1) need to transcribe a video for analysis, (2) user provides a video URL, (3) building a knowledge base from video content. Provides multiple methods with guided fallback chain (captions > Whisper > web services). Does NOT trigger for: watching videos, video editing, or non-transcript tasks.

What do practitioners actually DO (not just document)? Methodology for extracting practitioner knowledge from YouTube video transcripts. Use when (1) researching how people actually use a technology, (2) seeking practitioner insights beyond documentation, (3) looking for tips, patterns, or workflows from creators, (4) building a research corpus from video content.