Talk Stage2 Research logo

Talk Stage2 Research

CommunityPopular
FlorianBruniaux
talk-stage2-research

Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git repository.

Overview

PublisherFlorianBruniaux
Repositoryclaude-code-ultimate-guide
Skill nametalk-stage2-research
Stars
6.1K
Forks
807
Bundled files
Instructions only
LicenseCC-BY-SA-4.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by FlorianBruniaux on GitHub. Read the source before you install it.

Installation

Install the Talk Stage2 Research AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/examples/skills/talk-pipeline/stage-2-research
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide.git /tmp/claude-code-ultimate-guide
mkdir -p .claude/skills
cp -r /tmp/claude-code-ultimate-guide/examples/skills/talk-pipeline/stage-2-research .claude/skills/talk-stage2-research
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Talk Stage2 Research in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Talk Stage2 Research on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Talk Stage2 Research is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Talk Stage 2: Research (REX mode only)

Builds the git proof for a REX talk. Cross-references git history, CHANGELOG, and the Stage 1 summary to produce a verified timeline and velocity analysis.

Automatically skipped in --concept mode. Only runs when the source material is a REX with git repository access.

When to use this skill

  • After Stage 1 (Extract) when building a REX talk
  • When you have access to the project's git repository
  • To verify metrics mentioned in the source material against actual git data

What this skill does

  1. Reads the summary: understands the period and themes from Stage 1
  2. Git archaeology: extracts velocity metrics (read-only commands only)
  3. Changelog analysis: scans releases, features, documented metrics
  4. Cross-references: aligns git, CHANGELOG, and summary
  5. Builds the timeline: verified dates, not estimated
  6. Writes 3 output files

Input

  • talks/{YYYY}-{slug}-summary.md (from Stage 1, required)
  • repo_path: absolute path to the git repository
  • Optional: CHANGELOG path if different from {repo_path}/CHANGELOG.md

Output

Three files:

  • talks/{YYYY}-{slug}-git-archaeology.md
  • talks/{YYYY}-{slug}-changelog-analysis.md
  • talks/{YYYY}-{slug}-timeline.md

Git Commands (read-only only)

bash
# Commits by month
git -C {repo_path} log --pretty=format:"%Y-%m" | sort | uniq -c

# Commits by contributor
git -C {repo_path} shortlog -sn --no-merges

# First and last date
git -C {repo_path} log --pretty=format:"%ad" --date=short | tail -1
git -C {repo_path} log --pretty=format:"%ad" --date=short | head -1

# Merged PRs (if merge commit convention)
git -C {repo_path} log --merges --oneline | wc -l

# Tags (releases)
git -C {repo_path} tag --sort=version:refname

# Velocity peak (busiest months)
git -C {repo_path} log --pretty=format:"%Y-%m" | sort | uniq -c | sort -rn | head -5

Output formats

git-archaeology.md

markdown
# Git Archaeology: {slug}

**Repo**: {repo_path}
**Period analyzed**: {start date} -> {end date}
**Commands run**: {list}

## Global Metrics

| Metric | Value | Source |
|--------|-------|--------|
| Total commits | {n} | git log |
| Total merges/PRs | ~{n} | git log --merges |
| Total releases (tags) | {n} | git tag |
| Human contributors | {n} | git shortlog |
| Period covered | {n} months | first -> last date |

## Monthly Velocity

| Month | Commits | Notes |
|-------|---------|-------|
| {YYYY-MM} | {n} | {context if notable} |
...

## Contributors

| Rank | Name | Commits | % |
|------|------|---------|---|
| 1 | {name} | {n} | {%} |
...

---
*Generated by talk-stage2-research: {date}*

changelog-analysis.md

markdown
# Changelog Analysis: {slug}

**Source**: {CHANGELOG path}
**Releases analyzed**: {n} (v{first} -> v{last})

## Features by release (summary)

| Release | Date | Key features | Metrics mentioned |
|---------|------|--------------|------------------|
| {version} | {date} | {features} | {metrics} |
...

## Patterns identified

### Acceleration
{Periods of high velocity and what drove them}

### Inflection points
{Direction changes, major releases}

### Verifiable metrics in CHANGELOG
{Exhaustive list of numbers mentioned in CHANGELOG with their release}

---
*Generated by talk-stage2-research: {date}*

timeline.md

markdown
# Factual Timeline: {slug}

**Period**: {start} -> {end} ({n} months)
**Cross-referenced sources**: Summary x Git history x CHANGELOG

---

## Month-by-month timeline

| Month | Commits | Releases | Versions | Key features | Talk event |
|-------|---------|----------|----------|--------------|-----------|
| {YYYY-MM} | {n} | {n} | {versions} | {features} | {anecdote/event} |
...

## Cross-reference: Conflicts and inconsistencies

{If dates or metrics contradict between sources, note here}

---
*Generated by talk-stage2-research: {date}*
*Sources: git log x {CHANGELOG path} x {summary path}*

Key rules

  • Read-only only: no git commands that modify repo state
  • Verify before asserting: a date not found in git = "unverified"
  • Cross-reference: flag inconsistencies between sources, don't pick one arbitrarily
  • Granularity: month by month minimum; week by week if the period is short (< 2 months)

Anti-patterns

  • Running git commands that modify the repository
  • Estimating dates instead of verifying them in git
  • Rounding metrics without flagging it
  • Silently merging contradictory data from different sources
  • Omitting quiet periods (plateaus tell a story too)

Validation checklist

  • Only read-only git commands executed
  • Timeline covers the full period from summary
  • All metrics have an explicit source (git or CHANGELOG)
  • Conflicts between sources flagged in dedicated section
  • 3 files generated and saved

Tips

  • The timeline is what Stage 3 (Concepts) uses to enrich concept scores; a good timeline makes the concept catalogue stronger
  • "Quiet periods" in git velocity often correspond to hardest engineering challenges, worth noting
  • If the CHANGELOG has no version tags, fall back to date-based anchoring

Related

Frequently asked questions

What does the Talk Stage2 Research AI skill do?

Performs git archaeology, changelog analysis, and builds a verified factual timeline by cross-referencing git history with source material. REX mode only (skipped automatically in Concept mode). Use when building a REX talk and you need verified commit metrics, release timelines, and contributor data from a git repository.

Why use Talk Stage2 Research on TypingMind?

Because you install it once and use it with any model. Talk Stage2 Research is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Talk Stage2 Research in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/examples/skills/talk-pipeline/stage-2-research. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Talk Stage2 Research?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Talk Stage2 Research?

As many as you like. As long as a model supports skills, you can use Talk Stage2 Research with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Talk Stage2 Research AI skill free?

Yes. It is published on GitHub by FlorianBruniaux under the CC-BY-SA-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