[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C7VGXT42ZBTAZXQ3ZPZSN6":3,"skill-same:01M7C7VGXT42ZBTAZXQ3ZPZSN6":96},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":13,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7C7VGXT42ZBTAZXQ3ZPZSN6","highway-setup",null,"Orchestrates initial highway setup through the owning governance skills. Use when the person sets up highway in a repository for the first time, or runs setup again to revise it.","jacob623\u002Fhighway-skills","jacob623","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9532643?v=4","01M7C7HA4F52SFFC164SQ76BC6","01M7C7HA57FCG77W7TGPX5R706",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: highway-setup\ndescription: \"Orchestrates initial highway setup through the owning governance skills. Use when the person sets up highway in a repository for the first time, or runs setup again to revise it.\"\nlicense: Apache-2.0\nmetadata:\n  version: 10.4.0\n  usage: \"Run highway-setup.\"\n---\n\n# highway-setup\n\n## Purpose\n\nSeeds the project's catalogs, then orchestrates Profile, Objectives, Controls, and NFRs in order when the person runs setup.\n\n## When to use\n\n- The person invokes `highway-setup` and `library\u002Fknowledge\u002Fprofile.md` is absent.\n- The person invokes `highway-setup` again after a prior setup run.\n\n## When not to use\n\nDo not collect Profile, Objective, Control, or NFR evidence.\nDo not write Profile, Objective, Control, or NFR records or catalogs.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\nDo not show `Finished` to the person.\n\n## Inputs\n\n- `highway-profile`.\n- `highway-objectives`.\n- `highway-controls`.\n- `highway-nfrs`.\n- `library\u002Fknowledge\u002Fprofile.md` when present.\n- The seeded files' skeletons in `assets\u002F`, one per row of the Seed table.\n- The highway-experience skill, activated first.\n- The person's request to run setup.\n\n## Outputs\n\n- The welcome, once, when Profile has not been written.\n- One domain transition before Objectives, Controls, and NFRs.\n- The closing conclusion, once, after NFRs returns `Finished`.\n- Each seeded file that was absent, written from its asset, such as `requests\u002Frequests.md` from `assets\u002Frequest-catalog.md`.\n\n## Procedure\n\nActivate the highway-experience skill before any output the person sees, and follow it for Highway's identity, the Experience Standard, and the storage contract.\n\nUser-visible interaction follows the Highway Experience Standard.\n\nSeed first. Then delegate each owner in this order: Profile, Objectives, Controls, NFRs. Stay with the current owner until it returns `Finished`. Render that owner's messages as written. Do not answer its question, restate its recommendations, or add a second question.\n\n`Finished` is the only result that advances. Do not show that word. An owner that stops without `Finished` ends Setup. Do not delegate a later owner, and do not emit the conclusion.\n\n### Seed\n\nSeed in every setup run, after the storage contract's mode check and before the welcome.\n\nFor each row below, when the project file is absent, write it from the asset unchanged. Write every absent file as one group. Do not change a file that exists. Emit nothing for this step.\n\n| Asset | Project file |\n|---|---|\n| `assets\u002Frequest-catalog.md` | `requests\u002Frequests.md` |\n| `assets\u002Fdiscovery-catalog.md` | `discoveries\u002Fdiscoveries.md` |\n| `assets\u002Fadr-catalog.md` | `adrs\u002Fadrs.md` |\n| `assets\u002Farchitecture-catalog.md` | `architectures\u002Farchitectures.md` |\n| `assets\u002Fimplementation-catalog.md` | `implementations\u002Fimplementations.md` |\n| `assets\u002Fcapability-catalog.md` | `implementations\u002Fcapabilities.md` |\n| `assets\u002Fcodify-catalog.md` | `code\u002Fcode.md` |\n| `assets\u002Fcodify-integrations.md` | `code\u002Fintegrations.md` |\n| `assets\u002Fcodify-platforms.md` | `library\u002Fcoding-standards\u002Fcodify-platforms.md` |\n| `assets\u002Fcoding-standards-catalog.md` | `library\u002Fcoding-standards\u002Fcoding-standards.md` |\n| `assets\u002Fassessment-findings.md` | `library\u002Fknowledge\u002Fassessment-findings.md` |\n| `assets\u002Fstorage.md` | `library\u002Fknowledge\u002Fstorage.md` |\n\n### Welcome\n\nWhen `library\u002Fknowledge\u002Fprofile.md` is absent, emit the lines below before Profile. Emit \"Welcome to Highway\" as a level-2 heading and \"During setup we'll:\" as a level-3 heading. Emit every other line as written. Do not emit the welcome when that file exists.\n\nWelcome to Highway\n*Turn organizational knowledge into connected decisions.*\n**Your context stays yours.**\n\nHighway builds on information you choose to accept into your repository. Your repository remains the authoritative source of truth, and you retain ownership of the context and artifacts created through Highway.\n\n---\n\nDuring setup we'll:\n\n- **Learn about your organization**, where you'd like to go, how you plan to get there, and what principles guide decisions.\n- **Identify important business outcomes** worth pursuing.\n- **Establish safeguards** that future technology decisions should respect.\n- **Define operational expectations** for how future solutions should behave.\n\nYou don't need to have everything figured out in advance. We'll build this foundation together, and you can refine it over time as your organization evolves.\n\nNow, let's get started.\n\n---\n\nThen delegate `highway-profile`.\n\n### Profile\n\nDelegate `highway-profile`. Profile opens the organization conversation. Do not add a transition before it.\n\nWhen Profile returns `Finished`, emit the Objectives transition and delegate `highway-objectives` in that same moment.\n\n### Objectives\n\n---\n\n**Let's identify some outcomes worth pursuing.**\n\nThese give Highway something concrete to connect future decisions back to.\n\nWhen Objectives returns `Finished`, emit the Controls transition and delegate `highway-controls`.\n\n### Controls\n\n---\n\n**Now let's establish the safeguards that should guide future technology decisions.**\n\nThese help Highway keep future recommendations aligned with what needs to remain true.\n\nWhen Controls returns `Finished`, emit the NFR transition and delegate `highway-nfrs`.\n\n### NFRs\n\n---\n\n**Now let's consider the operational expectations future solutions should meet.**\n\nThese help connect your safeguards to how solutions need to behave in practice.\n\nWhen NFRs returns `Finished`, emit the conclusion.\n\n### Conclusion\n\nEmit this once.\n\n**Your foundational Highway context is now in place.**\n\nHighway now has organizational context, business objectives, safeguards, and operational expectations it can build on in future work.\n\n**Where would you like to go next?**\n\nRun `highway-onboarding` to inform Highway of your current technology landscape. This aids Highway in providing cohesive recommendations.\n\nRun highway-help to explore what Highway can help you do.\n\n## Resume\n\nEvery `highway-setup` run starts at Seed, then Profile. Setup stores no checkpoint. Seeding writes only absent files, so a later run keeps every catalog as it is. When `profile.md` already exists, skip the welcome and still delegate Profile, then Objectives, Controls, and NFRs. Each owner reviews what it already holds before returning `Finished`.\n\n## Verification\n\n- Seeding runs before the welcome in every run.\n- Seeding writes only absent seeded files, each from its asset.\n- Seeding changes no existing file.\n- Seeding emits nothing.\n- Owner order is Profile, Objectives, Controls, NFRs.\n- The welcome is emitted once, and only when `profile.md` is absent.\n- Profile is always delegated.\n- Each later owner is delegated only after the previous owner returns `Finished`.\n- The Objectives, Controls, and NFR transitions are each emitted once, directly before that owner's first message.\n- Setup does not add a question to an owner's message.\n- Setup does not add a synthesis between owners.\n- `Finished` is not shown.\n- An owner that stops without `Finished` ends Setup before the next owner.\n- The conclusion is emitted once, after NFRs returns `Finished`.\n- The conclusion directs the person to `highway-onboarding` before `highway-help`.\n- Setup writes no file other than the seeded files.\n\n## Error Handling\n\n- A seeded file that cannot be written stops Setup before the welcome. Say which file could not be written and what the person can do next.\n- An owner that stops without `Finished` ends Setup. The owner's message is the person's explanation. Do not delegate a later owner and do not emit the conclusion.\n- An unexpected orchestration failure stops Setup without claiming completion and says what the person can do next.\n\n## Example\n\n`\u002Fhighway-setup`","# highway-setup\n\n## Purpose\n\nSeeds the project's catalogs, then orchestrates Profile, Objectives, Controls, and NFRs in order when the person runs setup.\n\n## When to use\n\n- The person invokes `highway-setup` and `library\u002Fknowledge\u002Fprofile.md` is absent.\n- The person invokes `highway-setup` again after a prior setup run.\n\n## When not to use\n\nDo not collect Profile, Objective, Control, or NFR evidence.\nDo not write Profile, Objective, Control, or NFR records or catalogs.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\nDo not show `Finished` to the person.\n\n## Inputs\n\n- `highway-profile`.\n- `highway-objectives`.\n- `highway-controls`.\n- `highway-nfrs`.\n- `library\u002Fknowledge\u002Fprofile.md` when present.\n- The seeded files' skeletons in `assets\u002F`, one per row of the Seed table.\n- The highway-experience skill, activated first.\n- The person's request to run setup.\n\n## Outputs\n\n- The welcome, once, when Profile has not been written.\n- One domain transition before Objectives, Controls, and NFRs.\n- The closing conclusion, once, after NFRs returns `Finished`.\n- Each seeded file that was absent, written from its asset, such as `requests\u002Frequests.md` from `assets\u002Frequest-catalog.md`.\n\n## Procedure\n\nActivate the highway-experience skill before any output the person sees, and follow it for Highway's identity, the Experience Standard, and the storage contract.\n\nUser-visible interaction follows the Highway Experience Standard.\n\nSeed first. Then delegate each owner in this order: Profile, Objectives, Controls, NFRs. Stay with the current owner until it returns `Finished`. Render that owner's messages as written. Do not answer its question, restate its recommendations, or add a second question.\n\n`Finished` is the only result that advances. Do not show that word. An owner that stops without `Finished` ends Setup. Do not delegate a later owner, and do not emit the conclusion.\n\n### Seed\n\nSeed in every setup run, after the storage contract's mode check and before the welcome.\n\nFor each row below, when the project file is absent, write it from the asset unchanged. Write every absent file as one group. Do not change a file that exists. Emit nothing for this step.\n\n| Asset | Project file |\n|---|---|\n| `assets\u002Frequest-catalog.md` | `requests\u002Frequests.md` |\n| `assets\u002Fdiscovery-catalog.md` | `discoveries\u002Fdiscoveries.md` |\n| `assets\u002Fadr-catalog.md` | `adrs\u002Fadrs.md` |\n| `assets\u002Farchitecture-catalog.md` | `architectures\u002Farchitectures.md` |\n| `assets\u002Fimplementation-catalog.md` | `implementations\u002Fimplementations.md` |\n| `assets\u002Fcapability-catalog.md` | `implementations\u002Fcapabilities.md` |\n| `assets\u002Fcodify-catalog.md` | `code\u002Fcode.md` |\n| `assets\u002Fcodify-integrations.md` | `code\u002Fintegrations.md` |\n| `assets\u002Fcodify-platforms.md` | `library\u002Fcoding-standards\u002Fcodify-platforms.md` |\n| `assets\u002Fcoding-standards-catalog.md` | `library\u002Fcoding-standards\u002Fcoding-standards.md` |\n| `assets\u002Fassessment-findings.md` | `library\u002Fknowledge\u002Fassessment-findings.md` |\n| `assets\u002Fstorage.md` | `library\u002Fknowledge\u002Fstorage.md` |\n\n### Welcome\n\nWhen `library\u002Fknowledge\u002Fprofile.md` is absent, emit the lines below before Profile. Emit \"Welcome to Highway\" as a level-2 heading and \"During setup we'll:\" as a level-3 heading. Emit every other line as written. Do not emit the welcome when that file exists.\n\nWelcome to Highway\n*Turn organizational knowledge into connected decisions.*\n**Your context stays yours.**\n\nHighway builds on information you choose to accept into your repository. Your repository remains the authoritative source of truth, and you retain ownership of the context and artifacts created through Highway.\n\n---\n\nDuring setup we'll:\n\n- **Learn about your organization**, where you'd like to go, how you plan to get there, and what principles guide decisions.\n- **Identify important business outcomes** worth pursuing.\n- **Establish safeguards** that future technology decisions should respect.\n- **Define operational expectations** for how future solutions should behave.\n\nYou don't need to have everything figured out in advance. We'll build this foundation together, and you can refine it over time as your organization evolves.\n\nNow, let's get started.\n\n---\n\nThen delegate `highway-profile`.\n\n### Profile\n\nDelegate `highway-profile`. Profile opens the organization conversation. Do not add a transition before it.\n\nWhen Profile returns `Finished`, emit the Objectives transition and delegate `highway-objectives` in that same moment.\n\n### Objectives\n\n---\n\n**Let's identify some outcomes worth pursuing.**\n\nThese give Highway something concrete to connect future decisions back to.\n\nWhen Objectives returns `Finished`, emit the Controls transition and delegate `highway-controls`.\n\n### Controls\n\n---\n\n**Now let's establish the safeguards that should guide future technology decisions.**\n\nThese help Highway keep future recommendations aligned with what needs to remain true.\n\nWhen Controls returns `Finished`, emit the NFR transition and delegate `highway-nfrs`.\n\n### NFRs\n\n---\n\n**Now let's consider the operational expectations future solutions should meet.**\n\nThese help connect your safeguards to how solutions need to behave in practice.\n\nWhen NFRs returns `Finished`, emit the conclusion.\n\n### Conclusion\n\nEmit this once.\n\n**Your foundational Highway context is now in place.**\n\nHighway now has organizational context, business objectives, safeguards, and operational expectations it can build on in future work.\n\n**Where would you like to go next?**\n\nRun `highway-onboarding` to inform Highway of your current technology landscape. This aids Highway in providing cohesive recommendations.\n\nRun highway-help to explore what Highway can help you do.\n\n## Resume\n\nEvery `highway-setup` run starts at Seed, then Profile. Setup stores no checkpoint. Seeding writes only absent files, so a later run keeps every catalog as it is. When `profile.md` already exists, skip the welcome and still delegate Profile, then Objectives, Controls, and NFRs. Each owner reviews what it already holds before returning `Finished`.\n\n## Verification\n\n- Seeding runs before the welcome in every run.\n- Seeding writes only absent seeded files, each from its asset.\n- Seeding changes no existing file.\n- Seeding emits nothing.\n- Owner order is Profile, Objectives, Controls, NFRs.\n- The welcome is emitted once, and only when `profile.md` is absent.\n- Profile is always delegated.\n- Each later owner is delegated only after the previous owner returns `Finished`.\n- The Objectives, Controls, and NFR transitions are each emitted once, directly before that owner's first message.\n- Setup does not add a question to an owner's message.\n- Setup does not add a synthesis between owners.\n- `Finished` is not shown.\n- An owner that stops without `Finished` ends Setup before the next owner.\n- The conclusion is emitted once, after NFRs returns `Finished`.\n- The conclusion directs the person to `highway-onboarding` before `highway-help`.\n- Setup writes no file other than the seeded files.\n\n## Error Handling\n\n- A seeded file that cannot be written stops Setup before the welcome. Say which file could not be written and what the person can do next.\n- An owner that stops without `Finished` ends Setup. The owner's message is the person's explanation. Do not delegate a later owner and do not emit the conclusion.\n- An unexpected orchestration failure stops Setup without claiming completion and says what the person can do next.\n\n## Example\n\n`\u002Fhighway-setup`",{"name":5,"license":14,"metadata":23,"description":7},{"usage":24,"version":25},"Run highway-setup.","10.4.0","main","40844ce31770431531f69285c7c0b5372161e0f4","highway-agent-plugin\u002Fskills\u002Fhighway-setup","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills","https:\u002F\u002Fgithub.com\u002Fjacob623","2026-11-15 03:33:56",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add jacob623\u002Fhighway-skills --skill highway-setup",{"tool":38,"command":39},"bunx","bunx skills add jacob623\u002Fhighway-skills --skill highway-setup",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jacob623\u002Fhighway-skills --skill highway-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84,88,92],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fadr-catalog.md","ASSET","资产文件",224,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fadr-catalog.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Farchitecture-catalog.md",231,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Farchitecture-catalog.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fassessment-findings.md",239,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fassessment-findings.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Fcapability-catalog.md",135,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fcapability-catalog.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fcodify-catalog.md",198,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fcodify-catalog.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"assets\u002Fcodify-integrations.md",142,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fcodify-integrations.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"assets\u002Fcodify-platforms.md",220,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fcodify-platforms.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"assets\u002Fcoding-standards-catalog.md",381,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fcoding-standards-catalog.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"assets\u002Fdiscovery-catalog.md",173,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fdiscovery-catalog.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fimplementation-catalog.md",266,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fimplementation-catalog.md",{"path":89,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":90,"sourceHtmlUrl":91},"assets\u002Frequest-catalog.md",102,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Frequest-catalog.md",{"path":93,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":94,"sourceHtmlUrl":95},"assets\u002Fstorage.md",23,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-setup\u002Fassets\u002Fstorage.md",[97,104,111,117,123,130],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7C7Z5YQ3BWYB6H1P0ZDY484","valid-skill","A fully conformant fixture skill used only by the tests to validate the authoring framework. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid-skill\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M7C7YQQ3HSFB6DWS47BNYK95","invalid_skill_bad_id","Fixture whose directory name is not kebab-case, to test the id failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid_skill_bad_id\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7C7YJWDD4GWB5VYBXWNBVK0","invalid-skill-undeclared-key","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-undeclared-key\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":18},"01M7C7YFDNBRCDRGSV496BHESC","invalid-skill-short-description","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-short-description\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":18},"01M7C7YB56VE90KD00WMYY84XF","invalid-skill-relative-link","Fixture whose body carries a relative Markdown link target, to test the P8.7 failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-relative-link\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":18},"01M7C7Y6XJ9DXY6KVNYVB1VC7W","invalid-skill-nondeterministic-criterion","Fixture whose decision criteria depend on when they are read, to test the P6.4 failure path. Use when the tests exercise the validator.","https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Finvalid-skill-nondeterministic-criterion\u002FSKILL.md",[],[]]