[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FGQJK8EEKZF2H5TMXY0985":3,"skill-same:01M6FGQJK8EEKZF2H5TMXY0985":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6FGQJK8EEKZF2H5TMXY0985","byterover-headless",null,"Query and curate knowledge-base using ByteRover CLI. Use `brv query` for knowledge retrieval, `brv curate` for adding context, and `brv push\u002Fpull` for syncing.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fbyteroverinc\u002Fbyterover-headless\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"byterover","byterover headless","use","Knowledge Retrieval","retrieval","knowledge-base","query","base","curate","cli","install","context","node","knowledge","npm","push","pull","2026-11-10 10:12:30",false,"---\nname: byterover-headless\ndescription: \"Query and curate knowledge-base using ByteRover CLI. Use `brv query` for knowledge retrieval, `brv curate` for adding context, and `brv push\u002Fpull` for syncing.\"\nmetadata: {\"moltbot\":{\"emoji\":\"?\",\"requires\":{\"bins\":[\"brv\"]},\"install\":[{\"id\":\"npm\",\"kind\":\"node\",\"package\":\"@byterover\u002Fcli\",\"bins\":[\"brv\"],\"label\":\"Install ByteRover CLI (npm)\"}]}}\n---\n\n# ByteRover Knowledge Management\n\nUse the `brv` CLI to manage your own knowledgebase. ByteRover maintains a context tree that stores patterns, decisions, and implementation details about a project.\n\n**IMPORTANT**: For headless\u002Fautomated use, always add `--headless --format json` flags to get machine-parseable JSON output.\n\n## Setup (Headless)\n\n- ByteRover can be fully set up in headless mode. If user has not logged in or initialized `.brv\u002F` in the current working directory (check via `projectInitialized` and and `authStatus` in `brv status --headless --format json\n` response), ask them to provide:\n1. **API key** - for authentication (obtain from https:\u002F\u002Fapp.byterover.dev\u002Fsettings\u002Fkeys)\n2. **Team and space** - names or IDs for project initialization\n\n### Login with API Key\n\nAuthenticate using an API key:\n\n```bash\nbrv login --api-key \u003Ckey>\n```\n\nOutputs text: `Logged in as \u003Cemail>` on success.\n\n### Initialize Project\n\nInitialize ByteRover for a project (requires team and space for headless mode - can use either ID or name):\n\n```bash\n# Using names\nbrv init --headless --team my-team --space my-space --format json\n\n# Using IDs\nbrv init --headless --team team-abc123 --space space-xyz789 --format json\n```\n\nForce re-initialization:\n```bash\nbrv init --headless --team my-team --space my-space --force --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"init\",\n  \"data\": {\n    \"status\": \"success\",\n    \"teamName\": \"MyTeam\",\n    \"spaceName\": \"MySpace\",\n    \"configPath\": \"\u002Fpath\u002Fto\u002Fproject\u002F.brv\u002Fconfig.json\"\n  }\n}\n```\n\n**Note**: You can use either team\u002Fspace names or IDs. Names are matched case-insensitively.\n\n### Check Status\n\nCheck the current status of ByteRover and the project:\n\n```bash\nbrv status --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"status\",\n  \"data\": {\n    \"cliVersion\": \"1.0.0\",\n    \"authStatus\": \"logged_in\",\n    \"userEmail\": \"user@example.com\",\n    \"projectInitialized\": true,\n    \"teamName\": \"MyTeam\",\n    \"spaceName\": \"MySpace\",\n    \"mcpStatus\": \"connected\",\n    \"contextTreeStatus\": \"has_changes\"\n  }\n}\n```\n\n## Query Knowledge\n\nAsk questions to retrieve relevant knowledge:\n\n```bash\nbrv query \"How is authentication implemented?\" --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"query\",\n  \"data\": {\n    \"status\": \"completed\",\n    \"result\": \"Authentication uses JWT tokens...\",\n    \"toolCalls\": [{\"tool\": \"search_knowledge\", \"status\": \"success\", \"summary\": \"5 matches\"}]\n  }\n}\n```\n\n## Curate Context\n\nAdd new knowledge or context to the project's context tree:\n\n```bash\nbrv curate \"Auth uses JWT with 24h expiry. Tokens stored in httpOnly cookies via authMiddleware.ts\" --headless --format json\n```\n\nInclude specific files for comprehensive context (max 5 files):\n```bash\nbrv curate \"Authentication middleware validates JWT tokens\" --files src\u002Fmiddleware\u002Fauth.ts --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"curate\",\n  \"data\": {\n    \"status\": \"queued\",\n    \"taskId\": \"abc123\",\n    \"message\": \"Context queued for processing\"\n  }\n}\n```\n\n## Push Context Tree\n\nPush local context tree changes to ByteRover cloud storage:\n\n```bash\nbrv push --headless --format json -y\n```\n\nThe `-y` flag skips confirmation prompt (required for headless mode).\n\nPush to a specific branch:\n```bash\nbrv push --branch feature-branch --headless --format json -y\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"push\",\n  \"data\": {\n    \"status\": \"success\",\n    \"added\": 3,\n    \"edited\": 1,\n    \"deleted\": 0,\n    \"branch\": \"main\",\n    \"url\": \"https:\u002F\u002Fapp.byterover.com\u002Fteam\u002Fspace\"\n  }\n}\n```\n\nPossible statuses:\n\n- `success` - Push completed\n- `no_changes` - No context changes to push\n- `cancelled` - Push was cancelled\n- `error` - Push failed\n\n## Pull Context Tree\n\nPull context tree from ByteRover cloud storage:\n\n```bash\nbrv pull --headless --format json\n```\n\nPull from a specific branch:\n```bash\nbrv pull --branch feature-branch --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"pull\",\n  \"data\": {\n    \"status\": \"success\",\n    \"added\": 5,\n    \"edited\": 2,\n    \"deleted\": 1,\n    \"branch\": \"main\",\n    \"commitSha\": \"abc123def\"\n  }\n}\n```\n\nPossible statuses:\n\n- `success` - Pull completed\n- `local_changes` - Local changes exist, push first\n- `error` - Pull failed\n\n## Error Handling\n\nAlways check the `success` field in JSON responses:\n\n- `success: true` - Operation completed successfully\n- `success: false` - Operation failed, check `data.error` or `data.message` for details\n\nCommon error scenarios:\n- **Not authenticated**: Run `brv login --api-key \u003Ckey>`\n- **Project not initialized**: Run `brv init --headless --team \u003Cteam> --space \u003Cspace> --format json`\n- **Local changes exist**: Push local changes before pulling\n\n## Tips\n1. For pull and push operations, you should ask for user permission first.\n2. Always use `--headless --format json` for automation (except `brv login` which outputs text).\n3. Check `brv status --headless --format json` first to verify auth and project state.\n4. For curate operations, include relevant files with `--files` for better context.\n5. Query responses may include tool call details showing what knowledge was searched.\n6. For push operations, always use `-y` to skip confirmation in headless mode. For re-initialization, use `-f` to force re-initialization.\n7. Pull will fail if there are unpushed local changes - push first.\n","# ByteRover Knowledge Management\n\nUse the `brv` CLI to manage your own knowledgebase. ByteRover maintains a context tree that stores patterns, decisions, and implementation details about a project.\n\n**IMPORTANT**: For headless\u002Fautomated use, always add `--headless --format json` flags to get machine-parseable JSON output.\n\n## Setup (Headless)\n\n- ByteRover can be fully set up in headless mode. If user has not logged in or initialized `.brv\u002F` in the current working directory (check via `projectInitialized` and and `authStatus` in `brv status --headless --format json\n` response), ask them to provide:\n1. **API key** - for authentication (obtain from https:\u002F\u002Fapp.byterover.dev\u002Fsettings\u002Fkeys)\n2. **Team and space** - names or IDs for project initialization\n\n### Login with API Key\n\nAuthenticate using an API key:\n\n```bash\nbrv login --api-key \u003Ckey>\n```\n\nOutputs text: `Logged in as \u003Cemail>` on success.\n\n### Initialize Project\n\nInitialize ByteRover for a project (requires team and space for headless mode - can use either ID or name):\n\n```bash\n# Using names\nbrv init --headless --team my-team --space my-space --format json\n\n# Using IDs\nbrv init --headless --team team-abc123 --space space-xyz789 --format json\n```\n\nForce re-initialization:\n```bash\nbrv init --headless --team my-team --space my-space --force --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"init\",\n  \"data\": {\n    \"status\": \"success\",\n    \"teamName\": \"MyTeam\",\n    \"spaceName\": \"MySpace\",\n    \"configPath\": \"\u002Fpath\u002Fto\u002Fproject\u002F.brv\u002Fconfig.json\"\n  }\n}\n```\n\n**Note**: You can use either team\u002Fspace names or IDs. Names are matched case-insensitively.\n\n### Check Status\n\nCheck the current status of ByteRover and the project:\n\n```bash\nbrv status --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"status\",\n  \"data\": {\n    \"cliVersion\": \"1.0.0\",\n    \"authStatus\": \"logged_in\",\n    \"userEmail\": \"user@example.com\",\n    \"projectInitialized\": true,\n    \"teamName\": \"MyTeam\",\n    \"spaceName\": \"MySpace\",\n    \"mcpStatus\": \"connected\",\n    \"contextTreeStatus\": \"has_changes\"\n  }\n}\n```\n\n## Query Knowledge\n\nAsk questions to retrieve relevant knowledge:\n\n```bash\nbrv query \"How is authentication implemented?\" --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"query\",\n  \"data\": {\n    \"status\": \"completed\",\n    \"result\": \"Authentication uses JWT tokens...\",\n    \"toolCalls\": [{\"tool\": \"search_knowledge\", \"status\": \"success\", \"summary\": \"5 matches\"}]\n  }\n}\n```\n\n## Curate Context\n\nAdd new knowledge or context to the project's context tree:\n\n```bash\nbrv curate \"Auth uses JWT with 24h expiry. Tokens stored in httpOnly cookies via authMiddleware.ts\" --headless --format json\n```\n\nInclude specific files for comprehensive context (max 5 files):\n```bash\nbrv curate \"Authentication middleware validates JWT tokens\" --files src\u002Fmiddleware\u002Fauth.ts --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"curate\",\n  \"data\": {\n    \"status\": \"queued\",\n    \"taskId\": \"abc123\",\n    \"message\": \"Context queued for processing\"\n  }\n}\n```\n\n## Push Context Tree\n\nPush local context tree changes to ByteRover cloud storage:\n\n```bash\nbrv push --headless --format json -y\n```\n\nThe `-y` flag skips confirmation prompt (required for headless mode).\n\nPush to a specific branch:\n```bash\nbrv push --branch feature-branch --headless --format json -y\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"push\",\n  \"data\": {\n    \"status\": \"success\",\n    \"added\": 3,\n    \"edited\": 1,\n    \"deleted\": 0,\n    \"branch\": \"main\",\n    \"url\": \"https:\u002F\u002Fapp.byterover.com\u002Fteam\u002Fspace\"\n  }\n}\n```\n\nPossible statuses:\n\n- `success` - Push completed\n- `no_changes` - No context changes to push\n- `cancelled` - Push was cancelled\n- `error` - Push failed\n\n## Pull Context Tree\n\nPull context tree from ByteRover cloud storage:\n\n```bash\nbrv pull --headless --format json\n```\n\nPull from a specific branch:\n```bash\nbrv pull --branch feature-branch --headless --format json\n```\n\nExample response:\n```json\n{\n  \"success\": true,\n  \"command\": \"pull\",\n  \"data\": {\n    \"status\": \"success\",\n    \"added\": 5,\n    \"edited\": 2,\n    \"deleted\": 1,\n    \"branch\": \"main\",\n    \"commitSha\": \"abc123def\"\n  }\n}\n```\n\nPossible statuses:\n\n- `success` - Pull completed\n- `local_changes` - Local changes exist, push first\n- `error` - Pull failed\n\n## Error Handling\n\nAlways check the `success` field in JSON responses:\n\n- `success: true` - Operation completed successfully\n- `success: false` - Operation failed, check `data.error` or `data.message` for details\n\nCommon error scenarios:\n- **Not authenticated**: Run `brv login --api-key \u003Ckey>`\n- **Project not initialized**: Run `brv init --headless --team \u003Cteam> --space \u003Cspace> --format json`\n- **Local changes exist**: Push local changes before pulling\n\n## Tips\n1. For pull and push operations, you should ask for user permission first.\n2. Always use `--headless --format json` for automation (except `brv login` which outputs text).\n3. Check `brv status --headless --format json` first to verify auth and project state.\n4. For curate operations, include relevant files with `--files` for better context.\n5. Query responses may include tool call details showing what knowledge was searched.\n6. For push operations, always use `-y` to skip confirmation in headless mode. For re-initialization, use `-f` to force re-initialization.\n7. Pull will fail if there are unpushed local changes - push first.\n",{"name":5,"metadata":40,"description":7},{"moltbot":41},{"emoji":42,"install":43,"requires":49},"?",[44],{"id":32,"bins":45,"kind":30,"label":47,"package":48},[46],"brv","Install ByteRover CLI (npm)","@byterover\u002Fcli",{"bins":50},[46],"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fbyteroverinc\u002Fbyterover-headless",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add kbarbel640-del\u002Fskills --skill byterover-headless",{"tool":64,"command":65},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill byterover-headless",{"tool":67,"command":68},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill byterover-headless","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fbyteroverinc\u002Fbyterover-headless\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"_meta.json","REFERENCE","参考文档",296,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fbyteroverinc\u002Fbyterover-headless\u002F_meta.json",[79,110,138,159,165,185],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":35},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":35},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[122,93,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,98,20],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","design","strategy","headless","compete","submit","matchmaking",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"publishedAt":35},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000021","资料检索与研究",[148,149,150,151,152,153,154,94,155,136,20,156,93,157,158],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http","via",{"skillNo":160,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":35},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[163],{"categoryNo":145,"categoryName":146,"taxonomyType":119,"taxonomyTypeDesc":120},[151,150,149,148,158,153,154,94,152,136,20,155,156,93,157],{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":35},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[172,173,174,175,176,177,178,179,180,181,182,183,184],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":195,"publishedAt":35},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[191,192],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},{"categoryNo":193,"categoryName":194,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000037","律师与法务",[196,197,198,199,94,24,25,51,200,156,201,202,203,204,205,107,206,207,208],"agent constitution","constitution","contracts","tree","log","check","Rules","projects","compliance","actions","state","governance","github"]