[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B03PKE82CBTYV2P0E1CJ6P":3,"skill-same:01M7B03PKE82CBTYV2P0E1CJ6P":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7B03PKE82CBTYV2P0E1CJ6P","github-auth",null,"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.","dbillion\u002Fhermes-skills-public","dbillion","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F49393855?v=4","01M7AVH8QPGCM8WKWS22TRT0T6","Oludayo Adeoye","01M7AVH8RD1JJWA0YS9CFEWAV9",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fgithub\u002Fgithub-auth\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-auth\ndescription: \"GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.\"\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [GitHub, Authentication, Git, gh-cli, SSH, Setup]\n    related_skills: [github-pr-workflow, github-code-review, github-issues, github-repo-management]\n---\n\n# GitHub Authentication Setup\n\nThis skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:\n\n- **`git` (always available)** — uses HTTPS personal access tokens or SSH keys\n- **`gh` CLI (if installed)** — richer GitHub API access with a simpler auth flow\n\n## Detection Flow\n\nWhen a user asks you to work with GitHub, run this check first:\n\n```bash\n# Check what's available\ngit --version\ngh --version 2>\u002Fdev\u002Fnull || echo \"gh not installed\"\n\n# Check if already authenticated\ngh auth status 2>\u002Fdev\u002Fnull || echo \"gh not authenticated\"\ngit config --global credential.helper 2>\u002Fdev\u002Fnull || echo \"no git credential helper\"\n```\n\n**Decision tree:**\n1. If `gh auth status` shows authenticated → you're good, use `gh` for everything\n2. If `gh` is installed but not authenticated → use \"gh auth\" method below\n3. If `gh` is not installed → use \"git-only\" method below (no sudo needed)\n\n---\n\n## Method 1: Git-Only Authentication (No gh, No sudo)\n\nThis works on any machine with `git` installed. No root access needed.\n\n### Option A: HTTPS with Personal Access Token (Recommended)\n\nThis is the most portable method — works everywhere, no SSH config needed.\n\n**Step 1: Create a personal access token**\n\nTell the user to go to: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Ftokens**\n\n- Click \"Generate new token (classic)\"\n- Give it a name like \"hermes-agent\"\n- Select scopes:\n  - `repo` (full repository access — read, write, push, PRs)\n  - `workflow` (trigger and manage GitHub Actions)\n  - `read:org` (if working with organization repos)\n- Set expiration (90 days is a good default)\n- Copy the token — it won't be shown again\n\n**Step 2: Configure git to store the token**\n\n```bash\n# Set up the credential helper to cache credentials\n# \"store\" saves to ~\u002F.git-credentials in plaintext (simple, persistent)\ngit config --global credential.helper store\n\n# Now do a test operation that triggers auth — git will prompt for credentials\n# Username: \u003Ctheir-github-username>\n# Password: \u003Cpaste the personal access token, NOT their GitHub password>\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n```\n\nAfter entering credentials once, they're saved and reused for all future operations.\n\n**Alternative: cache helper (credentials expire from memory)**\n\n```bash\n# Cache in memory for 8 hours (28800 seconds) instead of saving to disk\ngit config --global credential.helper 'cache --timeout=28800'\n```\n\n**Alternative: set the token directly in the remote URL (per-repo)**\n\n```bash\n# Embed token in the remote URL (avoids credential prompts entirely)\ngit remote set-url origin https:\u002F\u002F\u003Cusername>:\u003Ctoken>@github.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n```\n\n**Step 3: Configure git identity**\n\n```bash\n# Required for commits — set name and email\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n**Step 4: Verify**\n\n```bash\n# Test push access (this should work without any prompts now)\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n\n# Verify identity\ngit config --global user.name\ngit config --global user.email\n```\n\n### Option B: SSH Key Authentication\n\nGood for users who prefer SSH or already have keys set up.\n\n**Step 1: Check for existing SSH keys**\n\n```bash\nls -la ~\u002F.ssh\u002Fid_*.pub 2>\u002Fdev\u002Fnull || echo \"No SSH keys found\"\n```\n\n**Step 2: Generate a key if needed**\n\n```bash\n# Generate an ed25519 key (modern, secure, fast)\nssh-keygen -t ed25519 -C \"their-email@example.com\" -f ~\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Display the public key for them to add to GitHub\ncat ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\nTell the user to add the public key at: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Fkeys**\n- Click \"New SSH key\"\n- Paste the public key content\n- Give it a title like \"hermes-agent-\u003Cmachine-name>\"\n\n**Step 3: Test the connection**\n\n```bash\nssh -T git@github.com\n# Expected: \"Hi \u003Cusername>! You've successfully authenticated...\"\n```\n\n**Step 4: Configure git to use SSH for GitHub**\n\n```bash\n# Rewrite HTTPS GitHub URLs to SSH automatically\ngit config --global url.\"git@github.com:\".insteadOf \"https:\u002F\u002Fgithub.com\u002F\"\n```\n\n**Step 5: Configure git identity**\n\n```bash\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n---\n\n## Method 2: gh CLI Authentication\n\nIf `gh` is installed, it handles both API access and git credentials in one step.\n\n### Interactive Browser Login (Desktop)\n\n```bash\ngh auth login\n# Select: GitHub.com\n# Select: HTTPS\n# Authenticate via browser\n```\n\n### Token-Based Login (Headless \u002F SSH Servers)\n\n```bash\necho \"\u003CTHEIR_TOKEN>\" | gh auth login --with-token\n\n# Set up git credentials through gh\ngh auth setup-git\n```\n\n### Verify\n\n```bash\ngh auth status\n```\n\n---\n\n## Using the GitHub API Without gh\n\nWhen `gh` is not available, you can still access the full GitHub API using `curl` with a personal access token. This is how the other GitHub skills implement their fallbacks.\n\n### Setting the Token for API Calls\n\n```bash\n# Option 1: Export as env var (preferred — keeps it out of commands)\nexport GITHUB_TOKEN=\"\u003Ctoken>\"\n\n# Then use in curl calls:\ncurl -s -H \"Authorization: token $GITHUB_TOKEN\" \\\n  https:\u002F\u002Fapi.github.com\u002Fuser\n```\n\n### Extracting the Token from Git Credentials\n\nIf git credentials are already configured (via credential.helper store), the token can be extracted:\n\n```bash\n# Read from git credential store\nuv run python3 \"${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgit-credential-token.py\"\n```\n\n### Helper: Detect Auth Method\n\nUse this pattern at the start of any GitHub workflow:\n\n```bash\n# Try gh first, fall back to git + curl\nif command -v gh &>\u002Fdev\u002Fnull && gh auth status &>\u002Fdev\u002Fnull; then\n  echo \"AUTH_METHOD=gh\"\nelif [ -n \"$GITHUB_TOKEN\" ]; then\n  echo \"AUTH_METHOD=curl\"\nelif _hermes_env=\"${HERMES_HOME:-$HOME\u002F.hermes}\u002F.env\"; [ -f \"$_hermes_env\" ] && grep -q \"^GITHUB_TOKEN=\" \"$_hermes_env\"; then\n  export GITHUB_TOKEN=$(grep \"^GITHUB_TOKEN=\" \"$_hermes_env\" | head -1 | cut -d= -f2 | tr -d '\\n\\r')\n  echo \"AUTH_METHOD=curl\"\nelif grep -q \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull; then\n  export GITHUB_TOKEN=$(uv run python3 \"${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgit-credential-token.py\")\n  echo \"AUTH_METHOD=curl\"\nelse\n  echo \"AUTH_METHOD=none\"\n  echo \"Need to set up authentication first\"\nfi\n```\n\n---\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `git push` asks for password | GitHub disabled password auth. Use a personal access token as the password, or switch to SSH |\n| `remote: Permission to X denied` | Token may lack `repo` scope — regenerate with correct scopes |\n| `fatal: Authentication failed` | Cached credentials may be stale — run `git credential reject` then re-authenticate |\n| `ssh: connect to host github.com port 22: Connection refused` | Try SSH over HTTPS port: add `Host github.com` with `Port 443` and `Hostname ssh.github.com` to `~\u002F.ssh\u002Fconfig` |\n| Credentials not persisting | Check `git config --global credential.helper` — must be `store` or `cache` |\n| Multiple GitHub accounts | Use SSH with different keys per host alias in `~\u002F.ssh\u002Fconfig`, or per-repo credential URLs |\n| `gh: command not found` + no sudo | Use git-only Method 1 above — no installation needed |\n","# GitHub Authentication Setup\n\nThis skill sets up authentication so the agent can work with GitHub repositories, PRs, issues, and CI. It covers two paths:\n\n- **`git` (always available)** — uses HTTPS personal access tokens or SSH keys\n- **`gh` CLI (if installed)** — richer GitHub API access with a simpler auth flow\n\n## Detection Flow\n\nWhen a user asks you to work with GitHub, run this check first:\n\n```bash\n# Check what's available\ngit --version\ngh --version 2>\u002Fdev\u002Fnull || echo \"gh not installed\"\n\n# Check if already authenticated\ngh auth status 2>\u002Fdev\u002Fnull || echo \"gh not authenticated\"\ngit config --global credential.helper 2>\u002Fdev\u002Fnull || echo \"no git credential helper\"\n```\n\n**Decision tree:**\n1. If `gh auth status` shows authenticated → you're good, use `gh` for everything\n2. If `gh` is installed but not authenticated → use \"gh auth\" method below\n3. If `gh` is not installed → use \"git-only\" method below (no sudo needed)\n\n---\n\n## Method 1: Git-Only Authentication (No gh, No sudo)\n\nThis works on any machine with `git` installed. No root access needed.\n\n### Option A: HTTPS with Personal Access Token (Recommended)\n\nThis is the most portable method — works everywhere, no SSH config needed.\n\n**Step 1: Create a personal access token**\n\nTell the user to go to: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Ftokens**\n\n- Click \"Generate new token (classic)\"\n- Give it a name like \"hermes-agent\"\n- Select scopes:\n  - `repo` (full repository access — read, write, push, PRs)\n  - `workflow` (trigger and manage GitHub Actions)\n  - `read:org` (if working with organization repos)\n- Set expiration (90 days is a good default)\n- Copy the token — it won't be shown again\n\n**Step 2: Configure git to store the token**\n\n```bash\n# Set up the credential helper to cache credentials\n# \"store\" saves to ~\u002F.git-credentials in plaintext (simple, persistent)\ngit config --global credential.helper store\n\n# Now do a test operation that triggers auth — git will prompt for credentials\n# Username: \u003Ctheir-github-username>\n# Password: \u003Cpaste the personal access token, NOT their GitHub password>\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n```\n\nAfter entering credentials once, they're saved and reused for all future operations.\n\n**Alternative: cache helper (credentials expire from memory)**\n\n```bash\n# Cache in memory for 8 hours (28800 seconds) instead of saving to disk\ngit config --global credential.helper 'cache --timeout=28800'\n```\n\n**Alternative: set the token directly in the remote URL (per-repo)**\n\n```bash\n# Embed token in the remote URL (avoids credential prompts entirely)\ngit remote set-url origin https:\u002F\u002F\u003Cusername>:\u003Ctoken>@github.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n```\n\n**Step 3: Configure git identity**\n\n```bash\n# Required for commits — set name and email\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n**Step 4: Verify**\n\n```bash\n# Test push access (this should work without any prompts now)\ngit ls-remote https:\u002F\u002Fgithub.com\u002F\u003Ctheir-username>\u002F\u003Cany-repo>.git\n\n# Verify identity\ngit config --global user.name\ngit config --global user.email\n```\n\n### Option B: SSH Key Authentication\n\nGood for users who prefer SSH or already have keys set up.\n\n**Step 1: Check for existing SSH keys**\n\n```bash\nls -la ~\u002F.ssh\u002Fid_*.pub 2>\u002Fdev\u002Fnull || echo \"No SSH keys found\"\n```\n\n**Step 2: Generate a key if needed**\n\n```bash\n# Generate an ed25519 key (modern, secure, fast)\nssh-keygen -t ed25519 -C \"their-email@example.com\" -f ~\u002F.ssh\u002Fid_ed25519 -N \"\"\n\n# Display the public key for them to add to GitHub\ncat ~\u002F.ssh\u002Fid_ed25519.pub\n```\n\nTell the user to add the public key at: **https:\u002F\u002Fgithub.com\u002Fsettings\u002Fkeys**\n- Click \"New SSH key\"\n- Paste the public key content\n- Give it a title like \"hermes-agent-\u003Cmachine-name>\"\n\n**Step 3: Test the connection**\n\n```bash\nssh -T git@github.com\n# Expected: \"Hi \u003Cusername>! You've successfully authenticated...\"\n```\n\n**Step 4: Configure git to use SSH for GitHub**\n\n```bash\n# Rewrite HTTPS GitHub URLs to SSH automatically\ngit config --global url.\"git@github.com:\".insteadOf \"https:\u002F\u002Fgithub.com\u002F\"\n```\n\n**Step 5: Configure git identity**\n\n```bash\ngit config --global user.name \"Their Name\"\ngit config --global user.email \"their-email@example.com\"\n```\n\n---\n\n## Method 2: gh CLI Authentication\n\nIf `gh` is installed, it handles both API access and git credentials in one step.\n\n### Interactive Browser Login (Desktop)\n\n```bash\ngh auth login\n# Select: GitHub.com\n# Select: HTTPS\n# Authenticate via browser\n```\n\n### Token-Based Login (Headless \u002F SSH Servers)\n\n```bash\necho \"\u003CTHEIR_TOKEN>\" | gh auth login --with-token\n\n# Set up git credentials through gh\ngh auth setup-git\n```\n\n### Verify\n\n```bash\ngh auth status\n```\n\n---\n\n## Using the GitHub API Without gh\n\nWhen `gh` is not available, you can still access the full GitHub API using `curl` with a personal access token. This is how the other GitHub skills implement their fallbacks.\n\n### Setting the Token for API Calls\n\n```bash\n# Option 1: Export as env var (preferred — keeps it out of commands)\nexport GITHUB_TOKEN=\"\u003Ctoken>\"\n\n# Then use in curl calls:\ncurl -s -H \"Authorization: token $GITHUB_TOKEN\" \\\n  https:\u002F\u002Fapi.github.com\u002Fuser\n```\n\n### Extracting the Token from Git Credentials\n\nIf git credentials are already configured (via credential.helper store), the token can be extracted:\n\n```bash\n# Read from git credential store\nuv run python3 \"${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgit-credential-token.py\"\n```\n\n### Helper: Detect Auth Method\n\nUse this pattern at the start of any GitHub workflow:\n\n```bash\n# Try gh first, fall back to git + curl\nif command -v gh &>\u002Fdev\u002Fnull && gh auth status &>\u002Fdev\u002Fnull; then\n  echo \"AUTH_METHOD=gh\"\nelif [ -n \"$GITHUB_TOKEN\" ]; then\n  echo \"AUTH_METHOD=curl\"\nelif _hermes_env=\"${HERMES_HOME:-$HOME\u002F.hermes}\u002F.env\"; [ -f \"$_hermes_env\" ] && grep -q \"^GITHUB_TOKEN=\" \"$_hermes_env\"; then\n  export GITHUB_TOKEN=$(grep \"^GITHUB_TOKEN=\" \"$_hermes_env\" | head -1 | cut -d= -f2 | tr -d '\\n\\r')\n  echo \"AUTH_METHOD=curl\"\nelif grep -q \"github.com\" ~\u002F.git-credentials 2>\u002Fdev\u002Fnull; then\n  export GITHUB_TOKEN=$(uv run python3 \"${HERMES_HOME:-$HOME\u002F.hermes}\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgit-credential-token.py\")\n  echo \"AUTH_METHOD=curl\"\nelse\n  echo \"AUTH_METHOD=none\"\n  echo \"Need to set up authentication first\"\nfi\n```\n\n---\n\n## Troubleshooting\n\n| Problem | Solution |\n|---------|----------|\n| `git push` asks for password | GitHub disabled password auth. Use a personal access token as the password, or switch to SSH |\n| `remote: Permission to X denied` | Token may lack `repo` scope — regenerate with correct scopes |\n| `fatal: Authentication failed` | Cached credentials may be stale — run `git credential reject` then re-authenticate |\n| `ssh: connect to host github.com port 22: Connection refused` | Try SSH over HTTPS port: add `Host github.com` with `Port 443` and `Hostname ssh.github.com` to `~\u002F.ssh\u002Fconfig` |\n| Credentials not persisting | Check `git config --global credential.helper` — must be `store` or `cache` |\n| Multiple GitHub accounts | Use SSH with different keys per host alias in `~\u002F.ssh\u002Fconfig`, or per-repo credential URLs |\n| `gh: command not found` + no sudo | Use git-only Method 1 above — no installation needed |\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":40,"description":7},"Hermes Agent","1.1.0",{"hermes":27},{"tags":28,"related_skills":35},[29,30,31,32,33,34],"GitHub","Authentication","Git","gh-cli","SSH","Setup",[36,37,38,39],"github-pr-workflow","github-code-review","github-issues","github-repo-management",[41,42,43],"linux","macos","windows","master","f341c46fed021656175d5c9ccc67a72126e50bfb","skills\u002Fgithub\u002Fgithub-auth","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public","https:\u002F\u002Fgithub.com\u002Fdbillion","I enjoy writing codes,teaching programming, solving problems, tasted automation in Python and never looked back😋😋😋💞","2026-10-14 03:31:55",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add dbillion\u002Fhermes-skills-public --skill github-auth",{"tool":57,"command":58},"bunx","bunx skills add dbillion\u002Fhermes-skills-public --skill github-auth",{"tool":60,"command":61},"pnpm","pnpm dlx skills add dbillion\u002Fhermes-skills-public --skill github-auth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fgithub\u002Fgithub-auth\u002FSKILL.md",true,[65,71],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fgh-env.sh","SCRIPT","脚本",2556,"https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgh-env.sh",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Fgit-credential-token.py",1788,"https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fgithub\u002Fgithub-auth\u002Fscripts\u002Fgit-credential-token.py",[76,83,90,99,106,113],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7B25T0V7RBKES86Y3RTXQRN","blocked-page-recovery","Use when a fetch fails: 403\u002F429, paywall, WAF, bot wall.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fweb\u002Fblocked-page-recovery\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7B25DSBBMZRHVD28MAX7N5X","gemini-vision-fallback","Vision fallback: Gemini REST API if vision_analyze blocked.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fvision\u002Fgemini-vision-fallback\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B22XW9QXT2ZWWXVZDFWYZP","twitter-cli","Use twitter-cli for ALL Twitter\u002FX operations — reading tweets, posting, replying, quoting, liking, retweeting, following, searching, user lookups. Invoke whenever user requests any Twitter interaction.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Ftwitter-cli\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Ftwitter-cli\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7B22QMWY1B4F7BC114RG4S6","prism-scan","Structural analysis through dynamically generated cognitive lenses. Generates the optimal analytical lens for the specific code\u002Fartifact, then executes it. Finds conservation laws, structural invariants, and concrete bugs that vanilla analysis misses. Use on any code file, system design, or text artifact.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-scan\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7B22JA5XCAP1ACT6V50WYR1","prism-reflect","Constraint transparency: analyzes an artifact structurally, then analyzes what its own analysis concealed. Produces a conservation law AND a constraint report showing what was maximized, what was sacrificed, and what to investigate next. The only AI skill that knows what it can't see.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-reflect\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7B22EB15M75M4X3C52YGDCC","prism-full","Full Prism: multi-pass structural analysis with mandatory adversarial self-correction. Designs custom analytical passes, executes them with chaining, then attacks its own findings before synthesizing. Use for maximum depth on important code or artifacts.","https:\u002F\u002Fgithub.com\u002Fdbillion\u002Fhermes-skills-public\u002Fblob\u002Fmaster\u002Fskills\u002Fts-superhermes-prism-full\u002FSKILL.md",[],[]]