npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

research-discussion-system

v0.1.4

Published

Research Discussion System: structured local research discussions, context persistence, and Obsidian-compatible navigation.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

hanyunseonghanyunseong

Keywords

researchdiscussionmarkdownobsidianagent

Readme

Research Discussion System (RDS)

License: MIT Status: v0.1 scaffold

한국어 | English

Turn AI research discussions into durable, navigable Markdown.

RDS is a local-file research discussion framework for researchers across disciplines. It turns a research project folder into a structured space where AI agents can discuss prior materials, inspect local files, preserve decisions, and leave Markdown records that can be explored with Obsidian or any plain file browser.

RDS is not an Obsidian vault format and is not tied to one AI provider. The source of truth is the RDS project directory and its files.

Quick Start

  1. Install RDS for the AI tool you use.
  2. Open the research project folder you want to organize.
  3. Run the setup workflow.

| Tool | Setup | | ------ | ------------ | | Claude | /rds:setup | | Codex | $rds-setup | | Gemini | /rds:setup |

After installation, the setup workflow asks only a short set of onboarding questions: research field, project topic, project scaffold, linking mode, whether to create a glossary, preferred log tone, and researcher stage. It detects your language from the setup conversation and uses that language for future discussion logs by default.

Based on those answers, it creates an RDS Project with context files, discussion logs, literature notes, metadata, and agent instructions for Claude, Codex, and Gemini. User-facing settings live in 00_context/user_profile.md so they are easy to edit. RDS learns blockers, data formats, tools, and detailed collaboration preferences later during normal discussions.

Install RDS

RDS should be installed through the extension surface of the AI tool you use. The terminal commands in this repository are for maintainers, testers, and source installs.

Claude

You can install RDS from either Claude Desktop or Claude Code.

Option A: Claude Desktop app

  1. Open the Claude Desktop app and switch to the Cowork workspace.
  2. Go to Customize → Browse plugins.
  3. If rds is not visible, add this repository as a marketplace source in the plugin browser:
    • https://github.com/HANYUNSEONG/research-discussion-system
  4. Install plugin ID rds.
  5. Start a task in your research folder and run /rds:setup.

Option B: Claude Code (CLI/Desktop Code)

  1. In Claude Code, add this repository as a marketplace source:

    /plugin marketplace add https://github.com/HANYUNSEONG/research-discussion-system

  2. Install the plugin:

    /plugin install rds

  3. Reload plugins:

    /reload-plugins

  4. Open your research folder and run:

    /rds:setup

The plugin ID is rds.

Codex

For Codex Desktop, two install paths are supported. Option A is recommended for researchers who prefer not to open a terminal.

Option A: Codex Desktop (no separate terminal)

  1. In Codex Desktop, paste:

    $skill-installer install https://github.com/HANYUNSEONG/research-discussion-system/tree/main/skills/rds-installer

  2. Restart Codex Desktop.

  3. Run $rds-installer. The skill checks Node.js prerequisites, shows each install command and waits for your approval, then runs the command from Codex and verifies the install with a smoke test. The first run downloads the npm package and may take 1–2 minutes.

  4. Restart Codex Desktop again so it picks up the operational skills.

  5. Open your research folder and run $rds-setup.

See docs/guides/codex-install.md for the full walkthrough and troubleshooting.

Option B: Terminal (npx)

  1. Install Node.js 20 or newer.

  2. Run:

    npx -y [email protected] codex install --force
npx -y [email protected] codex doctor --smoke-test

  3. Restart Codex Desktop, open your research folder, and run $rds-setup.

Notes:

  • Installed skill files are placed under $CODEX_HOME/skills/rds-* (default ~/.codex/skills/rds-*) — the path Codex Desktop loads.
  • The installer creates a stable local backend wrapper at ~/.rds/bin/rds so Codex can run RDS even when PATH inheritance differs by environment.
  • Windows 10/11 is supported natively. Install Codex via winget install Codex -s msstore. The installer writes rds.cmd (PowerShell/cmd) and rds (Git Bash) wrappers under %USERPROFILE%\.rds\bin\, and skills land at %USERPROFILE%\.codex\skills\. WSL users should run the install inside the WSL environment separately, not reuse the Windows install.
  • Migration from RDS 0.1.2: existing installs under ~/.agents/skills/rds-* are removed automatically by the new install command. Pass --keep-legacy if you want to retain the legacy directories.
  • Legacy Codex plugin marketplace metadata remains in this repository for compatibility experiments, but the recommended path is $rds-installer or the npx commands above.

