[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C7VBHP9FG8VEBZ1FBSHX71":3,"skill-same:01M7C7VBHP9FG8VEBZ1FBSHX71":52},{"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},"01M7C7VBHP9FG8VEBZ1FBSHX71","highway-profile",null,"Manages the repository-wide organizational Profile and its contextual guidance. Use when highway-setup delegates the Profile, at the start of setup or when setup runs again.","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-profile\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: highway-profile\ndescription: \"Manages the repository-wide organizational Profile and its contextual guidance. Use when highway-setup delegates the Profile, at the start of setup or when setup runs again.\"\nlicense: Apache-2.0\nmetadata:\n  version: 14.5.0\n  usage: \"Run highway-profile.\"\n---\n\n# highway-profile\n\n## Purpose\n\nCollects the organizational Profile when setup delegates this skill.\n\n## When to use\n\n- `highway-setup` delegates this skill at the start of setup.\n- `highway-setup` delegates this skill when setup runs again.\n\n## When not to use\n\nDo not create Controls, NFRs, Objectives, governance rules, or Highway identity.\nDo not treat proposed evidence as organizational fact.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- `library\u002Fknowledge\u002Fprofile.md` when present.\n- `assets\u002Fprofile-record.md`.\n- The highway-experience skill, activated first.\n- Delegation from `highway-setup`.\n- Material the person supplies, including a public website when retrieval is available.\n\n## Outputs\n\nThe complete structure is `assets\u002Fprofile-record.md`.\n\n- An updated `library\u002Fknowledge\u002Fprofile.md` after a review edit.\n- A new `library\u002Fknowledge\u002Fprofile.md` after the guided flow writes it.\n- `Finished` returned to `highway-setup` after review acceptance or a successful guided write.\n- `Finished` is not shown to the person.\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. Repository ownership stays with the person.\n\nX2.21 does not apply. The accepted proposal bullets are the retained domain, so Profile does not show a second capture heading.\n\nEmit only the active template. Follow this order: `review` when `profile.md` exists; otherwise `name`, `offer`, Identity, Vision, Competitive Path, Guiding Principles, then `write`. Follow the Highway Experience Standard for attribution and acceptance wording. Use accepted Organization Name in templates. Use Repository Name until an Organization Name is accepted. Repository Name does not become Organization Name.\n\n### Entry\n\n1. Read `library\u002Fknowledge\u002Fprofile.md` from the repository root.\n2. If `library\u002Fknowledge\u002Fprofile.md` is present and readable, go to `review`.\n3. If that file is absent, go to `name`.\n4. If that file is present and unreadable, stop. Say the Profile could not be read. Leave the file unchanged. Do not return `Finished`.\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, splits, combines, or replaces substance.\n- `accept`: affirms the current block and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: the person asks for an explanation.\n- `decline`: the person explicitly leaves the active domain unresolved.\n\n`unknown` is not `decline`.\n\n### review\n\nShow the file body. Omit frontmatter. Then emit the validation block.\n\n- `edit`: emit one consequence sentence. Rewrite the file with that edit. Preserve every section the person left unchanged. Show the updated body and emit the validation block. Stay on `review`.\n- `accept`: return `Finished`. Emit nothing else.\n- `unknown`: show the body and emit the validation block. Stay on `review`.\n- `question`: answer in one sentence. Show the body and emit the validation block. Stay on `review`.\n\nValidation block:\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so.\n\n### name\n\nEmit:\n\n#### Let's get to know your organization\n\n**What would you like to call your Highway repository?**\n\nUsing your organization's name is often a good choice.\n\nStore the reply as Repository Name. Go to `offer`.\n\n### offer\n\nEmit:\n\n**Do you already have something I can use to start understanding [Repository Name]?**\n\nYou can share a website link, an overview or description, a strategy document, or an assistant export. If you don't have anything handy, say so and we can work through it together.\n\n- The person has nothing: go to `identity.ask`.\n- Text, with or without a link: the text is supplied material for every domain. Store a link in it as Organization URL and retrieve it. When the link cannot be read, say so once and continue with the text. Go to `identity.review` when the material supports at least one Identity finding. Otherwise go to `identity.ask`.\n- A link or document with no other text: retrieve it. Store a supplied link as Organization URL. Go to `identity.review` when it supports at least one Identity finding. Otherwise go to `identity.ask`.\n- A link with no other text, when retrieval is unavailable: go to `identity.ask`. Do not mention the missing retrieval.\n\nFacts from supplied material stay proposed until accepted in that domain's proposal.\n\nUse supplied material across every later domain. Do not ask the person to repeat it. Do not use model memory or prior-agent memory as organizational evidence.\n\n### Domain order\n\nRun Identity, Vision, Competitive Path, then Guiding Principles.\n\nEach domain uses `start` when a proposal can be shown. Identity uses `ask` only when no supported starting point exists. Vision, Competitive Path, and Guiding Principles always use `start`. Do not put a question template in the same message as a starting point.\n\n1. `identity.review` or `identity.ask`\n2. `vision.start`\n3. `path.start`\n4. `principles.start`\n5. `write`\n\nHold each accepted bullet list until `write`. Do not write the file before `write`.\n\n### Shared replies\n\nApply these on every domain step.\n\n- `edit`: emit one sentence stating a consequence the person did not state. Re-emit the same template with the edit applied. Stay.\n- `accept` on `review` or `start`: hold the current bullets. Advance.\n- `accept` on `identity.ask`: hold the answer as the Identity bullets. Advance. Do not emit a capture paragraph.\n- `unknown` on `review` or `start`: re-emit that template. Stay.\n- `unknown` on `identity.ask`: re-emit the question template. Stay.\n- `question`: answer in one sentence. Re-emit the same template. Stay.\n- `decline`: store no narrative for this domain. Advance.\n\n`unknown` does not finish a domain.\n\n### Domain rules\n\nIdentity states who the organization is and what it provides. Omit a technology inventory.\n\nVision states the future the organization is creating. Omit method, sequencing, and organizational approach. When the person supplies those, emit this sentence, hold that material for Competitive Path, and stay on Vision:\n\n**That is an important part of how you will get there. I will carry it forward when we reach Competitive Path, and return to Vision.**\n\nCompetitive Path states the broad approach toward the accepted Vision. Omit Controls, NFRs, safeguards, architecture, implementation requirements, and plans. Keep only the broad strategic meaning of volunteered detail.\n\nGuiding Principles state enduring decision-making values. Do not write an enforceable Control.\n\nOpen Vision, Competitive Path, and Guiding Principles by naming accepted substance from the previous captured domain. Always emit the proposal. Infer a slot, including the Competitive Path tradeoff, from accepted context when the person has not stated it. Do not replace the proposal with a question.\n\n### Templates\n\nIdentity review:\n\nHere's what Highway believes [Name] does.\n\n**[Short activity name]:**\n[One sentence: who receives it, and what they receive.]\n\nEmit 3 to 6 findings. Omit a finding the source does not support.\n\nIdentity question:\n\n**What does [Name] do?**\n\nIf you don't know, say \"I don't know\" and we'll work through it together.\n\nVision opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nWhere you're going\n\nWith [accepted Identity substance], let's explore the future you are working to create.\n\n**Here is a proposed starting point for your Vision:**\n\n- **Future Direction**\n\n  [Inferred from accepted context.]\n\n- **Desired Impact**\n\n  [Inferred from accepted context.]\n\n- **Future State**\n\n  [Inferred from accepted context.]\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nCompetitive Path opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nHow you'll get there\n\nTo advance toward [accepted Vision substance], let's explore how [Name] plans to get there.\n\n**Here is a proposed starting point for your Competitive Path:**\n\n- **Primary Approach**\n\n  [Inferred from accepted context.]\n\n- **Strategic Advantage**\n\n  [Inferred from accepted context.]\n\n- **Important Tradeoff**\n\n  [Inferred from accepted context.]\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nGuiding Principles opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nWhat will guide your decisions\n\nWith your competitive path grounded in [accepted Competitive Path substance], let's explore what principles guide [Name]'s decisions.\n\n**Here is a proposed starting point for your Guiding Principles:**\n\n- **[Short principle name]**\n\n  [Accepted-evidence decision-making value.]\n\nEmit 3 to 5 principles. Infer each principle from accepted context when the person has not stated it. The label is a short principle name.\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nWhen the previous domain was declined, replace the bracketed accepted substance with: Nothing has been accepted for [previous domain] yet.\n\nBold only the question in each block.\n\n### write\n\nWrite `library\u002Fknowledge\u002Fprofile.md` from the repository root once, in the shape required by `assets\u002Fprofile-record.md`. Create `library\u002Fknowledge\u002F` when it is absent.\n\n- A captured domain is `discussed` and its narrative section contains the held bullets. Omit a term the person rejected.\n- A declined domain is `bounded` and its narrative section is omitted.\n- Write `## Context` with Repository Name.\n- Write Organization URL, Organization Name, and Organizational Context only when the person supplied or accepted that value.\n- Emit nothing after a successful write.\n- Return `Finished`.\n\n## Verification\n\n- An existing readable `profile.md` is shown with **What would you add, correct, or remove?**\n- Acceptance of that review returns `Finished` and emits nothing else.\n- A review edit rewrites the file and shows the updated body with the same question.\n- An absent `profile.md` begins at the repository-name template.\n- A starting-point message contains no canonical question.\n- The file is written once, after Guiding Principles is captured or declined.\n- A successful guided write returns `Finished` and emits nothing else.\n- The written file matches `assets\u002Fprofile-record.md`.\n- Setup receives `Finished` and the person does not see that word.\n\n## Error Handling\n\n- An unreadable `profile.md` stops the skill, leaves the file unchanged, and does not return `Finished`.\n- A failed review rewrite leaves the file unchanged, says what failed in terms the person can act on, and stays on `review`.\n- A failed guided write leaves the file absent, says what failed in terms the person can act on, and stays on `write`.\n- Pasted text is supplied material. A link in it that cannot be read is named once, and the skill continues with the text.\n- A link with no other text and no retrieval continues at `identity.ask` without mentioning the missing capability.\n\n## Example\n\n`\u002Fhighway-setup`","# highway-profile\n\n## Purpose\n\nCollects the organizational Profile when setup delegates this skill.\n\n## When to use\n\n- `highway-setup` delegates this skill at the start of setup.\n- `highway-setup` delegates this skill when setup runs again.\n\n## When not to use\n\nDo not create Controls, NFRs, Objectives, governance rules, or Highway identity.\nDo not treat proposed evidence as organizational fact.\nDo not report Status, Summary, Next Action, Blocking Reason, Missing, Complete, or Blocked.\n\n## Inputs\n\n- `library\u002Fknowledge\u002Fprofile.md` when present.\n- `assets\u002Fprofile-record.md`.\n- The highway-experience skill, activated first.\n- Delegation from `highway-setup`.\n- Material the person supplies, including a public website when retrieval is available.\n\n## Outputs\n\nThe complete structure is `assets\u002Fprofile-record.md`.\n\n- An updated `library\u002Fknowledge\u002Fprofile.md` after a review edit.\n- A new `library\u002Fknowledge\u002Fprofile.md` after the guided flow writes it.\n- `Finished` returned to `highway-setup` after review acceptance or a successful guided write.\n- `Finished` is not shown to the person.\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. Repository ownership stays with the person.\n\nX2.21 does not apply. The accepted proposal bullets are the retained domain, so Profile does not show a second capture heading.\n\nEmit only the active template. Follow this order: `review` when `profile.md` exists; otherwise `name`, `offer`, Identity, Vision, Competitive Path, Guiding Principles, then `write`. Follow the Highway Experience Standard for attribution and acceptance wording. Use accepted Organization Name in templates. Use Repository Name until an Organization Name is accepted. Repository Name does not become Organization Name.\n\n### Entry\n\n1. Read `library\u002Fknowledge\u002Fprofile.md` from the repository root.\n2. If `library\u002Fknowledge\u002Fprofile.md` is present and readable, go to `review`.\n3. If that file is absent, go to `name`.\n4. If that file is present and unreadable, stop. Say the Profile could not be read. Leave the file unchanged. Do not return `Finished`.\n\n### Classify\n\nClassify the latest reply before any other action.\n\n- `edit`: adds, removes, corrects, splits, combines, or replaces substance.\n- `accept`: affirms the current block and adds no fact.\n- `unknown`: the person says they do not know.\n- `question`: the person asks for an explanation.\n- `decline`: the person explicitly leaves the active domain unresolved.\n\n`unknown` is not `decline`.\n\n### review\n\nShow the file body. Omit frontmatter. Then emit the validation block.\n\n- `edit`: emit one consequence sentence. Rewrite the file with that edit. Preserve every section the person left unchanged. Show the updated body and emit the validation block. Stay on `review`.\n- `accept`: return `Finished`. Emit nothing else.\n- `unknown`: show the body and emit the validation block. Stay on `review`.\n- `question`: answer in one sentence. Show the body and emit the validation block. Stay on `review`.\n\nValidation block:\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so.\n\n### name\n\nEmit:\n\n#### Let's get to know your organization\n\n**What would you like to call your Highway repository?**\n\nUsing your organization's name is often a good choice.\n\nStore the reply as Repository Name. Go to `offer`.\n\n### offer\n\nEmit:\n\n**Do you already have something I can use to start understanding [Repository Name]?**\n\nYou can share a website link, an overview or description, a strategy document, or an assistant export. If you don't have anything handy, say so and we can work through it together.\n\n- The person has nothing: go to `identity.ask`.\n- Text, with or without a link: the text is supplied material for every domain. Store a link in it as Organization URL and retrieve it. When the link cannot be read, say so once and continue with the text. Go to `identity.review` when the material supports at least one Identity finding. Otherwise go to `identity.ask`.\n- A link or document with no other text: retrieve it. Store a supplied link as Organization URL. Go to `identity.review` when it supports at least one Identity finding. Otherwise go to `identity.ask`.\n- A link with no other text, when retrieval is unavailable: go to `identity.ask`. Do not mention the missing retrieval.\n\nFacts from supplied material stay proposed until accepted in that domain's proposal.\n\nUse supplied material across every later domain. Do not ask the person to repeat it. Do not use model memory or prior-agent memory as organizational evidence.\n\n### Domain order\n\nRun Identity, Vision, Competitive Path, then Guiding Principles.\n\nEach domain uses `start` when a proposal can be shown. Identity uses `ask` only when no supported starting point exists. Vision, Competitive Path, and Guiding Principles always use `start`. Do not put a question template in the same message as a starting point.\n\n1. `identity.review` or `identity.ask`\n2. `vision.start`\n3. `path.start`\n4. `principles.start`\n5. `write`\n\nHold each accepted bullet list until `write`. Do not write the file before `write`.\n\n### Shared replies\n\nApply these on every domain step.\n\n- `edit`: emit one sentence stating a consequence the person did not state. Re-emit the same template with the edit applied. Stay.\n- `accept` on `review` or `start`: hold the current bullets. Advance.\n- `accept` on `identity.ask`: hold the answer as the Identity bullets. Advance. Do not emit a capture paragraph.\n- `unknown` on `review` or `start`: re-emit that template. Stay.\n- `unknown` on `identity.ask`: re-emit the question template. Stay.\n- `question`: answer in one sentence. Re-emit the same template. Stay.\n- `decline`: store no narrative for this domain. Advance.\n\n`unknown` does not finish a domain.\n\n### Domain rules\n\nIdentity states who the organization is and what it provides. Omit a technology inventory.\n\nVision states the future the organization is creating. Omit method, sequencing, and organizational approach. When the person supplies those, emit this sentence, hold that material for Competitive Path, and stay on Vision:\n\n**That is an important part of how you will get there. I will carry it forward when we reach Competitive Path, and return to Vision.**\n\nCompetitive Path states the broad approach toward the accepted Vision. Omit Controls, NFRs, safeguards, architecture, implementation requirements, and plans. Keep only the broad strategic meaning of volunteered detail.\n\nGuiding Principles state enduring decision-making values. Do not write an enforceable Control.\n\nOpen Vision, Competitive Path, and Guiding Principles by naming accepted substance from the previous captured domain. Always emit the proposal. Infer a slot, including the Competitive Path tradeoff, from accepted context when the person has not stated it. Do not replace the proposal with a question.\n\n### Templates\n\nIdentity review:\n\nHere's what Highway believes [Name] does.\n\n**[Short activity name]:**\n[One sentence: who receives it, and what they receive.]\n\nEmit 3 to 6 findings. Omit a finding the source does not support.\n\nIdentity question:\n\n**What does [Name] do?**\n\nIf you don't know, say \"I don't know\" and we'll work through it together.\n\nVision opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nWhere you're going\n\nWith [accepted Identity substance], let's explore the future you are working to create.\n\n**Here is a proposed starting point for your Vision:**\n\n- **Future Direction**\n\n  [Inferred from accepted context.]\n\n- **Desired Impact**\n\n  [Inferred from accepted context.]\n\n- **Future State**\n\n  [Inferred from accepted context.]\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nCompetitive Path opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nHow you'll get there\n\nTo advance toward [accepted Vision substance], let's explore how [Name] plans to get there.\n\n**Here is a proposed starting point for your Competitive Path:**\n\n- **Primary Approach**\n\n  [Inferred from accepted context.]\n\n- **Strategic Advantage**\n\n  [Inferred from accepted context.]\n\n- **Important Tradeoff**\n\n  [Inferred from accepted context.]\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nGuiding Principles opening and starting point:\n\nEmit this level-3 heading, then the sentence under it:\n\nWhat will guide your decisions\n\nWith your competitive path grounded in [accepted Competitive Path substance], let's explore what principles guide [Name]'s decisions.\n\n**Here is a proposed starting point for your Guiding Principles:**\n\n- **[Short principle name]**\n\n  [Accepted-evidence decision-making value.]\n\nEmit 3 to 5 principles. Infer each principle from accepted context when the person has not stated it. The label is a short principle name.\n\n**What would you add, correct, or remove?**\n\nIf this is accurate, just say so. If you don't know, say \"I don't know\" and we'll work through it together.\n\nWhen the previous domain was declined, replace the bracketed accepted substance with: Nothing has been accepted for [previous domain] yet.\n\nBold only the question in each block.\n\n### write\n\nWrite `library\u002Fknowledge\u002Fprofile.md` from the repository root once, in the shape required by `assets\u002Fprofile-record.md`. Create `library\u002Fknowledge\u002F` when it is absent.\n\n- A captured domain is `discussed` and its narrative section contains the held bullets. Omit a term the person rejected.\n- A declined domain is `bounded` and its narrative section is omitted.\n- Write `## Context` with Repository Name.\n- Write Organization URL, Organization Name, and Organizational Context only when the person supplied or accepted that value.\n- Emit nothing after a successful write.\n- Return `Finished`.\n\n## Verification\n\n- An existing readable `profile.md` is shown with **What would you add, correct, or remove?**\n- Acceptance of that review returns `Finished` and emits nothing else.\n- A review edit rewrites the file and shows the updated body with the same question.\n- An absent `profile.md` begins at the repository-name template.\n- A starting-point message contains no canonical question.\n- The file is written once, after Guiding Principles is captured or declined.\n- A successful guided write returns `Finished` and emits nothing else.\n- The written file matches `assets\u002Fprofile-record.md`.\n- Setup receives `Finished` and the person does not see that word.\n\n## Error Handling\n\n- An unreadable `profile.md` stops the skill, leaves the file unchanged, and does not return `Finished`.\n- A failed review rewrite leaves the file unchanged, says what failed in terms the person can act on, and stays on `review`.\n- A failed guided write leaves the file absent, says what failed in terms the person can act on, and stays on `write`.\n- Pasted text is supplied material. A link in it that cannot be read is named once, and the skill continues with the text.\n- A link with no other text and no retrieval continues at `identity.ask` without mentioning the missing capability.\n\n## Example\n\n`\u002Fhighway-setup`",{"name":5,"license":14,"metadata":23,"description":7},{"usage":24,"version":25},"Run highway-profile.","14.5.0","main","40844ce31770431531f69285c7c0b5372161e0f4","highway-agent-plugin\u002Fskills\u002Fhighway-profile","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-profile",{"tool":38,"command":39},"bunx","bunx skills add jacob623\u002Fhighway-skills --skill highway-profile",{"tool":41,"command":42},"pnpm","pnpm dlx skills add jacob623\u002Fhighway-skills --skill highway-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-profile\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"assets\u002Fprofile-record.md","ASSET","资产文件",2926,"https:\u002F\u002Fgithub.com\u002Fjacob623\u002Fhighway-skills\u002Fblob\u002Fmain\u002Fhighway-agent-plugin\u002Fskills\u002Fhighway-profile\u002Fassets\u002Fprofile-record.md",[53,60,67,73,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"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":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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",[],[]]