[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BR7VA3VEDZSCBPHHGR0ENB":3,"skill-same:01M7BR7VA3VEDZSCBPHHGR0ENB":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7BR7VA3VEDZSCBPHHGR0ENB","worktree-bootstrap",null,"Use immediately after `git worktree add` or `git gtr new` creates a fresh worktree for any repo (a web\u002FNext app, a Node\u002FTypeScript backend, a Python data\u002FETL project, an Android\u002FGradle app, or anything else) and it won't run or build because .gitignored env files and installed dependencies weren't carried over. Fire when the user says \"set up the worktree\", \"the new worktree won't build\u002Frun\", \"missing .env in the worktree\", \"node_modules is missing\", \"gradle can't find the SDK \u002F local.properties\", or a dev server errors on missing env vars right after a worktree is created. Skip when the repo ships its own bootstrap skill: that one knows its extra credential files and hooks. Skip if the worktree has already run once.","damson\u002Fhard-won-skills","damson","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F804217?v=4","01M7BR01SMVEGA4HRD46VV1SXF","Damien D.","01M7BR01TR37MB9R73C1C0ENGG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflow\u002Fskills\u002Fworktree-bootstrap\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: worktree-bootstrap\ndescription: >\n  Use immediately after `git worktree add` or `git gtr new` creates a fresh worktree for\n  any repo (a web\u002FNext app, a Node\u002FTypeScript backend, a Python data\u002FETL project, an\n  Android\u002FGradle app, or anything else) and it won't run or build because .gitignored env\n  files and installed dependencies weren't carried over. Fire when the user says \"set up\n  the worktree\", \"the new worktree won't build\u002Frun\", \"missing .env in the worktree\",\n  \"node_modules is missing\", \"gradle can't find the SDK \u002F local.properties\", or a dev\n  server errors on missing env vars right after a worktree is created. Skip when the repo\n  ships its own bootstrap skill: that one knows its extra credential files and hooks. Skip\n  if the worktree has already run once.\n---\n\n# Bootstrap a fresh worktree (generic)\n\nA new worktree shares the repo's git history but is a **separate working tree** on disk. Two classes of thing do NOT come across, and both cause confusing first-run failures:\n\n1. **.gitignored config**: `.env`, `.env.local`, service credentials, local\n   settings. The app boots, then errors on a missing variable that \"works on\n   the other branch\".\n2. **Installed dependencies and generated artifacts**: `node_modules\u002F`, a\n   Python `.venv\u002F`, Prisma\u002Fcodegen output. These are gitignored or per-tree, so\n   a fresh worktree has none.\n\nThis skill copies the first from a donor worktree and rebuilds the second for\nthe detected stack, so the next `dev`\u002F`build`\u002F`test` works on the first try. It\ncovers what any repo needs; where a repo ships its own bootstrap skill, defer\nto that instead. It will know the extra credential files, submodules and hooks\nthis one deliberately omits.\n\n## Procedure\n\n### 1. Detect the stack\n\nFrom the worktree root:\n\n```bash\nls package.json pnpm-lock.yaml yarn.lock package-lock.json \\\n   pyproject.toml poetry.lock requirements.txt go.mod \\\n   settings.gradle settings.gradle.kts build.gradle gradlew 2>\u002Fdev\u002Fnull\n```\n\n| Signal | Stack | Dep install | Common gitignored config |\n|---|---|---|---|\n| `pnpm-lock.yaml` | Node (pnpm) | `pnpm install` | `.env`, `.env.local`, `.env.*.local` |\n| `package-lock.json` | Node (npm) | `npm ci` | `.env`, `.env.local` |\n| `yarn.lock` | Node (yarn) | `yarn install --immutable` | `.env`, `.env.local` |\n| `poetry.lock` | Python (poetry) | `poetry install` | `.env` |\n| `requirements.txt` \u002F `pyproject.toml` | Python (venv) | `python -m venv .venv && .venv\u002Fbin\u002Fpip install -e .` | `.env` |\n| `go.mod` | Go | `go mod download` | `.env`, local config |\n| `settings.gradle{,.kts}` \u002F `gradlew` | Gradle \u002F Android | none separate: Gradle resolves on first build | `local.properties`, `keystore.properties`, `*.jks` |\n\nIf nothing matches it is **general**, and the dep install is the part that\ncannot be guessed. Look for a manifest the repo's own tooling would recognise\nbefore giving up on it:\n\n```bash\nls Gemfile Gemfile.lock Cargo.toml composer.json mix.exs pubspec.yaml \\\n   Package.swift Makefile justfile 2>\u002Fdev\u002Fnull\n```\n\nWhere one turns up, take the install command from the repo's README or its CI\nworkflow rather than from memory, because it is often wrapped: `bin\u002Fsetup`,\n`make deps`, a `just` target. Where none turns up, copy the config in step 3,\nskip the install, and **say in the report that dependencies were not\ninstalled**. Step 6 otherwise fails on a missing dependency and reads as a\nbroken worktree rather than an uninstalled one, which is the harder bug to find\nbecause nothing in the output mentions the install that never ran.\n\n### 2. Find a donor worktree\n\nAny existing worktree of the same repo has the machine-local config (it's per-machine, not per-branch):\n\n```bash\nSOURCE=$(git worktree list --porcelain \\\n  | awk '\u002F^worktree \u002F {sub(\u002F^worktree \u002F, \"\"); print}' \\\n  | grep -vxF \"$(git rev-parse --show-toplevel)\" \\\n  | head -1)\necho \"Donor: ${SOURCE:-\u003Cnone. This is the only worktree>}\"\n```\n\nIf `SOURCE` is empty, ask the user where their primary checkout lives. Don't\nfabricate config.\n\n### 3. Copy the .gitignored config\n\nCopy only the files git ignores (never tracked files). List what the donor actually has, then copy the env\u002Fconfig among them:\n\n```bash\n# --ignored is REQUIRED: the files to carry over are gitignored, so plain\n# --exclude-standard (which HIDES ignored files) returns nothing.\ngit -C \"$SOURCE\" ls-files --others --ignored --exclude-standard \\\n  | grep -E '(^|\u002F)\\.env($|\\.)|\\.env\\.local|local\\.settings|\\.envrc|local\\.properties|keystore\\.properties|\\.jks$' || true\n```\n\nCopy each match into the same relative path here (create parent dirs as\nneeded). Then confirm the files this stack needs are present: `.env` \u002F\n`.env.local` for a Node\u002FPython app, `local.properties` (plus\n`keystore.properties` if the app signs) for Android. If an expected file is\nmissing, the donor didn't have it either. Stop and ask, don't fabricate it.\n\n### 4. Install dependencies (and submodules)\n\nRun the command from the step-1 table for the detected stack. For Node, match\nthe lockfile's package manager exactly: using `npm install` where the repo uses\n`pnpm` rewrites the lockfile and is a real bug. Gradle and general repos have\nno separate install step (Gradle resolves on the first build).\n\nIf the repo has submodules, a fresh worktree does not populate them:\n\n```bash\n[ -f .gitmodules ] && git submodule update --init --recursive\n```\n\n### 5. Run codegen \u002F prerequisites (only if the repo has them)\n\nCheck `package.json` scripts (or the Makefile \u002F `pyproject.toml`) for a\n`postinstall`, `generate`, `prepare`, `codegen`, or `prisma generate` step and\nrun it. Skip if none. Don't invent one.\n\n### 6. Verify the worktree actually works\n\nRun the cheapest command that exercises real config + deps, not just a lockfile check:\n\n- Node app: with the package manager step 1 detected (or, lacking a lockfile,\n  the `packageManager` field in `package.json`, else npm), run the first of\n  `typecheck` \u002F `build` that actually exists under `scripts` (read it; a\n  guessed script name fails as \"missing script\", not as a real verdict). If the\n  change is runtime-facing, start the dev server bounded and never leave it\n  running. Take the URL from the dev script's own output or the port in the\n  project's config, never a guessed 3000: a probe against the wrong port fails\n  the same way a broken server does. `timeout` is GNU coreutils and a stock\n  macOS does not have it, so the bound is the shell's:\n\n  ```bash\n  \u003Cpm> run dev & pid=$!\n  ready=\n  for _ in $(seq 1 30); do\n    curl -sf --max-time 2 \"$url\" >\u002Fdev\u002Fnull && { ready=1; break; }   # --max-time, or one hung request outlasts the loop\n    sleep 1\n  done\n  kill \"$pid\" 2>\u002Fdev\u002Fnull                                            # started it, so stop it on both paths\n  [ -n \"$ready\" ] || { echo \"dev server never answered $url\"; exit 1; }\n  ```\n- Python: `pytest -q` or `python -m \u003Cpackage> --help`.\n- Android\u002FGradle: `.\u002Fgradlew help -q`, the cheapest full configure; it proves\n  `local.properties` resolves. Then one task that actually compiles, read rather\n  than guessed, because `:app` is a convention and a multi-module project may\n  name no module that:\n\n  ```bash\n  .\u002Fgradlew -q projects                         # the module paths that exist\n  .\u002Fgradlew -q :\u003Cmodule>:tasks --all | grep -E '^assembleDebug( |$)'\n  ```\n\n  Take the module the change touches, or the smallest one that compiles where it\n  touches none in particular. Listing is not by itself a choice: on one module a\n  broader `^(assemble|compile).*Debug` returned 15 tasks, most of them test and\n  source-set variants that prove nothing about the app building.\n- General: the repo's documented smoke command.\n\nA green install is not proof: the app booting and reading its env is. If it\nfails on a missing variable, step 3 missed a file; re-list the donor's ignored\nfiles.\n\n## When to STOP\n\n- **No donor worktree and no known primary checkout.** The bootstrap needs a source for machine-local config; don't fabricate `.env` values or invent secrets.\n- **The donor's `.env` contains real secrets and the worktree is destined for a\n  shared\u002Fremote location.** Copying secrets into a shell others can read is a\n  leak: confirm the destination first.\n- **The lockfile's package manager differs from what's installed** (e.g. `pnpm-lock.yaml` but no `pnpm`). Surface the missing tool; don't silently fall back to `npm` and rewrite the lockfile.\n- **The verify step fails for a reason that isn't missing config\u002Fdeps** (a real\n  compile error on the branch). That's the branch's problem, not the\n  worktree's: report it, don't paper over it.\n- **The repo ships its own bootstrap skill.** Stop and use it. A repo-specific\n  one also handles things this generic skill omits: extra credential files,\n  submodule init, worktree-config trust prompts, and lint hooks that run on\n  push.\n\n## Anti-patterns to avoid\n\n- ❌ Committing `.env` \u002F credentials \"to fix the worktree permanently\". They're\n  gitignored because they're machine- or secret-specific: copy them, never\n  track them.\n- ❌ Authoring `.env` from memory. Copy it from a donor; a fabricated value that \"looks right\" fails silently later.\n","# Bootstrap a fresh worktree (generic)\n\nA new worktree shares the repo's git history but is a **separate working tree** on disk. Two classes of thing do NOT come across, and both cause confusing first-run failures:\n\n1. **.gitignored config**: `.env`, `.env.local`, service credentials, local\n   settings. The app boots, then errors on a missing variable that \"works on\n   the other branch\".\n2. **Installed dependencies and generated artifacts**: `node_modules\u002F`, a\n   Python `.venv\u002F`, Prisma\u002Fcodegen output. These are gitignored or per-tree, so\n   a fresh worktree has none.\n\nThis skill copies the first from a donor worktree and rebuilds the second for\nthe detected stack, so the next `dev`\u002F`build`\u002F`test` works on the first try. It\ncovers what any repo needs; where a repo ships its own bootstrap skill, defer\nto that instead. It will know the extra credential files, submodules and hooks\nthis one deliberately omits.\n\n## Procedure\n\n### 1. Detect the stack\n\nFrom the worktree root:\n\n```bash\nls package.json pnpm-lock.yaml yarn.lock package-lock.json \\\n   pyproject.toml poetry.lock requirements.txt go.mod \\\n   settings.gradle settings.gradle.kts build.gradle gradlew 2>\u002Fdev\u002Fnull\n```\n\n| Signal | Stack | Dep install | Common gitignored config |\n|---|---|---|---|\n| `pnpm-lock.yaml` | Node (pnpm) | `pnpm install` | `.env`, `.env.local`, `.env.*.local` |\n| `package-lock.json` | Node (npm) | `npm ci` | `.env`, `.env.local` |\n| `yarn.lock` | Node (yarn) | `yarn install --immutable` | `.env`, `.env.local` |\n| `poetry.lock` | Python (poetry) | `poetry install` | `.env` |\n| `requirements.txt` \u002F `pyproject.toml` | Python (venv) | `python -m venv .venv && .venv\u002Fbin\u002Fpip install -e .` | `.env` |\n| `go.mod` | Go | `go mod download` | `.env`, local config |\n| `settings.gradle{,.kts}` \u002F `gradlew` | Gradle \u002F Android | none separate: Gradle resolves on first build | `local.properties`, `keystore.properties`, `*.jks` |\n\nIf nothing matches it is **general**, and the dep install is the part that\ncannot be guessed. Look for a manifest the repo's own tooling would recognise\nbefore giving up on it:\n\n```bash\nls Gemfile Gemfile.lock Cargo.toml composer.json mix.exs pubspec.yaml \\\n   Package.swift Makefile justfile 2>\u002Fdev\u002Fnull\n```\n\nWhere one turns up, take the install command from the repo's README or its CI\nworkflow rather than from memory, because it is often wrapped: `bin\u002Fsetup`,\n`make deps`, a `just` target. Where none turns up, copy the config in step 3,\nskip the install, and **say in the report that dependencies were not\ninstalled**. Step 6 otherwise fails on a missing dependency and reads as a\nbroken worktree rather than an uninstalled one, which is the harder bug to find\nbecause nothing in the output mentions the install that never ran.\n\n### 2. Find a donor worktree\n\nAny existing worktree of the same repo has the machine-local config (it's per-machine, not per-branch):\n\n```bash\nSOURCE=$(git worktree list --porcelain \\\n  | awk '\u002F^worktree \u002F {sub(\u002F^worktree \u002F, \"\"); print}' \\\n  | grep -vxF \"$(git rev-parse --show-toplevel)\" \\\n  | head -1)\necho \"Donor: ${SOURCE:-\u003Cnone. This is the only worktree>}\"\n```\n\nIf `SOURCE` is empty, ask the user where their primary checkout lives. Don't\nfabricate config.\n\n### 3. Copy the .gitignored config\n\nCopy only the files git ignores (never tracked files). List what the donor actually has, then copy the env\u002Fconfig among them:\n\n```bash\n# --ignored is REQUIRED: the files to carry over are gitignored, so plain\n# --exclude-standard (which HIDES ignored files) returns nothing.\ngit -C \"$SOURCE\" ls-files --others --ignored --exclude-standard \\\n  | grep -E '(^|\u002F)\\.env($|\\.)|\\.env\\.local|local\\.settings|\\.envrc|local\\.properties|keystore\\.properties|\\.jks$' || true\n```\n\nCopy each match into the same relative path here (create parent dirs as\nneeded). Then confirm the files this stack needs are present: `.env` \u002F\n`.env.local` for a Node\u002FPython app, `local.properties` (plus\n`keystore.properties` if the app signs) for Android. If an expected file is\nmissing, the donor didn't have it either. Stop and ask, don't fabricate it.\n\n### 4. Install dependencies (and submodules)\n\nRun the command from the step-1 table for the detected stack. For Node, match\nthe lockfile's package manager exactly: using `npm install` where the repo uses\n`pnpm` rewrites the lockfile and is a real bug. Gradle and general repos have\nno separate install step (Gradle resolves on the first build).\n\nIf the repo has submodules, a fresh worktree does not populate them:\n\n```bash\n[ -f .gitmodules ] && git submodule update --init --recursive\n```\n\n### 5. Run codegen \u002F prerequisites (only if the repo has them)\n\nCheck `package.json` scripts (or the Makefile \u002F `pyproject.toml`) for a\n`postinstall`, `generate`, `prepare`, `codegen`, or `prisma generate` step and\nrun it. Skip if none. Don't invent one.\n\n### 6. Verify the worktree actually works\n\nRun the cheapest command that exercises real config + deps, not just a lockfile check:\n\n- Node app: with the package manager step 1 detected (or, lacking a lockfile,\n  the `packageManager` field in `package.json`, else npm), run the first of\n  `typecheck` \u002F `build` that actually exists under `scripts` (read it; a\n  guessed script name fails as \"missing script\", not as a real verdict). If the\n  change is runtime-facing, start the dev server bounded and never leave it\n  running. Take the URL from the dev script's own output or the port in the\n  project's config, never a guessed 3000: a probe against the wrong port fails\n  the same way a broken server does. `timeout` is GNU coreutils and a stock\n  macOS does not have it, so the bound is the shell's:\n\n  ```bash\n  \u003Cpm> run dev & pid=$!\n  ready=\n  for _ in $(seq 1 30); do\n    curl -sf --max-time 2 \"$url\" >\u002Fdev\u002Fnull && { ready=1; break; }   # --max-time, or one hung request outlasts the loop\n    sleep 1\n  done\n  kill \"$pid\" 2>\u002Fdev\u002Fnull                                            # started it, so stop it on both paths\n  [ -n \"$ready\" ] || { echo \"dev server never answered $url\"; exit 1; }\n  ```\n- Python: `pytest -q` or `python -m \u003Cpackage> --help`.\n- Android\u002FGradle: `.\u002Fgradlew help -q`, the cheapest full configure; it proves\n  `local.properties` resolves. Then one task that actually compiles, read rather\n  than guessed, because `:app` is a convention and a multi-module project may\n  name no module that:\n\n  ```bash\n  .\u002Fgradlew -q projects                         # the module paths that exist\n  .\u002Fgradlew -q :\u003Cmodule>:tasks --all | grep -E '^assembleDebug( |$)'\n  ```\n\n  Take the module the change touches, or the smallest one that compiles where it\n  touches none in particular. Listing is not by itself a choice: on one module a\n  broader `^(assemble|compile).*Debug` returned 15 tasks, most of them test and\n  source-set variants that prove nothing about the app building.\n- General: the repo's documented smoke command.\n\nA green install is not proof: the app booting and reading its env is. If it\nfails on a missing variable, step 3 missed a file; re-list the donor's ignored\nfiles.\n\n## When to STOP\n\n- **No donor worktree and no known primary checkout.** The bootstrap needs a source for machine-local config; don't fabricate `.env` values or invent secrets.\n- **The donor's `.env` contains real secrets and the worktree is destined for a\n  shared\u002Fremote location.** Copying secrets into a shell others can read is a\n  leak: confirm the destination first.\n- **The lockfile's package manager differs from what's installed** (e.g. `pnpm-lock.yaml` but no `pnpm`). Surface the missing tool; don't silently fall back to `npm` and rewrite the lockfile.\n- **The verify step fails for a reason that isn't missing config\u002Fdeps** (a real\n  compile error on the branch). That's the branch's problem, not the\n  worktree's: report it, don't paper over it.\n- **The repo ships its own bootstrap skill.** Stop and use it. A repo-specific\n  one also handles things this generic skill omits: extra credential files,\n  submodule init, worktree-config trust prompts, and lint hooks that run on\n  push.\n\n## Anti-patterns to avoid\n\n- ❌ Committing `.env` \u002F credentials \"to fix the worktree permanently\". They're\n  gitignored because they're machine- or secret-specific: copy them, never\n  track them.\n- ❌ Authoring `.env` from memory. Copy it from a donor; a fabricated value that \"looks right\" fails silently later.\n",{"name":5,"description":7},"main","9435f9fa04b69d2217f8cab3c817dd5c3c1d1021","plugins\u002Fgit-workflow\u002Fskills\u002Fworktree-bootstrap",0,"https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills","https:\u002F\u002Fgithub.com\u002Fdamson","http:\u002F\u002Fgoo.gl\u002F3UwFRt","2026-11-14 14:28:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add damson\u002Fhard-won-skills --skill worktree-bootstrap",{"tool":38,"command":39},"bunx","bunx skills add damson\u002Fhard-won-skills --skill worktree-bootstrap",{"tool":41,"command":42},"pnpm","pnpm dlx skills add damson\u002Fhard-won-skills --skill worktree-bootstrap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflow\u002Fskills\u002Fworktree-bootstrap\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"README.md","REFERENCE","参考文档",2396,"https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fgit-workflow\u002Fskills\u002Fworktree-bootstrap\u002FREADME.md",[53,60,66,71,76,81],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7BRCESR9BRFAH87J2ZQY5T2","skill-two","Fixture skill","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_welcome_total\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7BRCDPHEPZES71BYBRTZ1G3","skill-one","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_welcome_total\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":67,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7BRCCHHB3Q07BR0QN339D3F","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_table_count\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":72,"name":62,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7BRC9J97QKZHGKVXMER5ZEE","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fwrong_table_count\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[],{"skillNo":77,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7BRC8C39NM8VVAQ3TKP0CRS","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid_marketplace\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-two\u002FSKILL.md",[],[],{"skillNo":82,"name":62,"nameZh":6,"description":56,"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},"01M7BRC75THG394KDGYV35ET19","https:\u002F\u002Fgithub.com\u002Fdamson\u002Fhard-won-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid_marketplace\u002Fplugins\u002Falpha\u002Fskills\u002Fskill-one\u002FSKILL.md",[],[]]