Help us improve
Share bugs, ideas, or general feedback.
From research-lab
Cross-examine curated knowledge to form a defensible position. Takes a NotebookLM notebook and leading questions, uses structured examination techniques (pattern spotting, paradox hunting, naming the unnamed, contrast creation), and produces named concepts, a decision table, and ranked hypotheses. Works standalone with any notebook. Say "form decisions from this notebook", "cross-examine this research", "seminar on", or "help me form a position on".
npx claudepluginhub cosmicdreams/claude-plugins --plugin research-labHow this skill is triggered — by the user, by Claude, or both
Slash command
/research-lab:seminarThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transform curated research into a defensible position through structured interrogation.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Transform curated research into a defensible position through structured interrogation.
Read ${CLAUDE_PLUGIN_ROOT}/skills/seminar/references/examination-techniques.md for the four techniques.
NotebookLM scripts: Use ${CLAUDE_PLUGIN_ROOT}/scripts/notebook-ask.sh for all notebook queries. Reference: ${CLAUDE_PLUGIN_ROOT}/skills/literary-review/references/notebooklm-cli.md.
Required:
Optional:
03-workshop.md if running in pipelineFrom the leading questions and context, identify:
Use all four techniques from examination-techniques.md. For each, query the notebook with structured questions.
Ask the notebook: "What patterns appear across multiple sources on ? Which patterns are supported by the most evidence?"
Ask the notebook: "What seems true about based on the sources but might not be? Where do sources contradict each other or contradict common wisdom?"
Ask the notebook: "What recurring concepts in the sources don't have a standard name? What behaviors or patterns are described but not labeled?"
Give discovered patterns names. These become the engagement's vocabulary.
Ask the notebook: "Compare vs based on the sources. What does each gain? What does each lose? When would you choose one over the other?"
For each assumption identified in Step 1:
${CLAUDE_PLUGIN_ROOT}/scripts/notebook-ask.sh NOTEBOOK_ID \
"What evidence supports the assumption that <assumption>? What evidence contradicts it?"
Record: assumption, supporting evidence, contradicting evidence, revised confidence.
Write 04-seminar.md:
# Seminar: <topic>
## Decision Frame
<What decision does this inform?>
## Named Concepts
<New vocabulary — patterns we identified and named>
- **<Name>**: <definition and evidence>
- **<Name>**: <definition and evidence>
## Decision Table
| Option | Strengths | Weaknesses | When to Use | Risk |
|--------|-----------|------------|-------------|------|
| ... | ... | ... | ... | ... |
## Ranked Hypotheses
1. **<Hypothesis>** — Confidence: <high/medium/low>
Evidence for: <summary>
Evidence against: <summary>
2. **<Hypothesis>** — Confidence: <high/medium/low>
...
## Assumptions Challenged
| Assumption | Supported? | Key Evidence |
|------------|-----------|--------------|
| ... | ... | ... |
## Open Questions
<What we still don't know and can't answer from the sources>
When used outside of research-lab:run:
VAULT_ROOT="$HOME/Vaults/${OBSIDIAN_VAULT_NAME:-Neurons}"
TOPIC_SLUG="<kebab-case-topic>"
DEST="Research/$TOPIC_SLUG/$(date +%Y-%m-%d)-seminar.md"
mkdir -p "$VAULT_ROOT/$(dirname "$DEST")"
cp "04-seminar.md" "$VAULT_ROOT/$DEST"