[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AV7BR4EV3CJ5DCVRH8GE5P":3,"skill-same:01M7AV7BR4EV3CJ5DCVRH8GE5P":50},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7AV7BR4EV3CJ5DCVRH8GE5P","github-restricted-network-access",null,"Use when github.com clone times out or install fails.","peterlau123\u002Fskills-you-need","peterlau123","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19188200?v=4","01M7AV0Y55C30Y4E2TGRQ8X7WR","Sloth","01M7AV0Y5SNAJQ4E3FG1EEK8S4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fgithub\u002Fgithub-restricted-network-access\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: github-restricted-network-access\ndescription: Use when github.com clone times out or install fails.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos]\n---\n\n# GitHub Access Behind a Restricted Network\n\nSome networks (e.g. this machine, hostname mx001) block `github.com:443` outright but leave other GitHub services reachable. Direct `git clone` hangs until timeout; `hermes skills install` fails with \"Could not fetch from any source\" when its resolution path hits the GitHub API. This skill is the verified fallback ladder — do NOT retry the direct clone more than once.\n\n## Step 0 — Probe before assuming\n\n```bash\n# Which GitHub surfaces are reachable? (000 = unreachable\u002Ftimeout)\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"github.com: %{http_code}\\n\" https:\u002F\u002Fgithub.com\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"api.github.com: %{http_code}\\n\" https:\u002F\u002Fapi.github.com\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"codeload: %{http_code}\\n\" https:\u002F\u002Fcodeload.github.com\n# Probe a candidate proxy against the actual git endpoint:\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"%{http_code}\\n\" \"https:\u002F\u002F\u003Cproxy>\u002Fhttps:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git\u002Finfo\u002Frefs?service=git-upload-pack\"\n```\n\nVerified on this network: `api.github.com`, `raw.githubusercontent.com`, `codeload.github.com` reachable; `github.com` itself and `clawhub.org` NOT reachable.\n\n## Step 1 — Clone: prefer direct SSH when the pubkey is already registered\n\nIf `~\u002F.ssh\u002Fconfig` routes `github.com` → `ssh.github.com:443` AND the pubkey is registered (verified 2026-08-04 on mx001: `ssh -T git@ssh.github.com` → \"Hi peterlau123!\"), **just clone with the standard SSH URL first** — it worked when the proxy hung (see pitfall below):\n\n```bash\ngit clone git@github.com:\u003Cowner>\u002F\u003Crepo>.git\n```\n\n## Step 1b — Clone via a proxy prefix (fallback: no SSH key \u002F other machines)\n\n```bash\ngit clone https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n# verified 200 on this network; alternative: https:\u002F\u002Fghproxy.net\u002Fhttps:\u002F\u002Fgithub.com\u002F...\n```\n\nProbe any other mirror (ghfast.top, gitclone.com, hub.gitmirror.com) before use — availability changes. Keep the proxy prefix in `origin` (future `git pull` just works).\n\n## Push — the proxies are READ-ONLY; use SSH over 443\n\n`gh-proxy.com` \u002F `ghproxy.net` prefix URLs clone fine but **cannot push**. Verified on mx001: `git push` through the proxy dies with `fatal: could not read Username for 'https:\u002F\u002Fgh-proxy.com'` (no auth pass-through; the proxy answers 403 to write paths). Also `github.com:22` and `github.com:443` both time out — the ONLY reachable push route is SSH over HTTPS:\n\n```bash\n# Probe (connectivity check):\nssh -p 443 -T git@ssh.github.com\n# \"Permission denied (publickey)\" = connection OK, key not registered on the account\n```\n\nFix path (requires one user action): register the machine's pubkey on GitHub (Settings → SSH and GPG keys), then push over port 443:\n\n**STATUS ON mx001: RESOLVED — verified 2026-08-04.** The pubkey IS registered; `ssh -T git@ssh.github.com` returns \"Hi peterlau123! You've successfully authenticated\" and `git push` works (pushed `feat\u002Fpaper-notes` to ai-infra-wiki). Working config already in place on this machine:\n\n```\n# ~\u002F.ssh\u002Fconfig  (already applied on mx001)\nHost github.com\n    HostName ssh.github.com\n    Port 443\n    User git\n    IdentityFile ~\u002F.ssh\u002Fid_ed25519\n```\n```bash\ngit remote set-url origin git@github.com:\u003Cowner>\u002F\u003Crepo>.git   # standard URL — routing handled by ssh config\ngit push -u origin \u003Cbranch>\n```\n\nOn other machines\u002Faccounts: register the pubkey first, then push over 443 as above.\n\nNo `GITHUB_TOKEN` in `~\u002F.hermes\u002F.env` on this machine — SSH is the push path, not the API key.\n\n## Step 2 — Tarball fallback (no git history needed)\n\n```bash\ncurl -sL -o repo.tar.gz \"https:\u002F\u002Fcodeload.github.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Ftar.gz\u002Frefs\u002Fheads\u002F\u003Cbranch>\"\ntar xzf repo.tar.gz\n# If a real git repo is required: git init && git remote add origin \u003Curl> && git add\u002Fcommit\n```\n\n## Step 2b — Inspect repo \u002F fetch single files via API + raw (no clone)\n\nWhen you only need to READ files (verify a claim, check an implementation, list a repo's structure), skip clone AND tarball — list via the contents API, then pull the exact files raw. Both routes work through gh-proxy on mx001 (verified 2026-08-05):\n\n```bash\n# 1. List a directory (JSON: type\u002Fname\u002Fsize per entry)\ncurl -sL --max-time 60 \"https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fapi.github.com\u002Frepos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcontents\u002F\u003Cdir>?ref=main\"\n# 2. Fetch one file directly\ncurl -sL --max-time 90 \"https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fmain\u002F\u003Cpath>\" -o \u003Clocal>\n```\n\nWorked example: inspected `disler\u002Fpi-vs-claude-code` extension sources (`extensions\u002Fcoms.ts`, `coms-net.ts`, ~50KB each) this way after both a proxied clone and a tarball fetch failed. Also the right path for locating files before manual installs.\n\n## Step 3 — `hermes skills install` fallback (manual install)\n\nWhen install fails (rate limit, unreachable registry), pull the repo tarball via codeload and copy skill directories straight into the profile:\n\n```bash\nHERMES_HOME=$(hermes config path)          # e.g. ~\u002F.hermes\u002Fprofiles\u002F\u003Cprofile>\nmkdir -p \"$HERMES_HOME\u002Fskills\u002F\u003Ccategory>\"\ncp -r \u003Crepo>\u002Fskills\u002F\u003Cskill-dir> \"$HERMES_HOME\u002Fskills\u002F\u003Ccategory>\u002F\"   # copy WHOLE dirs — SKILL.md alone misses supporting files (agents\u002F, tests.md, scripts\u002F)\nhermes skills list   # verify: shows as source 'local', status enabled\n```\n\nResult is a normal enabled skill but tracked as `local` — `hermes skills update` won't manage it; re-run the tarball copy to refresh. Supporting files matter: e.g. mattpocock `tdd` carries `agents\u002Fopenai.yaml`, `tests.md`, `mocking.md`.\n\n## GitHub API rate limits\n\nUnauthenticated: 60 req\u002Fhr per IP (shared IPs exhaust fast — it bit this session mid-work). Fix: set `GITHUB_TOKEN` in `~\u002F.hermes\u002F.env` or `gh auth login` (5,000\u002Fhr). `raw.githubusercontent.com` and `codeload.github.com` are NOT rate-limited — prefer them for single-file \u002F tarball fetches.\n\n## Pitfalls\n\n- **`~\u002F.git-credentials` may hold an internal GitLab entry, not a usable proxy**: on mx001 the only stored credential is `http:\u002F\u002Fliux:***@10.20.30.25:8080`, and 10.20.30.25:8080 is a GitLab web app (`\u002Fusers\u002Fsign_in` redirect), NOT an HTTP CONNECT proxy — `curl -x http:\u002F\u002Fliux@10.20.30.25:8080 https:\u002F\u002Fapi.github.com` fails with `000` and git push through it dies with `HTTP 400 from proxy after CONNECT`. Don't burn probes treating it as a general egress proxy.\n- **Re-probe before believing \"direct access works\"**: a user may insist github.com is reachable because it IS, from their laptop or another environment (e.g. the H20 box). Step 0 costs seconds — run it and show the evidence (`github.com -> HTTP 000`, `codeload -> 301`, `proxy -> 200`) rather than silently switching strategies on hearsay. `HTTP 000` is curl's \"no response at all\" (connect failure\u002Ftimeout), distinct from any real HTTP status — it means the block is still in effect.\n- **Pipe masks exit codes**: `timeout 60 git clone ... | tail -3` reports tail's exit, not git's. Always verify the target directory contents afterwards.\n- **gh-proxy `git clone` can silently return an EMPTY repo**: clone exits 0 but `git log` says \"your current branch 'master' does not have any commits yet\" and the worktree has no files. Always check `ls`\u002F`git log` after a proxied clone; if empty, fall to Step 2 (codeload) or Step 2b (API+raw) instead of retrying the clone.\n- **gh-proxy HTTPS `git clone` can HANG outright** (observed 2026-08-06: `git clone https:\u002F\u002Fgh-proxy.com\u002F...peterlau123.github.io.git` timed out at 120s, exit 124), even for repos that cloned fine before — availability varies by repo\u002Fsize\u002Ftransient state. Don't retry the proxy twice; after ONE hang, fall to direct SSH clone (Step 1) which completed in seconds on the same network.\n- **gh-proxy routes to `codeload.github.com` and `\u002Farchive\u002Frefs\u002Fheads\u002F*.tar.gz` HANG** (observed twice, `curl` exit 28 timeout). The tarball route on this network is DIRECT codeload (Step 2); the proxied routes are for api\u002Fraw only. Don't burn 2-3 minutes per attempt on proxied tarballs.\n- **Never `rm -rf` the shell's cwd**: git then dies with \"Unable to read current working directory\". `cd` somewhere valid first.\n- **`hermes skills install` with a bare ambiguous name** (\"Multiple skills found\") — use the FULL identifier from `hermes skills search \u003Cname> --json` (e.g. `skills-sh\u002F\u003Cowner>\u002F\u003Crepo>\u002F\u003Cskill>`); a clawhub identifier equal to the bare name is an install trap.\n- **Verify ambiguous clone destinations**: before cloning to a path the user named, inspect the target and parent workspace for convention (e.g. this machine keeps repos at `\u002Fdata\u002Flx\u002F\u003Cproject>\u002F` — a folder named like the Hermes profile turned out to be an Obsidian wiki home, not the agent). Check first; a wrong 500MB clone is wasted work.\n- hermes-agent source on this machine lives at `~\u002F.hermes\u002Fhermes-agent\u002F`, cloned from a China mirror: `https:\u002F\u002Fcnb.cool\u002Fhermesagent-cn\u002Fhermes-agent-cn-mirror.git` (use it when github.com is unreachable).\n","# GitHub Access Behind a Restricted Network\n\nSome networks (e.g. this machine, hostname mx001) block `github.com:443` outright but leave other GitHub services reachable. Direct `git clone` hangs until timeout; `hermes skills install` fails with \"Could not fetch from any source\" when its resolution path hits the GitHub API. This skill is the verified fallback ladder — do NOT retry the direct clone more than once.\n\n## Step 0 — Probe before assuming\n\n```bash\n# Which GitHub surfaces are reachable? (000 = unreachable\u002Ftimeout)\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"github.com: %{http_code}\\n\" https:\u002F\u002Fgithub.com\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"api.github.com: %{http_code}\\n\" https:\u002F\u002Fapi.github.com\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"codeload: %{http_code}\\n\" https:\u002F\u002Fcodeload.github.com\n# Probe a candidate proxy against the actual git endpoint:\ncurl -s --max-time 8 -o \u002Fdev\u002Fnull -w \"%{http_code}\\n\" \"https:\u002F\u002F\u003Cproxy>\u002Fhttps:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git\u002Finfo\u002Frefs?service=git-upload-pack\"\n```\n\nVerified on this network: `api.github.com`, `raw.githubusercontent.com`, `codeload.github.com` reachable; `github.com` itself and `clawhub.org` NOT reachable.\n\n## Step 1 — Clone: prefer direct SSH when the pubkey is already registered\n\nIf `~\u002F.ssh\u002Fconfig` routes `github.com` → `ssh.github.com:443` AND the pubkey is registered (verified 2026-08-04 on mx001: `ssh -T git@ssh.github.com` → \"Hi peterlau123!\"), **just clone with the standard SSH URL first** — it worked when the proxy hung (see pitfall below):\n\n```bash\ngit clone git@github.com:\u003Cowner>\u002F\u003Crepo>.git\n```\n\n## Step 1b — Clone via a proxy prefix (fallback: no SSH key \u002F other machines)\n\n```bash\ngit clone https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fgithub.com\u002F\u003Cowner>\u002F\u003Crepo>.git\n# verified 200 on this network; alternative: https:\u002F\u002Fghproxy.net\u002Fhttps:\u002F\u002Fgithub.com\u002F...\n```\n\nProbe any other mirror (ghfast.top, gitclone.com, hub.gitmirror.com) before use — availability changes. Keep the proxy prefix in `origin` (future `git pull` just works).\n\n## Push — the proxies are READ-ONLY; use SSH over 443\n\n`gh-proxy.com` \u002F `ghproxy.net` prefix URLs clone fine but **cannot push**. Verified on mx001: `git push` through the proxy dies with `fatal: could not read Username for 'https:\u002F\u002Fgh-proxy.com'` (no auth pass-through; the proxy answers 403 to write paths). Also `github.com:22` and `github.com:443` both time out — the ONLY reachable push route is SSH over HTTPS:\n\n```bash\n# Probe (connectivity check):\nssh -p 443 -T git@ssh.github.com\n# \"Permission denied (publickey)\" = connection OK, key not registered on the account\n```\n\nFix path (requires one user action): register the machine's pubkey on GitHub (Settings → SSH and GPG keys), then push over port 443:\n\n**STATUS ON mx001: RESOLVED — verified 2026-08-04.** The pubkey IS registered; `ssh -T git@ssh.github.com` returns \"Hi peterlau123! You've successfully authenticated\" and `git push` works (pushed `feat\u002Fpaper-notes` to ai-infra-wiki). Working config already in place on this machine:\n\n```\n# ~\u002F.ssh\u002Fconfig  (already applied on mx001)\nHost github.com\n    HostName ssh.github.com\n    Port 443\n    User git\n    IdentityFile ~\u002F.ssh\u002Fid_ed25519\n```\n```bash\ngit remote set-url origin git@github.com:\u003Cowner>\u002F\u003Crepo>.git   # standard URL — routing handled by ssh config\ngit push -u origin \u003Cbranch>\n```\n\nOn other machines\u002Faccounts: register the pubkey first, then push over 443 as above.\n\nNo `GITHUB_TOKEN` in `~\u002F.hermes\u002F.env` on this machine — SSH is the push path, not the API key.\n\n## Step 2 — Tarball fallback (no git history needed)\n\n```bash\ncurl -sL -o repo.tar.gz \"https:\u002F\u002Fcodeload.github.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Ftar.gz\u002Frefs\u002Fheads\u002F\u003Cbranch>\"\ntar xzf repo.tar.gz\n# If a real git repo is required: git init && git remote add origin \u003Curl> && git add\u002Fcommit\n```\n\n## Step 2b — Inspect repo \u002F fetch single files via API + raw (no clone)\n\nWhen you only need to READ files (verify a claim, check an implementation, list a repo's structure), skip clone AND tarball — list via the contents API, then pull the exact files raw. Both routes work through gh-proxy on mx001 (verified 2026-08-05):\n\n```bash\n# 1. List a directory (JSON: type\u002Fname\u002Fsize per entry)\ncurl -sL --max-time 60 \"https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fapi.github.com\u002Frepos\u002F\u003Cowner>\u002F\u003Crepo>\u002Fcontents\u002F\u003Cdir>?ref=main\"\n# 2. Fetch one file directly\ncurl -sL --max-time 90 \"https:\u002F\u002Fgh-proxy.com\u002Fhttps:\u002F\u002Fraw.githubusercontent.com\u002F\u003Cowner>\u002F\u003Crepo>\u002Fmain\u002F\u003Cpath>\" -o \u003Clocal>\n```\n\nWorked example: inspected `disler\u002Fpi-vs-claude-code` extension sources (`extensions\u002Fcoms.ts`, `coms-net.ts`, ~50KB each) this way after both a proxied clone and a tarball fetch failed. Also the right path for locating files before manual installs.\n\n## Step 3 — `hermes skills install` fallback (manual install)\n\nWhen install fails (rate limit, unreachable registry), pull the repo tarball via codeload and copy skill directories straight into the profile:\n\n```bash\nHERMES_HOME=$(hermes config path)          # e.g. ~\u002F.hermes\u002Fprofiles\u002F\u003Cprofile>\nmkdir -p \"$HERMES_HOME\u002Fskills\u002F\u003Ccategory>\"\ncp -r \u003Crepo>\u002Fskills\u002F\u003Cskill-dir> \"$HERMES_HOME\u002Fskills\u002F\u003Ccategory>\u002F\"   # copy WHOLE dirs — SKILL.md alone misses supporting files (agents\u002F, tests.md, scripts\u002F)\nhermes skills list   # verify: shows as source 'local', status enabled\n```\n\nResult is a normal enabled skill but tracked as `local` — `hermes skills update` won't manage it; re-run the tarball copy to refresh. Supporting files matter: e.g. mattpocock `tdd` carries `agents\u002Fopenai.yaml`, `tests.md`, `mocking.md`.\n\n## GitHub API rate limits\n\nUnauthenticated: 60 req\u002Fhr per IP (shared IPs exhaust fast — it bit this session mid-work). Fix: set `GITHUB_TOKEN` in `~\u002F.hermes\u002F.env` or `gh auth login` (5,000\u002Fhr). `raw.githubusercontent.com` and `codeload.github.com` are NOT rate-limited — prefer them for single-file \u002F tarball fetches.\n\n## Pitfalls\n\n- **`~\u002F.git-credentials` may hold an internal GitLab entry, not a usable proxy**: on mx001 the only stored credential is `http:\u002F\u002Fliux:***@10.20.30.25:8080`, and 10.20.30.25:8080 is a GitLab web app (`\u002Fusers\u002Fsign_in` redirect), NOT an HTTP CONNECT proxy — `curl -x http:\u002F\u002Fliux@10.20.30.25:8080 https:\u002F\u002Fapi.github.com` fails with `000` and git push through it dies with `HTTP 400 from proxy after CONNECT`. Don't burn probes treating it as a general egress proxy.\n- **Re-probe before believing \"direct access works\"**: a user may insist github.com is reachable because it IS, from their laptop or another environment (e.g. the H20 box). Step 0 costs seconds — run it and show the evidence (`github.com -> HTTP 000`, `codeload -> 301`, `proxy -> 200`) rather than silently switching strategies on hearsay. `HTTP 000` is curl's \"no response at all\" (connect failure\u002Ftimeout), distinct from any real HTTP status — it means the block is still in effect.\n- **Pipe masks exit codes**: `timeout 60 git clone ... | tail -3` reports tail's exit, not git's. Always verify the target directory contents afterwards.\n- **gh-proxy `git clone` can silently return an EMPTY repo**: clone exits 0 but `git log` says \"your current branch 'master' does not have any commits yet\" and the worktree has no files. Always check `ls`\u002F`git log` after a proxied clone; if empty, fall to Step 2 (codeload) or Step 2b (API+raw) instead of retrying the clone.\n- **gh-proxy HTTPS `git clone` can HANG outright** (observed 2026-08-06: `git clone https:\u002F\u002Fgh-proxy.com\u002F...peterlau123.github.io.git` timed out at 120s, exit 124), even for repos that cloned fine before — availability varies by repo\u002Fsize\u002Ftransient state. Don't retry the proxy twice; after ONE hang, fall to direct SSH clone (Step 1) which completed in seconds on the same network.\n- **gh-proxy routes to `codeload.github.com` and `\u002Farchive\u002Frefs\u002Fheads\u002F*.tar.gz` HANG** (observed twice, `curl` exit 28 timeout). The tarball route on this network is DIRECT codeload (Step 2); the proxied routes are for api\u002Fraw only. Don't burn 2-3 minutes per attempt on proxied tarballs.\n- **Never `rm -rf` the shell's cwd**: git then dies with \"Unable to read current working directory\". `cd` somewhere valid first.\n- **`hermes skills install` with a bare ambiguous name** (\"Multiple skills found\") — use the FULL identifier from `hermes skills search \u003Cname> --json` (e.g. `skills-sh\u002F\u003Cowner>\u002F\u003Crepo>\u002F\u003Cskill>`); a clawhub identifier equal to the bare name is an install trap.\n- **Verify ambiguous clone destinations**: before cloning to a path the user named, inspect the target and parent workspace for convention (e.g. this machine keeps repos at `\u002Fdata\u002Flx\u002F\u003Cproject>\u002F` — a folder named like the Hermes profile turned out to be an Obsidian wiki home, not the agent). Check first; a wrong 500MB clone is wasted work.\n- hermes-agent source on this machine lives at `~\u002F.hermes\u002Fhermes-agent\u002F`, cloned from a China mirror: `https:\u002F\u002Fcnb.cool\u002Fhermesagent-cn\u002Fhermes-agent-cn-mirror.git` (use it when github.com is unreachable).\n",{"name":5,"author":24,"license":15,"version":25,"platforms":26,"description":7},"Hermes Agent","1.1.0",[27,28],"linux","macos","main","c0b220603dea88e986e5b31268098ef2f5b07fd0","github\u002Fgithub-restricted-network-access","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need","https:\u002F\u002Fgithub.com\u002Fpeterlau123","A software engineer in deep learning\r\n","2026-08-19 16:46:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add peterlau123\u002Fskills-you-need --skill github-restricted-network-access",{"tool":42,"command":43},"bunx","bunx skills add peterlau123\u002Fskills-you-need --skill github-restricted-network-access",{"tool":45,"command":46},"pnpm","pnpm dlx skills add peterlau123\u002Fskills-you-need --skill github-restricted-network-access","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fgithub\u002Fgithub-restricted-network-access\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7AVH2D16QBRC8T2P6SVXSTS","jekyll-chirpy-blog","Use when editing the Jekyll\u002FChirpy blog or fixing mermaid.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fweb\u002Fjekyll-chirpy-blog\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7AVGYYFDK4GKCSNHBCP59Y6","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7AVGT9GAVB5EBKZ2616R27Z","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7AVGQ23T5EHRQP5GZ45KZC5","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7AVGKZ0ZD91ATKD9QB44E1B","simplify-code","Parallel 4-agent cleanup of recent code changes.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Fsimplify-code\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7AVGFBR76BWQNG2X4CN5SQT","requesting-code-review","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Fpeterlau123\u002Fskills-you-need\u002Fblob\u002Fmain\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[],[]]