ai-research-os-workshop

Name: ai-research-os-workshop
Author: iusztinpaul

Pending

How to turn your Second Brain into a living research memory that your agents maintain. Workshop with slides, video and code.

51stars

7forks

Python

Installation

# Add to your Claude Code skills
git clone https://github.com/iusztinpaul/ai-research-os-workshop

Getting Started

Guides for using ai agents skills like ai-research-os-workshop.

Caveman: Cut Claude Token Use by 65%
How agent-side prompt compression works, when to use it, and when not to.
What is an AI Skills Marketplace?
Definitions, how marketplaces work, and how to choose between them in 2026.
Getting Started with AI Skills

README.md

Frequently Asked Questions

What is ai-research-os-workshop?

ai-research-os-workshop is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by iusztinpaul. How to turn your Second Brain into a living research memory that your agents maintain. Workshop with slides, video and code. It has 51 GitHub stars.

Is ai-research-os-workshop safe to use?

ai-research-os-workshop's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.

How do I install ai-research-os-workshop?

Clone the repository with "git clone https://github.com/iusztinpaul/ai-research-os-workshop" and add it to your Claude Code skills directory (see the Installation section above).

What programming language is ai-research-os-workshop written in?

ai-research-os-workshop is primarily written in Python. It is open-source under iusztinpaul on GitHub, so you can review or fork the full source.

Are there alternatives to ai-research-os-workshop?

Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ai-research-os-workshop against similar tools.

Agentic AI for Beginners

Build your first AI agent from scratch - tool use, ReAct pattern, memory, deployment

41 minBeginner

Comments (0)

to leave a comment.

No comments yet. Be the first to share your thoughts!

Related Skills

superpowers

by obra

An agentic skills framework & software development methodology that works.

234,966

Mythos-Claude-Orchestrator claude-design-studio-toolkit

I'm always losing my research.

5,000+ notes in Obsidian, 5,000+ highlights in Readwise, plus Notion and Google Drive — growing ~250 files a month. And every research session still starts from zero: paste the same links into Codex, watch it rebuild context on the fly, then lose all of it when the chat ends.

Access to information was never the bottleneck. Reusing it was.

AI Research OS turns your Second Brain into a living research memory your agents maintain — research that compounds over weeks, months, and years instead of dying in a conversation.

Codex or Claude gives you an answer. This gives your harness a reusable research memory:

raw/ - copied or fetched source material
wiki/sources/ - per-source summaries
wiki/concepts/, wiki/entities/, wiki/comparisons/ - reusable synthesis pages
wiki/overview.md and wiki/synthesis.md - the current thesis
index.yaml and index.md - the catalog future agents read first
log.md and wiki/open-questions.md - what happened and what to research next

The point is not to replace Codex. The point is to stop re-researching the same topic every week.

What this is

AI Research OS is a set of local AI skills for building and querying a persistent research wiki from your own sources:

Obsidian notes
Readwise highlights
NotebookLM notebooks
GitHub repos
YouTube videos with public transcripts
web links
PDFs and local files

Via deep research on top of your personal Second Brain

Obsidian is optional. It is just a visual IDE for browsing the generated markdown wiki. The system can run purely through Codex or Claude Code from a normal working directory.

Slides and video

Slides: Google Slide Deck
Video: [] (coming soon)

Whenever You're Ready, Here's How to Go Deeper

Our AI Research OS runs locally via skills.

Our Agent AI Engineering course, built with Towards AI, shows how to ship it to production as a multi-agent system: MCP servers with LangGraph, an evaluator-optimizer loop, observability, evals, and GCP deployment.

35 lessons. 3 end-to-end portfolio projects. A certificate. And a Discord community with direct access to industry experts and me.

Built for software engineers, data engineers, or scientists transitioning into AI engineering.

Rated 5/5 by 300+ students. The first 7 lessons are free:

Start here →

Architecture

Sources flow through deep research, get stored as raw files, indexed, synthesized into a wiki, and then queried:

user question / sources
        |
        v
  /research router
        |
        +--> query existing wiki
        +--> append known sources
        +--> run deep discovery
        |
        v
 raw sources -> source pages -> concepts/entities/comparisons
        |
        v
 index.yaml + overview.md + synthesis.md + open-questions.md

