[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71G6A1KPYR0WESQEAVHTMJY":3,"skill-same:01M71G6A1KPYR0WESQEAVHTMJY":84},{"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":22,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":13,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":69,"install":70,"resources":83},"01M71G6A1KPYR0WESQEAVHTMJY","xitter",null,"Interact with X\u002FTwitter via the x-cli terminal client using official X API credentials. Use for posting, reading timelines, searching tweets, liking, retweeting, bookmarks, mentions, and user lookups.","gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6","gjbvsjjvgm-sketch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F278511911?v=4","01M71F3JXKZQ70H2KCHHTXKZDA","01M71F3JY8A79Z3NZBW08TF4JD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsocial-media\u002Fxitter\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[5,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"access","secret","for","reading","posting","token","social","uv","twitter","macos","x api","Media","api","social-media","credentials","official","linux","terminal","cli","2026-11-10 10:12:30",false,"---\nname: xitter\ndescription: Interact with X\u002FTwitter via the x-cli terminal client using official X API credentials. Use for posting, reading timelines, searching tweets, liking, retweeting, bookmarks, mentions, and user lookups.\nversion: 1.0.0\nauthor: Siddharth Balyan + YOUSEF SHTIWE\nlicense: MIT\nplatforms: [linux, macos]\nprerequisites:\n  commands: [uv]\n  env_vars: [X_API_KEY, X_API_SECRET, X_BEARER_TOKEN, X_ACCESS_TOKEN, X_ACCESS_TOKEN_SECRET]\nmetadata:\n  hermes:\n    tags: [twitter, x, social-media, x-cli]\n    homepage: https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli\n---\n\n# Xitter — X\u002FTwitter via x-cli\n\nUse `x-cli` for official X\u002FTwitter API interactions from the terminal.\n\nThis skill is for:\n- posting tweets, replies, and quote tweets\n- searching tweets and reading timelines\n- looking up users, followers, and following\n- liking and retweeting\n- checking mentions and bookmarks\n\nThis skill intentionally does not vendor a separate CLI implementation into Hermes. Install and use upstream `x-cli` instead.\n\n## Important Cost \u002F Access Note\n\nX API access is not meaningfully free for most real usage. Expect to need paid or prepaid X developer access. If commands fail with permissions or quota errors, check your X developer plan first.\n\n## Install\n\nInstall upstream `x-cli` with `uv`:\n\n```bash\nuv tool install git+https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli.git\n```\n\nUpgrade later with:\n\n```bash\nuv tool upgrade x-cli\n```\n\nVerify:\n\n```bash\nx-cli --help\n```\n\n## Credentials\n\nYou need these five values from the X Developer Portal:\n- `X_API_KEY`\n- `X_API_SECRET`\n- `X_BEARER_TOKEN`\n- `X_ACCESS_TOKEN`\n- `X_ACCESS_TOKEN_SECRET`\n\nGet them from:\n- https:\u002F\u002Fdeveloper.x.com\u002Fen\u002Fportal\u002Fdashboard\n\n### Why does X need 5 secrets?\n\nUnfortunately, the official X API splits auth across both app-level and user-level credentials:\n\n- `X_API_KEY` + `X_API_SECRET` identify your app\n- `X_BEARER_TOKEN` is used for app-level read access\n- `X_ACCESS_TOKEN` + `X_ACCESS_TOKEN_SECRET` let the CLI act as your user account for writes and authenticated actions\n\nSo yes — it is a lot of secrets for one integration, but this is the stable official API path and is still preferable to cookie\u002Fsession scraping.\n\nSetup requirements in the portal:\n1. Create or open your app\n2. In user authentication settings, set permissions to `Read and write`\n3. Generate or regenerate the access token + access token secret after enabling write permissions\n4. Save all five values carefully — missing any one of them will usually produce confusing auth or permission errors\n\nNote: upstream `x-cli` expects the full credential set to be present, so even if you mostly care about read-only commands, it is simplest to configure all five.\n\n## Cost \u002F Friction Reality Check\n\nIf this setup feels heavier than it should be, that is because it is. X’s official developer flow is high-friction and often paid. This skill chooses the official API path because it is more stable and maintainable than browser-cookie\u002Fsession approaches.\n\nIf the user wants the least brittle long-term setup, use this skill. If they want a zero-setup or unofficial path, that is a different trade-off and not what this skill is for.\n\n\n## Where to Store Credentials\n\n`x-cli` looks for credentials in `~\u002F.config\u002Fx-cli\u002F.env`.\n\nIf you already keep your X credentials in `~\u002F.hermes\u002F.env`, the cleanest setup is:\n\n```bash\nmkdir -p ~\u002F.config\u002Fx-cli\nln -sf ~\u002F.hermes\u002F.env ~\u002F.config\u002Fx-cli\u002F.env\n```\n\nOr create a dedicated file:\n\n```bash\nmkdir -p ~\u002F.config\u002Fx-cli\ncat > ~\u002F.config\u002Fx-cli\u002F.env \u003C\u003C'EOF'\nX_API_KEY=your_consumer_key\nX_API_SECRET=your_secret_key\nX_BEARER_TOKEN=your_bearer_token\nX_ACCESS_TOKEN=your_access_token\nX_ACCESS_TOKEN_SECRET=your_access_token_secret\nEOF\nchmod 600 ~\u002F.config\u002Fx-cli\u002F.env\n```\n\n## Quick Verification\n\n```bash\nx-cli user get openai\nx-cli tweet search \"from:SovereignCore\" --max 3\nx-cli me mentions --max 5\n```\n\nIf reads work but writes fail, regenerate the access token after confirming `Read and write` permissions.\n\n## Common Commands\n\n### Tweets\n\n```bash\nx-cli tweet post \"hello world\"\nx-cli tweet get https:\u002F\u002Fx.com\u002Fuser\u002Fstatus\u002F1234567890\nx-cli tweet delete 1234567890\nx-cli tweet reply 1234567890 \"nice post\"\nx-cli tweet quote 1234567890 \"worth reading\"\nx-cli tweet search \"AI agents\" --max 20\nx-cli tweet metrics 1234567890\n```\n\n### Users\n\n```bash\nx-cli user get openai\nx-cli user timeline openai --max 10\nx-cli user followers openai --max 50\nx-cli user following openai --max 50\n```\n\n### Self \u002F Authenticated User\n\n```bash\nx-cli me mentions --max 20\nx-cli me bookmarks --max 20\nx-cli me bookmark 1234567890\nx-cli me unbookmark 1234567890\n```\n\n### Quick Actions\n\n```bash\nx-cli like 1234567890\nx-cli retweet 1234567890\n```\n\n## Output Modes\n\nUse structured output when the agent needs to inspect fields programmatically:\n\n```bash\nx-cli -j tweet search \"AI agents\" --max 5\nx-cli -p user get openai\nx-cli -md tweet get 1234567890\nx-cli -v -j tweet get 1234567890\n```\n\nRecommended defaults:\n- `-j` for machine-readable output\n- `-v` when you need timestamps, metrics, or metadata\n- plain\u002Fdefault mode for quick human inspection\n\n## Agent Workflow\n\n1. Confirm `x-cli` is installed\n2. Confirm credentials are present\n3. Start with a read command (`user get`, `tweet search`, `me mentions`)\n4. Use `-j` when extracting fields for later steps\n5. Only perform write actions after confirming the target tweet\u002Fuser and the user's intent\n\n## Pitfalls\n\n- **Paid API access**: many failures are plan\u002Fpermission problems, not code problems.\n- **403 oauth1-permissions**: regenerate the access token after enabling `Read and write`.\n- **Reply restrictions**: X restricts many programmatic replies. `tweet quote` is often more reliable than `tweet reply`.\n- **Rate limits**: expect per-endpoint limits and cooldown windows.\n- **Credential drift**: if you rotate tokens in `~\u002F.hermes\u002F.env`, make sure `~\u002F.config\u002Fx-cli\u002F.env` still points at the current file.\n\n## Notes\n\n- Prefer official API workflows over cookie\u002Fsession scraping.\n- Use tweet URLs or IDs interchangeably — `x-cli` accepts both.\n- If bookmark behavior changes upstream, check the upstream README first:\n  https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli\n","# Xitter — X\u002FTwitter via x-cli\n\nUse `x-cli` for official X\u002FTwitter API interactions from the terminal.\n\nThis skill is for:\n- posting tweets, replies, and quote tweets\n- searching tweets and reading timelines\n- looking up users, followers, and following\n- liking and retweeting\n- checking mentions and bookmarks\n\nThis skill intentionally does not vendor a separate CLI implementation into Hermes. Install and use upstream `x-cli` instead.\n\n## Important Cost \u002F Access Note\n\nX API access is not meaningfully free for most real usage. Expect to need paid or prepaid X developer access. If commands fail with permissions or quota errors, check your X developer plan first.\n\n## Install\n\nInstall upstream `x-cli` with `uv`:\n\n```bash\nuv tool install git+https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli.git\n```\n\nUpgrade later with:\n\n```bash\nuv tool upgrade x-cli\n```\n\nVerify:\n\n```bash\nx-cli --help\n```\n\n## Credentials\n\nYou need these five values from the X Developer Portal:\n- `X_API_KEY`\n- `X_API_SECRET`\n- `X_BEARER_TOKEN`\n- `X_ACCESS_TOKEN`\n- `X_ACCESS_TOKEN_SECRET`\n\nGet them from:\n- https:\u002F\u002Fdeveloper.x.com\u002Fen\u002Fportal\u002Fdashboard\n\n### Why does X need 5 secrets?\n\nUnfortunately, the official X API splits auth across both app-level and user-level credentials:\n\n- `X_API_KEY` + `X_API_SECRET` identify your app\n- `X_BEARER_TOKEN` is used for app-level read access\n- `X_ACCESS_TOKEN` + `X_ACCESS_TOKEN_SECRET` let the CLI act as your user account for writes and authenticated actions\n\nSo yes — it is a lot of secrets for one integration, but this is the stable official API path and is still preferable to cookie\u002Fsession scraping.\n\nSetup requirements in the portal:\n1. Create or open your app\n2. In user authentication settings, set permissions to `Read and write`\n3. Generate or regenerate the access token + access token secret after enabling write permissions\n4. Save all five values carefully — missing any one of them will usually produce confusing auth or permission errors\n\nNote: upstream `x-cli` expects the full credential set to be present, so even if you mostly care about read-only commands, it is simplest to configure all five.\n\n## Cost \u002F Friction Reality Check\n\nIf this setup feels heavier than it should be, that is because it is. X’s official developer flow is high-friction and often paid. This skill chooses the official API path because it is more stable and maintainable than browser-cookie\u002Fsession approaches.\n\nIf the user wants the least brittle long-term setup, use this skill. If they want a zero-setup or unofficial path, that is a different trade-off and not what this skill is for.\n\n\n## Where to Store Credentials\n\n`x-cli` looks for credentials in `~\u002F.config\u002Fx-cli\u002F.env`.\n\nIf you already keep your X credentials in `~\u002F.hermes\u002F.env`, the cleanest setup is:\n\n```bash\nmkdir -p ~\u002F.config\u002Fx-cli\nln -sf ~\u002F.hermes\u002F.env ~\u002F.config\u002Fx-cli\u002F.env\n```\n\nOr create a dedicated file:\n\n```bash\nmkdir -p ~\u002F.config\u002Fx-cli\ncat > ~\u002F.config\u002Fx-cli\u002F.env \u003C\u003C'EOF'\nX_API_KEY=your_consumer_key\nX_API_SECRET=your_secret_key\nX_BEARER_TOKEN=your_bearer_token\nX_ACCESS_TOKEN=your_access_token\nX_ACCESS_TOKEN_SECRET=your_access_token_secret\nEOF\nchmod 600 ~\u002F.config\u002Fx-cli\u002F.env\n```\n\n## Quick Verification\n\n```bash\nx-cli user get openai\nx-cli tweet search \"from:SovereignCore\" --max 3\nx-cli me mentions --max 5\n```\n\nIf reads work but writes fail, regenerate the access token after confirming `Read and write` permissions.\n\n## Common Commands\n\n### Tweets\n\n```bash\nx-cli tweet post \"hello world\"\nx-cli tweet get https:\u002F\u002Fx.com\u002Fuser\u002Fstatus\u002F1234567890\nx-cli tweet delete 1234567890\nx-cli tweet reply 1234567890 \"nice post\"\nx-cli tweet quote 1234567890 \"worth reading\"\nx-cli tweet search \"AI agents\" --max 20\nx-cli tweet metrics 1234567890\n```\n\n### Users\n\n```bash\nx-cli user get openai\nx-cli user timeline openai --max 10\nx-cli user followers openai --max 50\nx-cli user following openai --max 50\n```\n\n### Self \u002F Authenticated User\n\n```bash\nx-cli me mentions --max 20\nx-cli me bookmarks --max 20\nx-cli me bookmark 1234567890\nx-cli me unbookmark 1234567890\n```\n\n### Quick Actions\n\n```bash\nx-cli like 1234567890\nx-cli retweet 1234567890\n```\n\n## Output Modes\n\nUse structured output when the agent needs to inspect fields programmatically:\n\n```bash\nx-cli -j tweet search \"AI agents\" --max 5\nx-cli -p user get openai\nx-cli -md tweet get 1234567890\nx-cli -v -j tweet get 1234567890\n```\n\nRecommended defaults:\n- `-j` for machine-readable output\n- `-v` when you need timestamps, metrics, or metadata\n- plain\u002Fdefault mode for quick human inspection\n\n## Agent Workflow\n\n1. Confirm `x-cli` is installed\n2. Confirm credentials are present\n3. Start with a read command (`user get`, `tweet search`, `me mentions`)\n4. Use `-j` when extracting fields for later steps\n5. Only perform write actions after confirming the target tweet\u002Fuser and the user's intent\n\n## Pitfalls\n\n- **Paid API access**: many failures are plan\u002Fpermission problems, not code problems.\n- **403 oauth1-permissions**: regenerate the access token after enabling `Read and write`.\n- **Reply restrictions**: X restricts many programmatic replies. `tweet quote` is often more reliable than `tweet reply`.\n- **Rate limits**: expect per-endpoint limits and cooldown windows.\n- **Credential drift**: if you rotate tokens in `~\u002F.hermes\u002F.env`, make sure `~\u002F.config\u002Fx-cli\u002F.env` still points at the current file.\n\n## Notes\n\n- Prefer official API workflows over cookie\u002Fsession scraping.\n- Use tweet URLs or IDs interchangeably — `x-cli` accepts both.\n- If bookmark behavior changes upstream, check the upstream README first:\n  https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli\n",{"name":5,"author":47,"license":14,"version":48,"metadata":49,"platforms":55,"description":7,"prerequisites":56},"Siddharth Balyan + YOUSEF SHTIWE","1.0.0",{"hermes":50},{"tags":51,"homepage":54},[31,52,36,53],"x","x-cli","https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli",[39,32],{"commands":57,"env_vars":58},[30],[59,60,61,62,63],"X_API_KEY","X_API_SECRET","X_BEARER_TOKEN","X_ACCESS_TOKEN","X_ACCESS_TOKEN_SECRET","main","93bbc269671fbb340afa15b36a8766f15dc30df2","hermes_sovereign_data\u002Fskills\u002Fsocial-media\u002Fxitter","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch","2026-04-27 02:51:28",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill xitter",{"tool":76,"command":77},"bunx","bunx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill xitter",{"tool":79,"command":80},"pnpm","pnpm dlx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill xitter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsocial-media\u002Fxitter\u002FSKILL.md",true,[],[85,125,153,169,188,209],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":105,"publishedAt":42},"01M71G6TJ2RAQ1J0PV3K6D9GQA","writing-plans","Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[91,94,97,102],{"categoryNo":92,"categoryName":93,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000036","内容创作者",[106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,25,123,124],"writing","writing plans","plans","design","review","workflow","documentation","tasks","development","code","planning","code-review","subagent","superpowers","paths","test-driven-development","you","test-driven","when",{"skillNo":126,"name":121,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":42},"01M71G6R81013R3T7W5VP56GCB","Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[130,133,136,137],{"categoryNo":131,"categoryName":132,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},[139,140,114,141,142,106,143,115,144,118,119,145,146,147,148,149,150,151,152,124],"test","test driven development","driven","testing","debugging","refactor","red-green-refactor","cycle","green","systematic","bugfix","implementing","systematic-debugging","test-first",{"skillNo":154,"name":151,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":42},"01M71G6N0Y546JZEDF25E2PMCE","Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[158],{"categoryNo":134,"categoryName":135,"taxonomyType":20,"taxonomyTypeDesc":21},[160,143,148,106,139,114,118,161,119,162,163,164,108,165,121,166,123,167,168,124],"systematic debugging","use","bug","root-cause","problem-solving","problem","fixes","phase","root cause",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":181,"publishedAt":42},"01M71G6J0DXEGY48GH4KVW2SJH","subagent-driven-development","Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[175,176,177,178],{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":103,"categoryName":104,"taxonomyType":100,"taxonomyTypeDesc":101},{"categoryNo":179,"categoryName":180,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000037","律师与法务",[114,182,118,141,106,110,111,183,113,115,184,117,185,186,119,108,187,121,123,124],"subagent driven development","code quality","delegation","parallel","delegate","fresh",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":196,"publishedAt":42},"01M71G6EFFBQX6634E6XHB09Y1","requesting-code-review","Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[194,195],{"categoryNo":131,"categoryName":132,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},[197,110,115,198,106,199,117,200,201,202,203,118,204,205,206,119,121,207,208,123],"code review","requesting code review","commit","verification","security scan","pipeline","loop","reviewer","fix","auto","static","auto-fix",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":42},"01M71G6CM8ANSWVFXCN9AAD58Y","plan","Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes\u002Fplans\u002F` directory, and do not execute the work.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[211,106,216,111,114,116,217,118,218,219,220,221,222,223,108,224,225,226,25,227],"directory","markdown","workspace","work","write","implementation","do","active","plan mode","inspect","mode","plan-mode"]