[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NT73VVBK4D04RSJKRQCZ10":3,"skill-same:01M6NT73VVBK4D04RSJKRQCZ10":87},{"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":25,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":13,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M6NT73VVBK4D04RSJKRQCZ10","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.","qubit-calculus\u002FQubit","qubit-calculus","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271071935?v=4","01M6NS19569VZ1F2Z0SACBWPS7","01M6NS1992MKFQVNP9AGRTSZXN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsocial-media\u002Fxitter\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"access","for","reading","posting","token","social","uv","use","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 + Hermes Agent\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:NousResearch\" --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:NousResearch\" --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":50,"license":14,"version":51,"metadata":52,"platforms":58,"description":7,"prerequisites":59},"Siddharth Balyan + Hermes Agent","1.0.0",{"hermes":53},{"tags":54,"homepage":57},[34,55,39,56],"x","x-cli","https:\u002F\u002Fgithub.com\u002FInfatoshi\u002Fx-cli",[42,35],{"commands":60,"env_vars":61},[32],[62,63,64,65,66],"X_API_KEY","X_API_SECRET","X_BEARER_TOKEN","X_ACCESS_TOKEN","X_ACCESS_TOKEN_SECRET","main","a05c0ccfff1cda2a5d12e9ee7d02b75350ac0557","packages\u002Fskills\u002Fhermes\u002Fsocial-media\u002Fxitter","https:\u002F\u002Fgithub.com\u002Fqubit-calculus\u002FQubit","https:\u002F\u002Fgithub.com\u002Fqubit-calculus","2026-04-07 15:16:13",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add qubit-calculus\u002FQubit --skill xitter",{"tool":79,"command":80},"bunx","bunx skills add qubit-calculus\u002FQubit --skill xitter",{"tool":82,"command":83},"pnpm","pnpm dlx skills add qubit-calculus\u002FQubit --skill xitter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsocial-media\u002Fxitter\u002FSKILL.md",true,[],[88,127,155,172,193,215],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":108,"publishedAt":45},"01M6NT8MKBM6Q660B4D7SHXE3F","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\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[94,97,100,105],{"categoryNo":95,"categoryName":96,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000036","内容创作者",[109,110,111,112,113,114,115,116,117,118,119,120,121,33,122,123,124,125,126,27],"writing","writing plans","plans","design","review","workflow","documentation","tasks","development","code","planning","code-review","subagent","superpowers","complete","paths","test-driven-development","you",{"skillNo":128,"name":125,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":140,"publishedAt":45},"01M6NT8G9H510DV7VMY4X4Q9F3","Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.","https:\u002F\u002Fgithub.com\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[132,135,138,139],{"categoryNo":133,"categoryName":134,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":136,"categoryName":137,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},[141,142,117,143,144,109,145,118,146,121,122,147,148,149,150,111,151,152,153,154],"test","test driven development","driven","testing","debugging","refactor","red-green-refactor","cycle","green","feature","systematic","bugfix","implementing","systematic-debugging",{"skillNo":156,"name":154,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":45},"01M6NT87T34SVN9P1S3PCBWY2D","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\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[160],{"categoryNo":136,"categoryName":137,"taxonomyType":20,"taxonomyTypeDesc":21},[162,145,151,109,141,117,163,164,121,165,166,33,122,167,168,169,111,170,125,171],"systematic debugging","first","investigation","hermes","behavior","bug","root-cause","problem-solving","problem","fixes",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":185,"publishedAt":45},"01M6NT83GMFJRDY84BWJHQSVQE","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\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[178,179,180,181,182],{"categoryNo":98,"categoryName":99,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":106,"categoryName":107,"taxonomyType":103,"taxonomyTypeDesc":104},{"categoryNo":183,"categoryName":184,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000037","律师与法务",[117,186,121,143,109,113,114,187,116,118,188,120,189,190,33,122,191,111,192,125],"subagent driven development","code quality","delegation","parallel","delegate","stage","fresh",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":201,"publishedAt":45},"01M6NT7YMC7H5NK632ED23WMV6","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\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[199,200],{"categoryNo":133,"categoryName":134,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[202,113,118,203,109,204,205,120,206,207,208,209,121,210,211,212,122,125,213,214],"code review","requesting code review","security","commit","verification","security scan","pipeline","loop","reviewer","fix","auto","static","auto-fix",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":45},"01M6NT7AWK0VW1RFSJTAG92363","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\u002Fqubit-calculus\u002FQubit\u002Fblob\u002Fmain\u002Fpackages\u002Fskills\u002Fhermes\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[217,109,222,114,117,119,223,121,224,225,226,227,228,229,111,230,231,232,27,233],"directory","markdown","workspace","work","write","implementation","do","active","plan mode","inspect","mode","plan-mode"]