[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C7T7JVTSAZ9350X9M20P3W":3,"skill-same:01M7C7T7JVTSAZ9350X9M20P3W":62},{"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},"01M7C7T7JVTSAZ9350X9M20P3W","highway-architecture",null,"Manages one reference architecture from one accepted adr. Use when an ADR is accepted and the person wants the reference architecture that realizes it, or when highway-onboarding hands off an accepted ADR.","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-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: highway-architecture\ndescription: \"Manages one reference architecture from one accepted adr. Use when an ADR is accepted and the person wants the reference architecture that realizes it, or when highway-onboarding hands off an accepted ADR.\"\nlicense: Apache-2.0\nmetadata:\n  version: 5.8.0\n  usage: \"Run highway-architecture with one adr id.\"\n---\n\n# highway-architecture\n\n## Purpose\n\nCreates one proposed Reference Architecture from an accepted ADR after the person accepts the proposed architecture.\n\n## When to use\n\n- The person invokes `highway-architecture` with one ADR id.\n- The person invokes `highway-architecture` without an ADR id.\n- `highway-onboarding` hands off an accepted ADR id.\n\n## When not to use\n\nDo not select an ADR by recency, filename, or batch.\nDo not use an ADR whose status is not `accepted`.\nDo not change the Discovery, Request, Profile, Objectives, Controls, or NFRs.\nDo not change the ADR or its catalog row, except its Reference Architecture field and its Architecture ID.\nDo not select a different ADR alternative.\nDo not create a Reference Implementation or authorize implementation.\nDo not create capability records or capability ids.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- One ADR id that matches one row in `adrs\u002Fadrs.md`, when the person supplies one.\n- `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md`.\n- The accepted ADR at `adrs\u002F[ID].md`.\n- Accepted Profile, Objectives, Controls, and NFRs when present.\n- `architectures\u002Farchitectures.md` and `architectures\u002FRA*.md` when present.\n- `assets\u002Farchitecture-record.md`.\n- `highway-implementation`.\n- The highway-experience skill, activated first.\n\n## Outputs\n\nThe complete structure is `assets\u002Farchitecture-record.md`. `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md` keep the structure highway-setup seeded.\n\n- One architecture record at `architectures\u002F[ID].md` after the person accepts the proposed architecture, or when `highway-onboarding` hands off an accepted ADR id.\n- An updated `architectures\u002Farchitectures.md` written with that record.\n- The ADR's Reference Architecture field set to that architecture id, and the ADR's Architecture ID in `adrs\u002Fadrs.md` set to the same id.\n- A closing message that names the architecture and the implementation command.\n- No architecture when the ADR is missing, not accepted, or a write fails.\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\nBefore the first question, confirm these seeded files exist: `adrs\u002Fadrs.md`, `architectures\u002Farchitectures.md`.\nWhen any is absent, emit the message below exactly, stop, and write nothing.\n\n**Oops... we need to setup your repository.**\n\nHighway needs to gather your organizational preferences and set up your repository. Run highway-setup to get started.\n\nEmit only the active template. Follow this order: `onboarding` when `highway-onboarding` hands off an accepted ADR id; `choose` when no ADR id is supplied; otherwise `start`, then `identifier`, `title` when needed, `write`, `name`, and `close`. The ADR remains the decision. Inherit its decision, rationale, alternatives, consequences, and constraints without changing their meaning. Describe the architecture in conceptual terms. A platform, product, vendor, or specific technology stays in the inherited decision and is not part of the architecture. A missing Profile, Objective, Control, or NFR continues without invented evidence. A malformed one of those baselines stops the skill and writes nothing.\n\nOne accepted ADR produces at most one architecture. When the architecture catalog already has that ADR as Parent, show the recorded architecture and write no second one.\n\nBefore a step in this table, read its file and follow it to the end.\n\n| File | Steps |\n| --- | --- |\n| `references\u002Fproposal.md` | `start` |\n| `references\u002Frecord.md` | `identifier`, `title`, `write`, `name` |\n\n### Entry\n\nWhen `highway-onboarding` hands off an accepted ADR id, go to `onboarding`.\n\n1. Read the invocation for one ADR id. When it has no ADR id and contains the exact title of one waiting ADR, as `choose` defines it, that ADR's id is present. Compare without regard to case.\n2. When none is present, go to `choose`.\n3. When an ADR id is present, resolve it. When it matches no ADR, stop. Say the ADR was not found. Write nothing.\n4. When that ADR status is not `accepted`, stop. Say the ADR is not accepted. Write nothing.\n5. When the ADR's Reference Architecture field names an RA id, show that architecture and write nothing.\n6. When that ADR already appears in an architecture catalog ADR ID cell, show the recorded architecture. When the ADR's Reference Architecture field is still `None`, go to `name`. Otherwise write nothing.\n7. Otherwise go to `start`. Create an architecture only when the accepted ADR names none.\n\n### choose\n\nRead `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md`. An ADR is waiting when its Status is `accepted`, its Architecture ID column is `None`, and its ADR ID does not appear as a whole id in any architecture catalog ADR ID cell. A removed architecture row still counts as that ADR already having an architecture. Do not open ADR records to build this list.\n\nWhen none are waiting, say that no ADR is waiting for a Reference Architecture. Write nothing.\n\nOtherwise emit one numbered line per waiting ADR, starting at 1, in ADR catalog order. Show the ADR ID and its title. A stated number selects that ADR.\n\n**1. [ADR ID]:** [ADR Title]\n\n**Which ADR would you like to turn into a Reference Architecture?**\n\n- An ADR id, a listed ADR title, or its number: follow Entry from case 3.\n- `unknown`: re-emit this list. Stay on `choose`.\n- `decline`: stop. Write nothing.\n\n### onboarding\n\n`highway-onboarding` hands off one accepted ADR id. Write the architecture as accepted without asking the person, except for the questions in step 4. Emit nothing else.\n\n1. Resolve the ADR as Entry does from case 3. When Entry would stop, return to `highway-onboarding` and say why.\n2. When the ADR's Reference Architecture field names an `RA` id, return that id to `highway-onboarding`. Write nothing. When the ADR already appears in an architecture catalog ADR ID cell and its field is still `None`, follow `name` for that architecture, then return its id.\n3. Build the architecture as `start` does, without emitting it. Current Decisions is this ADR. Do not write Key Technologies. Do not copy the decision statement. Do not ask whether a decision replaces or runs beside another.\n4. Derive the title and the id as `identifier` does. Ask only these: the purpose question, when `identifier` would ask it; the `title` message, when `identifier` would go to `title`. Write nothing until the person gives a usable title. A `decline` writes nothing and returns to `highway-onboarding` without an architecture.\n5. When `identifier` reuses the existing record, go to step 6. Otherwise write as `write` does. The catalog ADR ID cell is this ADR id. A failed write leaves every existing architecture byte unchanged. Return to `highway-onboarding` and say the architecture could not be written.\n6. Follow `name`. Do not go to `close`. Return the `RA` id to `highway-onboarding`. When the ADR could not be updated, say so with the id.\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, or replaces architecture text.\n- `accept`: affirms the proposed architecture and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: asks for an explanation.\n- `decline`: the person stops or cancels.\n\nOn `start`, \"looks good\" is `accept`.\n\n### close\n\n**Reference Architecture accepted**\n\n- **Architecture record:** `architectures\u002F[RA id].md`\n- **Title:** [Title]\n- **Identifier:** `[RA id]`\n- **ADR:** `[ADR id]`\n\nRun `highway-implementation [RA id]` to create the Reference Implementation.\n\n## Verification\n\n- An ADR id for an accepted ADR opens the proposed architecture.\n- An invocation without an ADR id lists the accepted ADRs whose ADR ID is absent from every architecture catalog row. Each line shows the ADR ID and its title. The list is numbered. A stated number selects that ADR. A removed architecture row keeps that ADR off the list.\n- One accepted ADR produces at most one architecture.\n- The proposed architecture is accepted before the record is written.\n- The architecture does not change the ADR decision.\n- The architecture remains conceptual. It names no platform, product, vendor, or specific technology. It has no Key Technologies section.\n- The record identifier is an `RA` id. The record status is `accepted` after the person accepts the architecture. It does not use an `ARCH` identifier or status `proposed`.\n- Context states when the architecture applies and what it leaves open. The style states why it was chosen.\n- Variation, Responsibilities, Information, and each component's responsibility and interface are in the record.\n- Relationship lines use `advances`, `bound by`, and `satisfies`, or `None`.\n- Required capabilities name their component, follow the capability title rule, and have no capability ids.\n- Implementation is not authorized.\n- The closing message names `highway-implementation [RA id]`.\n- The skill creates no Reference Implementation.\n- A handoff from `highway-onboarding` writes an accepted architecture without a proposal, names it on the ADR and in the ADR catalog, and returns its `RA` id. It asks only the purpose question or the title message, when the title cannot be used. A `decline` writes nothing.\n\n## Error Handling\n\n- A missing or unknown ADR stops the skill and writes nothing.\n- An ADR that is not accepted stops the skill and writes nothing.\n- A second architecture for the same ADR stops the write and shows the existing architecture.\n- A malformed present Profile, Objective, Control, or NFR baseline stops the skill and writes nothing.\n- A failed write leaves existing architecture and catalog bytes unchanged.\n- A failed ADR update keeps the architecture, says the ADR could not be updated, and does not call the chain complete.\n\n## Example\n\n`\u002Fhighway-architecture ADRb7c41e20`","# highway-architecture\n\n## Purpose\n\nCreates one proposed Reference Architecture from an accepted ADR after the person accepts the proposed architecture.\n\n## When to use\n\n- The person invokes `highway-architecture` with one ADR id.\n- The person invokes `highway-architecture` without an ADR id.\n- `highway-onboarding` hands off an accepted ADR id.\n\n## When not to use\n\nDo not select an ADR by recency, filename, or batch.\nDo not use an ADR whose status is not `accepted`.\nDo not change the Discovery, Request, Profile, Objectives, Controls, or NFRs.\nDo not change the ADR or its catalog row, except its Reference Architecture field and its Architecture ID.\nDo not select a different ADR alternative.\nDo not create a Reference Implementation or authorize implementation.\nDo not create capability records or capability ids.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- One ADR id that matches one row in `adrs\u002Fadrs.md`, when the person supplies one.\n- `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md`.\n- The accepted ADR at `adrs\u002F[ID].md`.\n- Accepted Profile, Objectives, Controls, and NFRs when present.\n- `architectures\u002Farchitectures.md` and `architectures\u002FRA*.md` when present.\n- `assets\u002Farchitecture-record.md`.\n- `highway-implementation`.\n- The highway-experience skill, activated first.\n\n## Outputs\n\nThe complete structure is `assets\u002Farchitecture-record.md`. `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md` keep the structure highway-setup seeded.\n\n- One architecture record at `architectures\u002F[ID].md` after the person accepts the proposed architecture, or when `highway-onboarding` hands off an accepted ADR id.\n- An updated `architectures\u002Farchitectures.md` written with that record.\n- The ADR's Reference Architecture field set to that architecture id, and the ADR's Architecture ID in `adrs\u002Fadrs.md` set to the same id.\n- A closing message that names the architecture and the implementation command.\n- No architecture when the ADR is missing, not accepted, or a write fails.\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\nBefore the first question, confirm these seeded files exist: `adrs\u002Fadrs.md`, `architectures\u002Farchitectures.md`.\nWhen any is absent, emit the message below exactly, stop, and write nothing.\n\n**Oops... we need to setup your repository.**\n\nHighway needs to gather your organizational preferences and set up your repository. Run highway-setup to get started.\n\nEmit only the active template. Follow this order: `onboarding` when `highway-onboarding` hands off an accepted ADR id; `choose` when no ADR id is supplied; otherwise `start`, then `identifier`, `title` when needed, `write`, `name`, and `close`. The ADR remains the decision. Inherit its decision, rationale, alternatives, consequences, and constraints without changing their meaning. Describe the architecture in conceptual terms. A platform, product, vendor, or specific technology stays in the inherited decision and is not part of the architecture. A missing Profile, Objective, Control, or NFR continues without invented evidence. A malformed one of those baselines stops the skill and writes nothing.\n\nOne accepted ADR produces at most one architecture. When the architecture catalog already has that ADR as Parent, show the recorded architecture and write no second one.\n\nBefore a step in this table, read its file and follow it to the end.\n\n| File | Steps |\n| --- | --- |\n| `references\u002Fproposal.md` | `start` |\n| `references\u002Frecord.md` | `identifier`, `title`, `write`, `name` |\n\n### Entry\n\nWhen `highway-onboarding` hands off an accepted ADR id, go to `onboarding`.\n\n1. Read the invocation for one ADR id. When it has no ADR id and contains the exact title of one waiting ADR, as `choose` defines it, that ADR's id is present. Compare without regard to case.\n2. When none is present, go to `choose`.\n3. When an ADR id is present, resolve it. When it matches no ADR, stop. Say the ADR was not found. Write nothing.\n4. When that ADR status is not `accepted`, stop. Say the ADR is not accepted. Write nothing.\n5. When the ADR's Reference Architecture field names an RA id, show that architecture and write nothing.\n6. When that ADR already appears in an architecture catalog ADR ID cell, show the recorded architecture. When the ADR's Reference Architecture field is still `None`, go to `name`. Otherwise write nothing.\n7. Otherwise go to `start`. Create an architecture only when the accepted ADR names none.\n\n### choose\n\nRead `adrs\u002Fadrs.md` and `architectures\u002Farchitectures.md`. An ADR is waiting when its Status is `accepted`, its Architecture ID column is `None`, and its ADR ID does not appear as a whole id in any architecture catalog ADR ID cell. A removed architecture row still counts as that ADR already having an architecture. Do not open ADR records to build this list.\n\nWhen none are waiting, say that no ADR is waiting for a Reference Architecture. Write nothing.\n\nOtherwise emit one numbered line per waiting ADR, starting at 1, in ADR catalog order. Show the ADR ID and its title. A stated number selects that ADR.\n\n**1. [ADR ID]:** [ADR Title]\n\n**Which ADR would you like to turn into a Reference Architecture?**\n\n- An ADR id, a listed ADR title, or its number: follow Entry from case 3.\n- `unknown`: re-emit this list. Stay on `choose`.\n- `decline`: stop. Write nothing.\n\n### onboarding\n\n`highway-onboarding` hands off one accepted ADR id. Write the architecture as accepted without asking the person, except for the questions in step 4. Emit nothing else.\n\n1. Resolve the ADR as Entry does from case 3. When Entry would stop, return to `highway-onboarding` and say why.\n2. When the ADR's Reference Architecture field names an `RA` id, return that id to `highway-onboarding`. Write nothing. When the ADR already appears in an architecture catalog ADR ID cell and its field is still `None`, follow `name` for that architecture, then return its id.\n3. Build the architecture as `start` does, without emitting it. Current Decisions is this ADR. Do not write Key Technologies. Do not copy the decision statement. Do not ask whether a decision replaces or runs beside another.\n4. Derive the title and the id as `identifier` does. Ask only these: the purpose question, when `identifier` would ask it; the `title` message, when `identifier` would go to `title`. Write nothing until the person gives a usable title. A `decline` writes nothing and returns to `highway-onboarding` without an architecture.\n5. When `identifier` reuses the existing record, go to step 6. Otherwise write as `write` does. The catalog ADR ID cell is this ADR id. A failed write leaves every existing architecture byte unchanged. Return to `highway-onboarding` and say the architecture could not be written.\n6. Follow `name`. Do not go to `close`. Return the `RA` id to `highway-onboarding`. When the ADR could not be updated, say so with the id.\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, or replaces architecture text.\n- `accept`: affirms the proposed architecture and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: asks for an explanation.\n- `decline`: the person stops or cancels.\n\nOn `start`, \"looks good\" is `accept`.\n\n### close\n\n**Reference Architecture accepted**\n\n- **Architecture record:** `architectures\u002F[RA id].md`\n- **Title:** [Title]\n- **Identifier:** `[RA id]`\n- **ADR:** `[ADR id]`\n\nRun `highway-implementation [RA id]` to create the Reference Implementation.\n\n## Verification\n\n- An ADR id for an accepted ADR opens the proposed architecture.\n- An invocation without an ADR id lists the accepted ADRs whose ADR ID is absent from every architecture catalog row. Each line shows the ADR ID and its title. The list is numbered. A stated number selects that ADR. A removed architecture row keeps that ADR off the list.\n- One accepted ADR produces at most one architecture.\n- The proposed architecture is accepted before the record is written.\n- The architecture does not change the ADR decision.\n- The architecture remains conceptual. It names no platform, product, vendor, or specific technology. It has no Key Technologies section.\n- The record identifier is an `RA` id. The record status is `accepted` after the person accepts the architecture. It does not use an `ARCH` identifier or status `proposed`.\n- Context states when the architecture applies and what it leaves open. The style states why it was chosen.\n- Variation, Responsibilities, Information, and each component's responsibility and interface are in the record.\n- Relationship lines use `advances`, `bound by`, and `satisfies`, or `None`.\n- Required capabilities name their component, follow the capability title rule, and have no capability ids.\n- Implementation is not authorized.\n- The closing message names `highway-implementation [RA id]`.\n- The skill creates no Reference Implementation.\n- A handoff from `highway-onboarding` writes an accepted architecture without a proposal, names it on the ADR and in the ADR catalog, and returns its `RA` id. It asks only the purpose question or the title message, when the title cannot be used. A `decline` writes nothing.\n\n## Error Handling\n\n- A missing or unknown ADR stops the skill and writes nothing.\n- An ADR that is not accepted stops the skill and writes nothing.\n- A second architecture for the same ADR stops the write and shows the existing architecture.\n- A malformed present Profile, Objective, Control, or NFR baseline stops the skill and writes nothing.\n- A failed write leaves existing architecture and catalog bytes unchanged.\n- A failed ADR update keeps the architecture, says the ADR could not be updated, and does not call the chain complete.\n\n## Example\n\n`\u002Fhighway-architecture ADRb7c41e20`",{"name":5,"license":14,"metadata":23,"description":7},{"usage":24,"version":25},"Run highway-architecture with one adr id.","5.8.0","main","40844ce31770431531f69285c7c0b5372161e0f4","highway-agent-plugin\u002Fskills\u002Fhighway-architecture","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-architecture",{"tool":38,"command":39},"bunx","bunx skills add jacob623\u002Fhighway-skills --skill highway-architecture",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jacob623\u002Fhighway-skills --skill highway-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-architecture\u002FSKILL.md",true,[46,52,58],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Farchitecture-record.md","ASSET","资产文件",2971,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-architecture\u002Fassets\u002Farchitecture-record.md",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fproposal.md","REFERENCE","参考文档",2468,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-architecture\u002Freferences\u002Fproposal.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Frecord.md",8702,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-architecture\u002Freferences\u002Frecord.md",[63,70,77,83,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"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":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[]]