Gemini

Gemini currently uses reusable custom commands for this RDS workflow rather than the same plugin marketplace model used by Claude and Codex.

For non-technical users, prefer one of these distribution paths:

  1. Use an RDS-enabled project template that already contains .gemini/commands/rds/.
  2. Ask a maintainer to install the RDS command pack globally for your Gemini CLI profile.
  3. If you can use a file browser, copy the rds folder from .gemini/commands/ into the .gemini/commands/ folder of your research project.

A file such as .gemini/commands/rds/setup.toml becomes /rds:setup in Gemini.

Maintainers And Source Installs

Use the source install path only when you are maintaining RDS, preparing a release, or testing a local checkout:

git clone https://github.com/HANYUNSEONG/research-discussion-system.git
cd research-discussion-system
npm install
npm run build
export RDS_HOME="$PWD"
export PATH="$RDS_HOME/bin:$PATH"
rds doctor --repo "$RDS_HOME"

The packaged backend requires Node.js 20 or newer at runtime. TypeScript is only used to build the JavaScript files shipped in dist/.

Release checklist:

  1. Publish or distribute the Claude plugin package using .claude-plugin/plugin.json and .claude-plugin/marketplace.json.
  2. Publish or distribute the Codex installer flow (rds codex install) and keep legacy .agents/plugins/marketplace.json + .codex-plugin/plugin.json metadata aligned if you still test native marketplace behavior.
  3. Distribute the Gemini command pack under .gemini/commands/rds/ or include it in RDS-enabled project templates.
  4. Bump the npx version pin in skills/rds-installer/SKILL.md to match the new package.json version.
  5. Update the $skill-installer URL in this README and README.ko.md to tree/v<version>/skills/rds-installer when cutting a tagged release.

Installation references: Codex app docs, Codex CLI docs, Codex auth docs, Codex Windows guide, Codex plugin build docs, Codex quickstart, Claude Cowork plugins, Claude Code plugins, Claude Code skills, Gemini CLI get started, and Gemini custom commands.

Daily Use

| Goal | Claude | Codex | Gemini | | -------------------- | ----------------------- | ----------------------- | ----------------------- | | Resume context | /rds:resume | $rds-resume | /rds:resume | | Start a discussion | /rds:new-discussion | $rds-new-discussion | /rds:new-discussion | | Save a discussion | /rds:close-discussion | $rds-close-discussion | /rds:close-discussion | | Check project health | /rds:doctor | $rds-doctor | /rds:doctor |

Open the same folder in Obsidian if you want graph navigation, backlinks, wiki links, or Dataview-friendly metadata.

Project Structure

RDS Project
├── 00_context/        # user profile, project identity, decisions, assumptions, open questions
├── 01_*              # field-specific working folders generated by setup
├── 02_*
├── 03_*
├── 04_discussions/   # structured discussion logs and discussion index
├── 05_literature/    # papers, literature notes, reading summaries
└── 99_meta/          # RDS runtime config, agent contract, safety policy

Generated projects also include:

CLAUDE.md    # Claude project memory
AGENTS.md    # Codex / AGENTS.md-compatible instructions
GEMINI.md    # Gemini project context

Learn More

Safety Boundary

RDS is for research discussion and local organization. Do not use it for regulated clinical, patient-identifiable, or compliance-bound data unless your institutional policy explicitly permits the selected AI tool and storage path. De-identify sensitive data before agent discussion.

Status

This repository is an early v0.1 scaffold. The core file protocol is intentionally simple: Markdown, YAML frontmatter, and a small Node.js backend built from TypeScript.

License

MIT. See LICENSE.