vibe-research

Sync research code with paper.md and doc/ across project lifecycles.

25|5|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Zhangyanbo/vibe-research-skill --skill vibe-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-research
Source: https://github.com/Zhangyanbo/vibe-research-skill/tree/main
Command: npx skills add https://github.com/Zhangyanbo/vibe-research-skill --skill vibe-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Bi-directional synchronization between research code, paper.md, and doc/ to keep all surfaces in sync and verifiable.

Core Features & Use Cases

  • Bi-directional sync between code, paper.md, and doc/
  • Project initialization and migration workflows to standard VR structure
  • Automated maintenance of documentation surfaces and session logging

Quick Start

Initialize a new Vibe Research project in your workspace and let the agent organize code and documentation into the standard structure.

Frequently Asked Questions about vibe-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep research code and documentation in sync?

Bi-directional sync between research code and documentation keeps all surfaces verifiable by automatically aligning code changes with paper.md and doc/ files across the full project lifecycle.

What is the best way to migrate existing research workflows to a standardized structure?

Migrating existing workflows to a standardized structure requires an initialization workflow that reorganizes current code and documentation into a consistent VR structure for bi-directional alignment.

How do I initialize a new research project with code and paper documentation?

Initializing a new research project involves setting up a standard structure where the agent organizes code and documentation, ensuring paper.md and doc/ surfaces are maintained from the start.

Does bi-directional code-doc sync support automated session logging?

Bi-directional code-doc sync supports automated session logging by consistently reflecting maintenance updates and session records across both code and research papers.

When do I need bi-directional sync for research code and paper.md files?

Bi-directional sync is needed when maintaining ongoing research environments where code updates must be consistently reflected in paper.md and doc/ files to keep all surfaces verifiable.