[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M782MCA4YV6AD77P5K0CSH6G":3,"skill-same:01M782MCA4YV6AD77P5K0CSH6G":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M782MCA4YV6AD77P5K0CSH6G","adopt",null,"Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup. Use for \u002Fadopt or requests to bootstrap Blueprint into an established app. Use onboard for a fresh scaffold.","bradtraversy\u002Fskillpass","bradtraversy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5550850?v=4","01M782H8BT6A97A17XDFHDABWZ","Brad Traversy","01M782H8CDJZW3HYDHX23FA9VF",26,"MIT","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadopt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: adopt\ndescription: Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup. Use for \u002Fadopt or requests to bootstrap Blueprint into an established app. Use onboard for a fresh scaffold.\ndisable-model-invocation: true\n---\n\n# adopt - bootstrap the blueprint from an existing codebase\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    existing codebase  ->  [adopt]  ->  project-plan + build-plan + coding-standards  ->  \u002Foverview  ->  normal loop\n    (already has code)     (survey +     (seeded from the real code; shipped               (project-       (\u002Ffeature,\n                            interview)     features already checked off)                    overview.md)     \u002Fimplement, ...)\n\nThe standard onboarding assumes a freshly scaffolded, near-empty app: you write\nthe two plans from scratch and build forward. That doesn't fit a project that\nalready has thousands of lines of working code. `\u002Fadopt` is the brownfield\non-ramp: it reads what's already there, asks you only for what the code can't tell\nit (the *why* and the *roadmap*), and produces the same input files the rest of\nthe workflow expects - so an existing project joins the loop without you\nhand-writing everything.\n\nIt generates the inputs; it does not generate `project-overview.md`. That stays\n`\u002Foverview`'s job. `\u002Fadopt` ends by telling you to run `\u002Foverview`.\n\n## Input\n\nA description of what the project is, if the user offers one. Otherwise just the\nrepository itself. No argument is required.\n\n## Step 0 - confirm it's brownfield and safe\n\nLook at `blueprint\u002Fproject-plan.md` and `blueprint\u002Fbuild-plan.md`.\n\n- If they're missing or still the empty worksheet\u002Fplaceholder, proceed.\n- If they already hold real content, this project is already adopted. Stop and say\n  so; offer to refresh a specific file instead of overwriting work the user owns.\n\nNever overwrite a filled-in plan without explicit confirmation. Never run a\nframework scaffolder (the blueprint is an overlay, never a generator).\n\nProtect the project README:\n\n- If the root `README.md` already looks like a real project README, leave it\n  alone.\n- If the root `README.md` is the copied Blueprint workflow doc (for example it\n  starts with `# AI Coding Blueprint`), report it as obsolete overlay content\n  and ask before replacing or removing it. Do not move it into `blueprint\u002F`.\n- Do not create or overwrite a root project README for a brownfield app unless\n  the user explicitly asks. The existing project face belongs to the app, not the\n  workflow.\n\n## Step 1 - survey the codebase (read-only)\n\nRead the repo to establish the facts. Change nothing in this step. Establish:\n\n- **Stack and tooling** - language(s), framework(s), and versions, from the real\n  manifest (`package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`,\n  `Gemfile`, `Cargo.toml`, etc.). Note the package manager actually in use (lockfile).\n- **Commands** - the real dev \u002F build \u002F test \u002F lint scripts. These feed the\n  Commands section of `AGENTS.md` and, per the testing opt-in switch, decide\n  whether a testing gate even applies.\n- **Conventions in practice** - directory layout, component\u002Ffile naming, styling\n  approach, state management, data-fetching pattern, error handling. Read what the\n  code *does*, not what a default template prescribes.\n- **Testing reality** - is a runner configured and are there tests, or none? Be\n  honest; don't describe a gate the project doesn't have.\n- **Verification and CI** - note any combined verification command, GitHub\n  remote, `.github\u002Fworkflows\u002F`, or external CI. Preserve what already exists.\n- **What the app already does** - the shipped features, inferred from routes,\n  pages, entry points, and modules. This becomes the *checked* part of the build plan.\n\nKeep notes; you'll turn them into the files in Step 3.\n\n## Step 2 - interview for intent\n\nThe code reveals *what* and *how*, never *why* or *what next*. Ask the user a short\nset of questions (aim for three to five, not an interrogation) to fill the gaps:\n\n- What is this project for, and who uses it? (the problem and the users)\n- Is the stack and structure you found intentional, or are there parts they'd call\n  legacy \u002F want to change?\n- What do you want to build next? (the unchecked items in the build plan)\n- Anything the survey got wrong or missed?\n\nIf the user already gave intent up front, skip what they've answered. Don't ask\nwhat you can read from the code.\n\n## Step 3 - generate the inputs\n\nWrite these, drawn from the survey (facts) and the interview (intent). Mark every\ninference you're unsure of with a clear `> TODO (confirm)` so the user can correct\nit rather than inherit a wrong guess.\n\n- **`blueprint\u002Fproject-plan.md`** - the what & why, following the existing\n  worksheet structure (problem, users, features, data, tech, monetization, UI\u002FUX).\n  The \"features\" and \"tech\" sections describe what *already exists*; the rest comes\n  from the interview.\n- **`blueprint\u002Fbuild-plan.md`** - the ordered feature list as a checklist. **Mark\n  shipped features `- [x]`** (this is the brownfield difference: the build plan\n  reflects reality, so most of an existing app starts checked) and the roadmap\n  items from the interview as `- [ ]`. This makes `\u002Fstatus` and `\u002Ffeature` work\n  immediately - the next unchecked item is genuinely what's next.\n- **`blueprint\u002Fcontext\u002Fcoding-standards.md`** - rewrite the default to match the\n  project's *actual* conventions from Step 1, not the shipped Next.js\u002FPrisma\n  defaults. Keep the Writing and Comments sections; replace the stack-specific ones\n  with what the code really does. Its Testing section must reflect the real testing\n  state (the opt-in switch is a `test` command in `AGENTS.md`).\n- **`AGENTS.md` Commands section** - fill in the real dev \u002F build \u002F test \u002F lint\n  commands you found, so the rest of the workflow (and the testing gate) uses the\n  project's actual scripts. Include `Verify` when a real combined command exists.\n\nDo not write `project-overview.md`; that's `\u002Foverview`'s job, downstream of these.\n\n## Step 4 - point to optional CI setup\n\nDo not create or change Verify commands or GitHub workflows during adoption.\nReport any verification command or CI already present. When equivalent automatic\npull-request checks are absent, mention the optional standalone setup:\n\n```text\nRun \u002Fci or $ci when you want automatic GitHub checks.\n```\n\nExplain that CI is not required to finish adoption. The `\u002Fci` skill owns\nproject-specific Verify and GitHub workflow setup.\n\n## Step 5 - ask about Blueprint visibility\n\nAsk how the Blueprint workflow files should be handled in git, unless the user\nalready gave a preference:\n\n```text\nBlueprint visibility?\n\n1. Commit Blueprint workflow files\n   Portable. Best for teams and working across machines.\n\n2. Keep Blueprint workflow files local\n   Adds .agents\u002F, .claude\u002F, blueprint\u002F, and CLAUDE.md to .gitignore.\n   Keeps AGENTS.md public as the lightweight project agent guide.\n```\n\nRecommend option 1 by default. If the user chooses option 2:\n\n- Add this block to `.gitignore`, preserving existing entries:\n\n  ```gitignore\n  # AI Blueprint local workflow files\n  .agents\u002F\n  .claude\u002F\n  blueprint\u002F\n  CLAUDE.md\n  ```\n\n- Keep `AGENTS.md` tracked. It remains the lightweight public project guide for\n  commands and conventions.\n- Make `AGENTS.md` public-safe: keep project description, commands, testing gate,\n  and coding conventions, but remove or avoid Blueprint workflow explanations,\n  hidden adapter paths, workflow-document pointers, and core skill lists that\n  would expose the local-only workflow.\n- Explain that local-only mode hides the workflow contents from the repo, but the\n  `.gitignore` names still reveal the ignored paths.\n- Explain that Blueprint state, specs, findings, and history will not travel\n  with the repo; another machine needs the Blueprint reinstalled or restored\n  locally.\n- Because adoption runs right after the Blueprint files were added to an\n  existing repository, they are more likely to already be staged or committed\n  than in a fresh install. If any of `.agents\u002F`, `.claude\u002F`, `blueprint\u002F`, or\n  `CLAUDE.md` are already tracked, say `.gitignore` will not hide tracked files.\n  Ask before running\n  `git rm --cached -r .agents .claude blueprint CLAUDE.md`, and\n  only run it if the user explicitly approves. Never delete the local files.\n\n## Step 6 - review gate, then hand off\n\nStop and show the user what you generated, calling out:\n\n- the **build-plan split** - what you marked shipped vs not, since that's the\n  judgment most worth their eyes,\n- every `> TODO (confirm)` you left,\n- anything the survey and the interview disagreed on,\n- verification command and GitHub checks status,\n- Blueprint visibility choice, and a tracked-file warning if local-only mode was\n  chosen after files were already tracked.\n\nThese files are the ones the user *owns*. Have them review and adjust, then tell\nthem to run `\u002Foverview` to distill the plans into `project-overview.md` and start\nthe normal loop.\n\n## Rules\n\n- **Read-only until Step 3.** The survey changes nothing; only generation writes.\n- **Reflect reality, don't prescribe.** `coding-standards.md` must match the code\n  that exists. A project using Zustand and REST routes should not be handed\n  standards about Server Actions and Prisma just because that's the default.\n- Follow and preserve the proportional-engineering contract in `AGENTS.md`;\n  record only established usage or trust constraints and leave unknowns blank.\n- **Never invent intent.** Ask for the why and the roadmap; mark anything inferred\n  with `> TODO (confirm)`. Silent guesses about purpose are the main failure mode.\n- **Don't clobber owned work.** If the plans already have real content, confirm\n  before touching them. Never run a scaffolder.\n- **Be honest about testing.** If there's no runner, say testing is opt-in and not\n  yet set up; don't describe a gate the project hasn't adopted.\n- Keep `AGENTS.md` public in local-only mode unless the user explicitly asks for\n  a more advanced setup.\n- Do not untrack Blueprint files with `git rm --cached` without a separate\n  explicit approval.\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n","# adopt - bootstrap the blueprint from an existing codebase\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    existing codebase  ->  [adopt]  ->  project-plan + build-plan + coding-standards  ->  \u002Foverview  ->  normal loop\n    (already has code)     (survey +     (seeded from the real code; shipped               (project-       (\u002Ffeature,\n                            interview)     features already checked off)                    overview.md)     \u002Fimplement, ...)\n\nThe standard onboarding assumes a freshly scaffolded, near-empty app: you write\nthe two plans from scratch and build forward. That doesn't fit a project that\nalready has thousands of lines of working code. `\u002Fadopt` is the brownfield\non-ramp: it reads what's already there, asks you only for what the code can't tell\nit (the *why* and the *roadmap*), and produces the same input files the rest of\nthe workflow expects - so an existing project joins the loop without you\nhand-writing everything.\n\nIt generates the inputs; it does not generate `project-overview.md`. That stays\n`\u002Foverview`'s job. `\u002Fadopt` ends by telling you to run `\u002Foverview`.\n\n## Input\n\nA description of what the project is, if the user offers one. Otherwise just the\nrepository itself. No argument is required.\n\n## Step 0 - confirm it's brownfield and safe\n\nLook at `blueprint\u002Fproject-plan.md` and `blueprint\u002Fbuild-plan.md`.\n\n- If they're missing or still the empty worksheet\u002Fplaceholder, proceed.\n- If they already hold real content, this project is already adopted. Stop and say\n  so; offer to refresh a specific file instead of overwriting work the user owns.\n\nNever overwrite a filled-in plan without explicit confirmation. Never run a\nframework scaffolder (the blueprint is an overlay, never a generator).\n\nProtect the project README:\n\n- If the root `README.md` already looks like a real project README, leave it\n  alone.\n- If the root `README.md` is the copied Blueprint workflow doc (for example it\n  starts with `# AI Coding Blueprint`), report it as obsolete overlay content\n  and ask before replacing or removing it. Do not move it into `blueprint\u002F`.\n- Do not create or overwrite a root project README for a brownfield app unless\n  the user explicitly asks. The existing project face belongs to the app, not the\n  workflow.\n\n## Step 1 - survey the codebase (read-only)\n\nRead the repo to establish the facts. Change nothing in this step. Establish:\n\n- **Stack and tooling** - language(s), framework(s), and versions, from the real\n  manifest (`package.json`, `requirements.txt`, `pyproject.toml`, `go.mod`,\n  `Gemfile`, `Cargo.toml`, etc.). Note the package manager actually in use (lockfile).\n- **Commands** - the real dev \u002F build \u002F test \u002F lint scripts. These feed the\n  Commands section of `AGENTS.md` and, per the testing opt-in switch, decide\n  whether a testing gate even applies.\n- **Conventions in practice** - directory layout, component\u002Ffile naming, styling\n  approach, state management, data-fetching pattern, error handling. Read what the\n  code *does*, not what a default template prescribes.\n- **Testing reality** - is a runner configured and are there tests, or none? Be\n  honest; don't describe a gate the project doesn't have.\n- **Verification and CI** - note any combined verification command, GitHub\n  remote, `.github\u002Fworkflows\u002F`, or external CI. Preserve what already exists.\n- **What the app already does** - the shipped features, inferred from routes,\n  pages, entry points, and modules. This becomes the *checked* part of the build plan.\n\nKeep notes; you'll turn them into the files in Step 3.\n\n## Step 2 - interview for intent\n\nThe code reveals *what* and *how*, never *why* or *what next*. Ask the user a short\nset of questions (aim for three to five, not an interrogation) to fill the gaps:\n\n- What is this project for, and who uses it? (the problem and the users)\n- Is the stack and structure you found intentional, or are there parts they'd call\n  legacy \u002F want to change?\n- What do you want to build next? (the unchecked items in the build plan)\n- Anything the survey got wrong or missed?\n\nIf the user already gave intent up front, skip what they've answered. Don't ask\nwhat you can read from the code.\n\n## Step 3 - generate the inputs\n\nWrite these, drawn from the survey (facts) and the interview (intent). Mark every\ninference you're unsure of with a clear `> TODO (confirm)` so the user can correct\nit rather than inherit a wrong guess.\n\n- **`blueprint\u002Fproject-plan.md`** - the what & why, following the existing\n  worksheet structure (problem, users, features, data, tech, monetization, UI\u002FUX).\n  The \"features\" and \"tech\" sections describe what *already exists*; the rest comes\n  from the interview.\n- **`blueprint\u002Fbuild-plan.md`** - the ordered feature list as a checklist. **Mark\n  shipped features `- [x]`** (this is the brownfield difference: the build plan\n  reflects reality, so most of an existing app starts checked) and the roadmap\n  items from the interview as `- [ ]`. This makes `\u002Fstatus` and `\u002Ffeature` work\n  immediately - the next unchecked item is genuinely what's next.\n- **`blueprint\u002Fcontext\u002Fcoding-standards.md`** - rewrite the default to match the\n  project's *actual* conventions from Step 1, not the shipped Next.js\u002FPrisma\n  defaults. Keep the Writing and Comments sections; replace the stack-specific ones\n  with what the code really does. Its Testing section must reflect the real testing\n  state (the opt-in switch is a `test` command in `AGENTS.md`).\n- **`AGENTS.md` Commands section** - fill in the real dev \u002F build \u002F test \u002F lint\n  commands you found, so the rest of the workflow (and the testing gate) uses the\n  project's actual scripts. Include `Verify` when a real combined command exists.\n\nDo not write `project-overview.md`; that's `\u002Foverview`'s job, downstream of these.\n\n## Step 4 - point to optional CI setup\n\nDo not create or change Verify commands or GitHub workflows during adoption.\nReport any verification command or CI already present. When equivalent automatic\npull-request checks are absent, mention the optional standalone setup:\n\n```text\nRun \u002Fci or $ci when you want automatic GitHub checks.\n```\n\nExplain that CI is not required to finish adoption. The `\u002Fci` skill owns\nproject-specific Verify and GitHub workflow setup.\n\n## Step 5 - ask about Blueprint visibility\n\nAsk how the Blueprint workflow files should be handled in git, unless the user\nalready gave a preference:\n\n```text\nBlueprint visibility?\n\n1. Commit Blueprint workflow files\n   Portable. Best for teams and working across machines.\n\n2. Keep Blueprint workflow files local\n   Adds .agents\u002F, .claude\u002F, blueprint\u002F, and CLAUDE.md to .gitignore.\n   Keeps AGENTS.md public as the lightweight project agent guide.\n```\n\nRecommend option 1 by default. If the user chooses option 2:\n\n- Add this block to `.gitignore`, preserving existing entries:\n\n  ```gitignore\n  # AI Blueprint local workflow files\n  .agents\u002F\n  .claude\u002F\n  blueprint\u002F\n  CLAUDE.md\n  ```\n\n- Keep `AGENTS.md` tracked. It remains the lightweight public project guide for\n  commands and conventions.\n- Make `AGENTS.md` public-safe: keep project description, commands, testing gate,\n  and coding conventions, but remove or avoid Blueprint workflow explanations,\n  hidden adapter paths, workflow-document pointers, and core skill lists that\n  would expose the local-only workflow.\n- Explain that local-only mode hides the workflow contents from the repo, but the\n  `.gitignore` names still reveal the ignored paths.\n- Explain that Blueprint state, specs, findings, and history will not travel\n  with the repo; another machine needs the Blueprint reinstalled or restored\n  locally.\n- Because adoption runs right after the Blueprint files were added to an\n  existing repository, they are more likely to already be staged or committed\n  than in a fresh install. If any of `.agents\u002F`, `.claude\u002F`, `blueprint\u002F`, or\n  `CLAUDE.md` are already tracked, say `.gitignore` will not hide tracked files.\n  Ask before running\n  `git rm --cached -r .agents .claude blueprint CLAUDE.md`, and\n  only run it if the user explicitly approves. Never delete the local files.\n\n## Step 6 - review gate, then hand off\n\nStop and show the user what you generated, calling out:\n\n- the **build-plan split** - what you marked shipped vs not, since that's the\n  judgment most worth their eyes,\n- every `> TODO (confirm)` you left,\n- anything the survey and the interview disagreed on,\n- verification command and GitHub checks status,\n- Blueprint visibility choice, and a tracked-file warning if local-only mode was\n  chosen after files were already tracked.\n\nThese files are the ones the user *owns*. Have them review and adjust, then tell\nthem to run `\u002Foverview` to distill the plans into `project-overview.md` and start\nthe normal loop.\n\n## Rules\n\n- **Read-only until Step 3.** The survey changes nothing; only generation writes.\n- **Reflect reality, don't prescribe.** `coding-standards.md` must match the code\n  that exists. A project using Zustand and REST routes should not be handed\n  standards about Server Actions and Prisma just because that's the default.\n- Follow and preserve the proportional-engineering contract in `AGENTS.md`;\n  record only established usage or trust constraints and leave unknowns blank.\n- **Never invent intent.** Ask for the why and the roadmap; mark anything inferred\n  with `> TODO (confirm)`. Silent guesses about purpose are the main failure mode.\n- **Don't clobber owned work.** If the plans already have real content, confirm\n  before touching them. Never run a scaffolder.\n- **Be honest about testing.** If there's no runner, say testing is opt-in and not\n  yet set up; don't describe a gate the project hasn't adopted.\n- Keep `AGENTS.md` public in local-only mode unless the user explicitly asks for\n  a more advanced setup.\n- Do not untrack Blueprint files with `git rm --cached` without a separate\n  explicit approval.\n\n## Formatting\n\nFormat the output to match the project's conventions in\n`blueprint\u002Fcontext\u002Fai-interaction.md`: concise, scannable markdown, with lists for\nenumerations and tables for matrices rather than dense paragraphs.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","0007775402258962018a93be4dbf1cbcbc1536d8",".claude\u002Fskills\u002Fadopt",3,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass","https:\u002F\u002Fgithub.com\u002Fbradtraversy","traversymedia.com","Full stack web developer and online instructor at https:\u002F\u002Ftraversymedia.com and https:\u002F\u002Fstart.dev","2026-10-06 00:26:26",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add bradtraversy\u002Fskillpass --skill adopt",{"tool":40,"command":41},"bunx","bunx skills add bradtraversy\u002Fskillpass --skill adopt",{"tool":43,"command":44},"pnpm","pnpm dlx skills add bradtraversy\u002Fskillpass --skill adopt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fadopt\u002FSKILL.md",[],[48,54,60,65,71,77],{"skillNo":49,"name":50,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M782QBBKH3WTBZDE9DP52XH4","plan","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":6,"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},"01M782Q980Y1KP1J77TNJHD5H8","apply","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fapply\u002FSKILL.md",[],[],{"skillNo":61,"name":50,"nameZh":6,"description":6,"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},"01M782Q75AS3P8SW7D819TACVD","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":6,"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},"01M782Q5WAP9DQH14TEKG5ZFX5","undeclared-network","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fundeclared-network\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M782Q424YF4TAYYX9TCCZCS8","prompt-injection","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fprompt-injection\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":6,"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},"01M782Q28RQV6MJM98J6EN7XFF","missing-manifest","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fmissing-manifest\u002FSKILL.md",[],[]]