ByteRover is a context engineering platform that lets you curate context for your coding agents—patterns, decisions, and learnings. It automatically syncs context across team members and eliminates manual markdown file management.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbyteroverExecute the skills CLI command in your project's root directory to begin installation:
Fetches byterover from junsuzuki1973/openclaw-skill-byterover and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate byterover. Access via /byterover in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
0
upvotes
Run in your terminal
1
installs
1
this week
—
stars
ByteRover is a context engineering platform that lets you curate context for your coding agents—patterns, decisions, and learnings. It automatically syncs context across team members and eliminates manual markdown file management.
API credentials are stored in ~/.clawdbot/byterover-config.json:
{
"apiKey": "your_byterover_api_key_here",
"team": "your_team_name",
"space": "your_space_name"
}
ByteRover CLI requires Node.js 20+ and libsecret for credential storage. This skill uses Docker to provide an isolated environment with all dependencies.
cd ~/.openclaw/workspace/skills/byterover
docker-compose up -d
Login with API Key:
docker-compose exec byterover brv login --api-key $BRV_API_KEY
Initialize Project:
docker-compose exec byterover brv init --headless --team "$BRV_TEAM" --space "$BRV_SPACE"
Check Status:
docker-compose exec byterover brv status --headless --format json
Query Context:
docker-compose exec byterover brv query "What are the testing strategies?" --headless --format json
Curate Context:
docker-compose exec byterover brv curate "Make sure to document API authentication patterns" --headless --format json
Push Changes:
docker-compose exec byterover brv push --headless --format json
Pull Changes:
docker-compose exec byterover brv pull --headless --format json
ByteRover CLI supports headless mode for automation and scripting. Headless mode disables interactive prompts and supports machine-readable JSON output.
brv init (requires --team and --space)brv statusbrv querybrv curatebrv push (auto-skips confirmation)brv pullUse --format to control output:
text (default): Human-readable text outputjson: NDJSON (newline-delimited JSON) for machine parsingInstead of OAuth browser flow, use API key for headless environments:
brv login --api-key $BRV_API_KEY
The Context Tree is ByteRover's structured knowledge system that organizes project context into domains:
Prompt your coding agent:
Use brv query command to check what authentication patterns are used in this project
Agent will execute:
brv query "What authentication patterns are used?" --headless --format json
Check project status:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv status
Add context from terminal:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv curate "Document the API rate limiting strategy"
Query specific knowledge:
~/.openclaw/workspace/skills/byterover/docker-compose exec byterover brv query "How do we handle rate limiting?"
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/status.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv status --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/query.sh
QUERY="${1:-project overview}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv query "$QUERY" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/curate.sh
CONTEXT="${1}"
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv curate "$CONTEXT" --headless --format json
#!/bin/bash
# ~/.openclaw/workspace/skills/byterover/scripts/sync.sh
CONFIG=$(cat ~/.clawdbot/byterover-config.json)
API_KEY=$(echo "$CONFIG" | jq -r '.apiKey')
TEAM=$(echo "$CONFIG" | jq -r '.team')
SPACE=$(echo "$CONFIG" | jq -r '.space')
cd ~/.openclaw/workspace/skills/byterover
echo "Pulling latest context..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv pull --headless --format json
echo "Pushing local changes..."
BRV_API_KEY="$API_KEY" BRV_TEAM="$TEAM" BRV_SPACE="$SPACE" \
docker-compose exec -T byterover brv push --headless --format json
Build image:
cd ~/.openclaw/workspace/skills/byterover
docker-compose build
Start container:
docker-compose up -d
Stop container:
docker-compose down
View logs:
docker-compose logs -f
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
We added byterover from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for byterover matched our evaluation — installs cleanly and behaves as described in the markdown.
byterover reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: byterover is focused, and the summary matches what you get after install.
byterover reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: byterover is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for byterover matched our evaluation — installs cleanly and behaves as described in the markdown.
byterover has been reliable in day-to-day use. Documentation quality is above average for community skills.
byterover has been reliable in day-to-day use. Documentation quality is above average for community skills.
byterover has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 47