Examples

Three end-to-end runs, each browsable in examples/. Open the linked prompt in Claude Code / Codex with /research to reproduce it; each screenshot shows the resulting wiki browsed in Obsidian.

1. Deep research from an outline + web resources

Discover sources, summarize, and synthesize them into a topic wiki.

How to use it: /research example_1_deep_research/prompt.md

A full research wiki on agentic harnesses, built from a content outline and reference links.

2. Ingest GitHub repos

Compute per-repo notes (architecture, agents, memory, permissions) and cross-repo comparisons, skipping deep discovery.

How to use it: /research example_2_github/prompt.md

Side-by-side comparison pages across three coding-agent repositories.

3. Ingest web links

Pull a handful of specific articles into the wiki without running deep research.

How to use it: /research example_3_ingest_links/prompt.md

Source pages and synthesis built from three custom URLs.

How to use it

Start with a question and a few sources.
Run /research.
Show the generated working-dir/research-<topic>/ directory.
Ask a follow-up question that answers from the existing wiki instead of re-ingesting.
Add a YouTube video or GitHub repo and show the wiki update.

When to use it

Use this when:

you are researching a topic over multiple sessions
you want sources, summaries, claims, and open questions preserved
you want to compare several repos, papers, videos, or notes
you want future Codex / Claude runs to reuse prior research
you want a local markdown wiki you can inspect, edit, and version
you want deep research to write durable artifacts, not just a chat answer

Do not use this when:

you have one simple question
you only need a quick answer from one link
you do not care about saving the result
you need a fully managed hosted knowledge base
you want semantic search infrastructure only, without an agent workflow

Compared to alternatives

Tool	Best for	Limitation	Where `AI Research OS` fits
Codex one-shot	Fast answers, coding help, repo Q&A	The answer is not automatically turned into a durable research workspace	Use Codex directly for simple questions; use this when the research should be reused and extended
NotebookLM	Chatting with a fixed set of uploaded sources	Less programmable, less agent-native, not designed around repo parsing, wiki updates, or repeated source ingestion loops	Creates local files, source pages, indexes, and synthesis that agents can keep editing
Deep research agents	Broad discovery and synthesis	Often produce a one-time report	Stores the report as a living wiki with raw sources, open questions, and append workflows
RAG / vector databases	Retrieval over large corpora	Infrastructure-heavy; retrieval alone does not create source pages, comparisons, or a thesis	Keeps the workflow lightweight and artifact-first; indexing is human/agent-readable
`AI Research OS`	Research that compounds across notes, repos, videos, links, and follow-up questions	More setup than a one-shot prompt	Gives Codex / Claude Code a reusable research workspace

Skills

Skill	What it does
`/research`	Init, append, or query a per-topic research directory.
`/research-distill`	Distill a research directory into a compact `research.md` for a specific piece of content.
`/research-lint`	Health-check a research directory for orphan sources, broken links, stale claims, contradictions, and missing hubs.
`/research-render`	Render wiki pages into slides, charts, canvases, or content briefs.

The shared data contract lives in plugins/ai-research-os/skills/research/CONVENTIONS.md.

Research modes

/research routes requests before doing expensive work:

Mode	Use when	Behavior
`query`	Ask from an existing research directory	Reads `index.yaml` and `wiki/`; no ingest or discovery.
`append`	Add the sources you provide	Ingests the provided sources only; no discovery rounds.
`deep`	Explicitly request deep research	Runs source discovery rounds (at a `fast`/`light`/`deep` depth preset), dedup, and wiki updates.
`init`	Start a new research directory	Creates `working-dir/research-<topic>/`.

Deep discovery is opt-in and runs at one of three depth presets — fast (1 round, 3 queries), light (2 rounds, 3 + 2 queries), or deep (3 rounds, 3 queries each). Long runs show a plan first: selected mode, sources to ingest, expected runtime, and files to write.

In query mode the agent drills down progressively — index summary first, then the source wiki page, then derivatives, and only the raw source if it still needs it — so the context window stays small: