[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F2820BADMX1S5SQA09TCC2":3,"skill-same:01M7F2820BADMX1S5SQA09TCC2":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F2820BADMX1S5SQA09TCC2","slipway-doctor",null,"Check a static site with slipway doctor after you edit it, read the findings, and fix them until the site reaches its conformance level. Use for any Slipway site or any site that follows the agent-editable site spec.","arminazimi\u002Fslipway","arminazimi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F33401832?v=4","01M7F1ZTKSXGKQGEXS7MJAEB2N","Armin Azimi","01M7F26NCHMY6W6ZZT1YDRNGSV",2,"MIT","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-doctor\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: slipway-doctor\ndescription: Check a static site with slipway doctor after you edit it, read the findings, and fix them until the site reaches its conformance level. Use for any Slipway site or any site that follows the agent-editable site spec.\nmetadata:\n  version: \"0.3.0\"\n---\n\n# Check a site with slipway doctor\n\n`slipway doctor` checks a site's source folder and, when given, its built output against the [agent-editable site spec](https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fspec\u002Fagent-editable\u002F0.1.md). It reports the [conformance level](https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fspec\u002Fagent-editable\u002Flevels.md) the site reaches, L0 to L3, and every finding with its file and line. It works for any generator and never changes a file.\n\nRun it after every edit, before you say the edit is done.\n\n## 1. Run it\n\nUse the `doctor` tool when the Slipway MCP server is registered for the site (the Slipway repository's `packages\u002Fmcp\u002FREADME.md` says how). It takes two optional inputs:\n\n| Input | Meaning |\n| --- | --- |\n| `build` | The built output folder, relative to the site, such as `dist`. Without it, the tests on the output fail. |\n| `level` | The level the site must reach, `L0` to `L3`. Without it, `ok` is true when every MUST test passes. |\n\nOtherwise run the command line from a clone of this repository, after `npm ci`:\n\n```sh\nnode packages\u002Fdoctor\u002Fbin\u002Fslipway.ts doctor \u003Csite> --build \u003Csite>\u002Fdist --format json\n```\n\nAdd `--level L2` (or the level the site's `AGENTS.md` names) to fail below that level. In CI, `--format sarif` writes the findings for GitHub code scanning. Exit code `0` means the target is reached, `1` means findings, and `2` a usage error or a missing folder.\n\nBuild the site first with the engine (`slipway build \u003Csite> --out \u003Csite>\u002Fdist`) when you pass `build`, so the doctor checks the output of your edit and not an old one. The deploy Action runs this check on its build when its `doctor` input is true. Leave `--network` off unless the owner asks: it fetches remote schemas, and no other test needs it.\n\n## 2. Read the report\n\nThe tool returns the JSON report; the command prints it with `--format json`. Read these fields:\n\n- `ok`: the tool's answer to \"is the site done?\". The command's exit code says the same.\n- `level`: the highest level reached, or `null` when an L0 MUST test fails.\n- `findings`: what to fix. Each has the test `id`, `severity`, `message`, and when known `in` (`source` or `output`), `file` (relative to that folder), `line`, `column`, `key`, `allowed`, and `fix`. A finding on a built page already names its source file and line when the site has a source map; `output.file` keeps the built file.\n- `notRun`: tests the doctor did not run. Two are decided by a person; tell the owner, do not mark them as passed.\n\nAn `error` is a failed MUST: it keeps the site below the level. A `warning` is a failed SHOULD or a generator advisory: fix it when the fix is clear, but it never lowers the level.\n\n## 3. Fix and run it again\n\n1. Fix findings in the source. A finding with `in: output` points at a built file the source map does not cover; change the source that produces it, never the built file.\n2. Use `fix` and `allowed` when a finding has them: they name the value the site needs.\n3. Fix errors first, lowest level first: an L0 error hides what L1 and above would report.\n4. Run the doctor again, with the same inputs. Stop when `ok` is true and no new finding appeared.\n\nIf a finding stays after two attempts, stop and report it to the owner with its `id`, file, line, and message.\n\n## Never\n\n- Never lower `level`, drop `build`, or remove a file the doctor reads to get `ok`. That hides findings instead of fixing them.\n- Never edit `spec\u002Fagent-editable\u002Ftests.json`, the schemas, or the doctor itself to make a site pass.\n- Never fix a finding by deleting the content it is about, unless the owner asked for that.\n","# Check a site with slipway doctor\n\n`slipway doctor` checks a site's source folder and, when given, its built output against the [agent-editable site spec](https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fspec\u002Fagent-editable\u002F0.1.md). It reports the [conformance level](https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fspec\u002Fagent-editable\u002Flevels.md) the site reaches, L0 to L3, and every finding with its file and line. It works for any generator and never changes a file.\n\nRun it after every edit, before you say the edit is done.\n\n## 1. Run it\n\nUse the `doctor` tool when the Slipway MCP server is registered for the site (the Slipway repository's `packages\u002Fmcp\u002FREADME.md` says how). It takes two optional inputs:\n\n| Input | Meaning |\n| --- | --- |\n| `build` | The built output folder, relative to the site, such as `dist`. Without it, the tests on the output fail. |\n| `level` | The level the site must reach, `L0` to `L3`. Without it, `ok` is true when every MUST test passes. |\n\nOtherwise run the command line from a clone of this repository, after `npm ci`:\n\n```sh\nnode packages\u002Fdoctor\u002Fbin\u002Fslipway.ts doctor \u003Csite> --build \u003Csite>\u002Fdist --format json\n```\n\nAdd `--level L2` (or the level the site's `AGENTS.md` names) to fail below that level. In CI, `--format sarif` writes the findings for GitHub code scanning. Exit code `0` means the target is reached, `1` means findings, and `2` a usage error or a missing folder.\n\nBuild the site first with the engine (`slipway build \u003Csite> --out \u003Csite>\u002Fdist`) when you pass `build`, so the doctor checks the output of your edit and not an old one. The deploy Action runs this check on its build when its `doctor` input is true. Leave `--network` off unless the owner asks: it fetches remote schemas, and no other test needs it.\n\n## 2. Read the report\n\nThe tool returns the JSON report; the command prints it with `--format json`. Read these fields:\n\n- `ok`: the tool's answer to \"is the site done?\". The command's exit code says the same.\n- `level`: the highest level reached, or `null` when an L0 MUST test fails.\n- `findings`: what to fix. Each has the test `id`, `severity`, `message`, and when known `in` (`source` or `output`), `file` (relative to that folder), `line`, `column`, `key`, `allowed`, and `fix`. A finding on a built page already names its source file and line when the site has a source map; `output.file` keeps the built file.\n- `notRun`: tests the doctor did not run. Two are decided by a person; tell the owner, do not mark them as passed.\n\nAn `error` is a failed MUST: it keeps the site below the level. A `warning` is a failed SHOULD or a generator advisory: fix it when the fix is clear, but it never lowers the level.\n\n## 3. Fix and run it again\n\n1. Fix findings in the source. A finding with `in: output` points at a built file the source map does not cover; change the source that produces it, never the built file.\n2. Use `fix` and `allowed` when a finding has them: they name the value the site needs.\n3. Fix errors first, lowest level first: an L0 error hides what L1 and above would report.\n4. Run the doctor again, with the same inputs. Stop when `ok` is true and no new finding appeared.\n\nIf a finding stays after two attempts, stop and report it to the owner with its `id`, file, line, and message.\n\n## Never\n\n- Never lower `level`, drop `build`, or remove a file the doctor reads to get `ok`. That hides findings instead of fixing them.\n- Never edit `spec\u002Fagent-editable\u002Ftests.json`, the schemas, or the doctor itself to make a site pass.\n- Never fix a finding by deleting the content it is about, unless the owner asked for that.\n",{"name":5,"metadata":24,"description":7},{"version":25},"0.3.0","main","4ace9213edc3d1c6f4c08a1bc4f2f3aebcd70401","skills\u002Fslipway-doctor","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway","https:\u002F\u002Farminazimi.github.io\u002Fslipway\u002F","https:\u002F\u002Fgithub.com\u002Farminazimi","https:\u002F\u002Fvelella.sh","I make codebases confess what they’ve been hiding.","2026-11-11 00:40:10",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add arminazimi\u002Fslipway --skill slipway-doctor",{"tool":41,"command":42},"bunx","bunx skills add arminazimi\u002Fslipway --skill slipway-doctor",{"tool":44,"command":45},"pnpm","pnpm dlx skills add arminazimi\u002Fslipway --skill slipway-doctor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-doctor\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7F28EHG0XQBYM34ECQ1YAWP","slipway-translate","Add a language to a Slipway site, translate pages, and keep every translation linked through lang and translation_key, then check it with slipway check.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-translate\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7F28A1J1XNA5Z5P333SM3MT","slipway-site","Create a Slipway docs site, or customize an existing one through slipway.yml, navigation, languages, redirects, and theme options, then check it with slipway check.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-site\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"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},"01M7F286GG3M7GQ2Q4D7V0J065","slipway-release-notes","Write a changelog entry and a release page from merged pull requests, for a site built with Slipway or for Slipway itself.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-release-notes\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F27YCP18CYDNKSZHZFPMHJ","slipway-design","Restyle a Slipway site with design tokens and a preset, add CSS through the override slots, and keep light and dark contrast passing.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-design\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F27TZM9YAAV5NZPAFBK233","slipway-deploy","Publish a Slipway site to GitHub Pages with the deploy Action, set a custom domain, and fix the common build, base path, theme, and permission failures.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-deploy\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F27Q214435H67M8296E2B2","slipway-content","Write or edit a page on a Slipway site, or translate one into another language, using the engine's front matter keys and directives, then check it with slipway check.","https:\u002F\u002Fgithub.com\u002Farminazimi\u002Fslipway\u002Fblob\u002Fmain\u002Fskills\u002Fslipway-content\u002FSKILL.md",[],[]]