[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DAPG2NR1DF979WVPVCVTEY":3,"skill-same:01M7DAPG2NR1DF979WVPVCVTEY":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7DAPG2NR1DF979WVPVCVTEY","docs-rules-check",null,"Review documents under docs\u002F and the Lorecraft specs in docs\u002F__meta__\u002F that govern them - run lorecraft check for frontmatter, section outline, word caps and token budget, walk each spec's checklist for what a machine cannot decide, and check that each changed spec loads, that its prose and JSON agree, and that it governs the documents intended. Use after editing anything under docs\u002F, when reviewing a pull request that touches docs\u002F, before committing, when lorecraft check exits 1 or 2, or a document is unexpectedly ungoverned, or when setting the checks up in CI. Not for writing documents or specs; see \u002Fdocs-rules and \u002Fdocs-rules-creator","LNSD\u002Florecraft","LNSD","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F3949095?v=4","01M7DAK7ETP75C8S8PT783SWSP","Lorenzo Delgado","01M7DAK7FBVXE30743ZG437MTN",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fskills\u002Fdocs-rules-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: docs-rules-check\ndescription: Review documents under docs\u002F and the Lorecraft specs in docs\u002F__meta__\u002F that govern them - run lorecraft check for frontmatter, section outline, word caps and token budget, walk each spec's checklist for what a machine cannot decide, and check that each changed spec loads, that its prose and JSON agree, and that it governs the documents intended. Use after editing anything under docs\u002F, when reviewing a pull request that touches docs\u002F, before committing, when lorecraft check exits 1 or 2, or a document is unexpectedly ungoverned, or when setting the checks up in CI. Not for writing documents or specs; see \u002Fdocs-rules and \u002Fdocs-rules-creator\ncompatibility: Requires the lorecraft command, on PATH or run through uvx lorecraft, or uv run lorecraft in a uv project that declares Lorecraft as a dependency, and a git checkout\nallowed-tools: Bash(lorecraft check*) Bash(lorecraft inspect*) Bash(uvx lorecraft *) Bash(uv run lorecraft *) Bash(git diff *) Bash(git status *) Bash(git merge-base *) Bash(grep *) Bash(ls docs\u002F*)\n---\n\n# Docs Rules Check\n\nThe review pass over `docs\u002F`. For a changed document it verifies that the document follows the specs\nin `docs\u002F__meta__\u002F` that govern it; for a changed spec, that it loads, agrees with itself, and governs\nwhat it claims to. This is a **conformance check, not a review of content**: it does not question whether a\nconvention is the right one, or whether the code a document describes works.\n\nThis skill carries no per-corpus conventions. It resolves the specs from each document's path and validates\nagainst them. It reports; the fixes belong to the writing paths — `\u002Fdocs-rules` for a document,\n`\u002Fdocs-rules-creator` for a spec.\n\n## Running lorecraft\n\nEvery command below calls `lorecraft` directly. Where it is not on `PATH`, run `uvx lorecraft …` instead, or\n`uv run lorecraft …` in a uv project that declares Lorecraft as a dependency. Run from the repository root.\n\n## 1. The changeset\n\n```bash\ngit status --short -- docs                                     # uncommitted work, the default\ngit diff --name-only \"$(git merge-base HEAD main)\"...HEAD -- docs   # a whole branch\n```\n\nGiven explicit paths, check those instead. Split what changed in two:\n\n- **Documents** — every changed Markdown file outside `docs\u002F__meta__\u002F`. §2 to §5 check them.\n- **Specs** — every changed file in `docs\u002F__meta__\u002F`. A change to any file at a spec name is\n  a change to that spec: its prose and every JSON file beside it. §6 checks them.\n\n## 2. The specs that govern each document\n\n```bash\nlorecraft inspect\n```\n\nEach document is followed by the names of the specs governing it, broad to narrow; the name `\u003Cname>` is the\nprose at `docs\u002F__meta__\u002F\u003Cname>.md`.\n[cli-inspect](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-inspect.md) describes the output. Read every\nspec listed for a document **before** the document, so its checklist is in hand while reading. A document can\nbe governed for one part and not another;\n[check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#key-concepts) says what governs each part.\nReport a document as unvalidated for a part nothing governs, rather than borrowing another corpus's conventions.\n\n## 3. Run the checks\n\nThe checks decide every mechanical requirement — required and allowed frontmatter fields, their vocabularies and\npatterns, `name` against the filename, the title, section order, empty and forbidden sections, word caps and the\ntoken budget. Do not check those by hand.\n\n```bash\nlorecraft check                              # every rule over every document and skill, one read of the tree\nlorecraft check --format json                # machine-readable\n```\n\nThe run covers the whole workspace; read the diagnostics for the documents the change touches. A diagnostic prints as\n`path:line: severity[CODE]: message`, and may be followed by `-->`, `= help:` and `= note:` lines, or `labels` and\n`children` in JSON; for a missing section they say what it holds and show a sample, so read them before fixing it.\nExit `0` means no error, warnings included, `1` at least one error, a spec that cannot be loaded included — §6 covers that one — and `2` invalid input or\nselectors, or that the root or `docs\u002F__meta__\u002F` cannot be listed. A `\u003Cpath>: ungoverned for \u003Cparts>` line on stderr is not a\nfailure; report the document as unvalidated for those parts. The rule groups and their codes, `LC2xx` frontmatter, `LC3xx`\noutline, `LC4xx` length, `LC5xx` links, are listed in\n[check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#findings).\n\nThe run checks every agent skill too. A diagnostic at a skill's path, or an `LC1xx` one, is about a skill, not a\ndocument, and falls outside this review.\n\nA word cap or budget diagnostic on a section the change added to blocks, like any other error. One on a section\nthe change did not touch is pre-existing: report it as such. The fix for an overage is to move or cut, never to\ncompress.\n\n## 4. Walk the checklist\n\n**A spec's checklist is the check surface for what the commands cannot decide**: whether a section\nsays what the spec asks of it, cross-reference direction, whether a `description` genuinely helps a\nreader find the document. Walk each item against each changed document, and each namespace layer's checklist\ntoo. Where a spec has no checklist, walk its requirements instead.\n\nCheck only what the changeset touches — an unchanged document breaking a requirement is not this changeset's finding.\nThe one exception is §5.\n\n## 5. Hunt for inventories that will rot\n\nA list of files inside a document is a second source of truth nothing keeps honest. **Flag every one, whether\nor not the changeset introduced it**: a table or list whose entries are documents, a \"see also\" naming each\nsibling, a count (\"the four principle documents\"). For each, report the derivation that should replace it: the\ncorpus directory, a naming convention, or `lorecraft inspect`. A references section naming what a document\ndepends on is not a finding. Where a list survives for a stated reason, compare it with `ls docs\u002F\u003Ccorpus>\u002F`; a\nlist already out of sync is a finding.\n\n## 6. Changed specs\n\nLorecraft loads and validates each JSON file on its own, but it cannot tell whether the JSON says what the\nprose says, or whether a spec name governs the documents its author meant. Check each changed\nspec for both.\n\n**Load.** `lorecraft inspect` validates every spec before any document is read. A structure file\nmust use only the dialect's keys and state usable values, and its `frontmatter` key must satisfy the JSON Schema Draft\n2020-12 meta-schema, state `\"type\": \"object\"` at its root, and carry no `$id` at any depth. A leftover\n`\u003Cname>.header.json` is not read: its schema belongs in that key now. A file that fails stops the run with an error\nnaming it: `inspect` exits `2`, and `lorecraft check` reports it as an error diagnostic and exits `1`. That error is the finding;\n[spec-structure](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure.md) says what is refused for any\nfile, and [spec-structure-outline](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-outline.md),\n[spec-structure-budget](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-budget.md) and\n[spec-structure-frontmatter](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-frontmatter.md) what\nis refused for their keys.\n\n**Resolution.** In the `inspect` tree, compare what is governed with what was meant.\n[spec](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec.md) states how a path selects its specs.\n\n- Each changed spec appears under its corpus. A file whose name does not parse — a hyphen in a corpus name, a\n  dot in a spec name, a `\u003Cname>.\u003Ctoken>.json` that no file type's pattern claims — is left out silently, and\n  so is a namespace spec whose corpus has no file of its own or no directory under `docs\u002F`.\n- Each document lists the spec names intended. A namespace matches a filename that equals it or continues it\n  with a hyphen: `code-python` governs `python-typing.md`, not `pythonic.md`.\n- A namespace spec matches at least one document. One that matches none still loads and governs nothing,\n  usually after a rename.\n- For each part the corpus means to govern, the documents meant are governed, as\n  [check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#key-concepts) defines it. A namespace\n  file never governs alone: the checks read it only once the corpus spec has a structure file, and its\n  `frontmatter` only once that file states the key.\n\n**Agreement.** Nothing detects drift between a spec's prose and its JSON, so read both:\n\n- Frontmatter: every frontmatter field the prose describes is in the `frontmatter` schema's `properties`, and\n  none is only in the schema; required fields, vocabularies and patterns match the prose's wording.\n- Structure: the prose's section list, order, and optional sections match `outline`; any word cap, token\n  budget, forbidden section or empty-section requirement in one is in the other, with the same number.\n- Layering: a namespace file states only what it adds, and does not restate or contradict its base. A\n  namespace written as though it could relax a corpus requirement is a finding.\n- Direction: the base names none of its extensions, in prose, `description`, or references.\n- A checklist: the prose ends with checklist items for the requirements no JSON file holds, since those are checked by\n  reading or not at all.\n\n**Consequence.** Run `lorecraft check`. A spec change that breaks existing documents must fix them in the same\nchange, or say why they are left: a finding the changed spec introduced belongs to this changeset.\n\n## 7. Report\n\nClean:\n\n> Docs rules check clean. Applied: `docs\u002F__meta__\u002Fcode.md`, `docs\u002F__meta__\u002Fcode-python.md`.\n\nFindings, per document or spec, most severe first, one per line, with the fix:\n\n> `docs\u002Fcode\u002Fpython-typing.md:3` — **code.md, Frontmatter**: `description` has no trigger clause. Name the\n> situations the document should be read in.\n>\n> `docs\u002F__meta__\u002Fcode.spec.json` — **drift**: its `frontmatter` schema allows `status`, which `code.md`'s\n> frontmatter section does not describe. Describe it in the prose, or remove it from the schema.\n\n- **Every document finding cites the spec and section that states the requirement.** A finding with no\n  spec behind it is a style opinion — drop it.\n- Quote the checklist item when the violation is not self-evident.\n- A drift finding cites both halves; a load error is quoted as `lorecraft` printed it.\n- A requirement that seems wrong, or contradicts another spec, is a finding against the spec.\n\n## Setting the checks up in CI\n\n`lorecraft check` is the whole gate: it runs every rule over every document and every skill, and exits\nnon-zero on an error or a spec that cannot load. Run it in CI and in a pre-commit\nhook as is; do not narrow it to changed files, since a change to one document or spec can break\nanother.\n","# Docs Rules Check\n\nThe review pass over `docs\u002F`. For a changed document it verifies that the document follows the specs\nin `docs\u002F__meta__\u002F` that govern it; for a changed spec, that it loads, agrees with itself, and governs\nwhat it claims to. This is a **conformance check, not a review of content**: it does not question whether a\nconvention is the right one, or whether the code a document describes works.\n\nThis skill carries no per-corpus conventions. It resolves the specs from each document's path and validates\nagainst them. It reports; the fixes belong to the writing paths — `\u002Fdocs-rules` for a document,\n`\u002Fdocs-rules-creator` for a spec.\n\n## Running lorecraft\n\nEvery command below calls `lorecraft` directly. Where it is not on `PATH`, run `uvx lorecraft …` instead, or\n`uv run lorecraft …` in a uv project that declares Lorecraft as a dependency. Run from the repository root.\n\n## 1. The changeset\n\n```bash\ngit status --short -- docs                                     # uncommitted work, the default\ngit diff --name-only \"$(git merge-base HEAD main)\"...HEAD -- docs   # a whole branch\n```\n\nGiven explicit paths, check those instead. Split what changed in two:\n\n- **Documents** — every changed Markdown file outside `docs\u002F__meta__\u002F`. §2 to §5 check them.\n- **Specs** — every changed file in `docs\u002F__meta__\u002F`. A change to any file at a spec name is\n  a change to that spec: its prose and every JSON file beside it. §6 checks them.\n\n## 2. The specs that govern each document\n\n```bash\nlorecraft inspect\n```\n\nEach document is followed by the names of the specs governing it, broad to narrow; the name `\u003Cname>` is the\nprose at `docs\u002F__meta__\u002F\u003Cname>.md`.\n[cli-inspect](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-inspect.md) describes the output. Read every\nspec listed for a document **before** the document, so its checklist is in hand while reading. A document can\nbe governed for one part and not another;\n[check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#key-concepts) says what governs each part.\nReport a document as unvalidated for a part nothing governs, rather than borrowing another corpus's conventions.\n\n## 3. Run the checks\n\nThe checks decide every mechanical requirement — required and allowed frontmatter fields, their vocabularies and\npatterns, `name` against the filename, the title, section order, empty and forbidden sections, word caps and the\ntoken budget. Do not check those by hand.\n\n```bash\nlorecraft check                              # every rule over every document and skill, one read of the tree\nlorecraft check --format json                # machine-readable\n```\n\nThe run covers the whole workspace; read the diagnostics for the documents the change touches. A diagnostic prints as\n`path:line: severity[CODE]: message`, and may be followed by `-->`, `= help:` and `= note:` lines, or `labels` and\n`children` in JSON; for a missing section they say what it holds and show a sample, so read them before fixing it.\nExit `0` means no error, warnings included, `1` at least one error, a spec that cannot be loaded included — §6 covers that one — and `2` invalid input or\nselectors, or that the root or `docs\u002F__meta__\u002F` cannot be listed. A `\u003Cpath>: ungoverned for \u003Cparts>` line on stderr is not a\nfailure; report the document as unvalidated for those parts. The rule groups and their codes, `LC2xx` frontmatter, `LC3xx`\noutline, `LC4xx` length, `LC5xx` links, are listed in\n[check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#findings).\n\nThe run checks every agent skill too. A diagnostic at a skill's path, or an `LC1xx` one, is about a skill, not a\ndocument, and falls outside this review.\n\nA word cap or budget diagnostic on a section the change added to blocks, like any other error. One on a section\nthe change did not touch is pre-existing: report it as such. The fix for an overage is to move or cut, never to\ncompress.\n\n## 4. Walk the checklist\n\n**A spec's checklist is the check surface for what the commands cannot decide**: whether a section\nsays what the spec asks of it, cross-reference direction, whether a `description` genuinely helps a\nreader find the document. Walk each item against each changed document, and each namespace layer's checklist\ntoo. Where a spec has no checklist, walk its requirements instead.\n\nCheck only what the changeset touches — an unchanged document breaking a requirement is not this changeset's finding.\nThe one exception is §5.\n\n## 5. Hunt for inventories that will rot\n\nA list of files inside a document is a second source of truth nothing keeps honest. **Flag every one, whether\nor not the changeset introduced it**: a table or list whose entries are documents, a \"see also\" naming each\nsibling, a count (\"the four principle documents\"). For each, report the derivation that should replace it: the\ncorpus directory, a naming convention, or `lorecraft inspect`. A references section naming what a document\ndepends on is not a finding. Where a list survives for a stated reason, compare it with `ls docs\u002F\u003Ccorpus>\u002F`; a\nlist already out of sync is a finding.\n\n## 6. Changed specs\n\nLorecraft loads and validates each JSON file on its own, but it cannot tell whether the JSON says what the\nprose says, or whether a spec name governs the documents its author meant. Check each changed\nspec for both.\n\n**Load.** `lorecraft inspect` validates every spec before any document is read. A structure file\nmust use only the dialect's keys and state usable values, and its `frontmatter` key must satisfy the JSON Schema Draft\n2020-12 meta-schema, state `\"type\": \"object\"` at its root, and carry no `$id` at any depth. A leftover\n`\u003Cname>.header.json` is not read: its schema belongs in that key now. A file that fails stops the run with an error\nnaming it: `inspect` exits `2`, and `lorecraft check` reports it as an error diagnostic and exits `1`. That error is the finding;\n[spec-structure](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure.md) says what is refused for any\nfile, and [spec-structure-outline](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-outline.md),\n[spec-structure-budget](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-budget.md) and\n[spec-structure-frontmatter](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec-structure-frontmatter.md) what\nis refused for their keys.\n\n**Resolution.** In the `inspect` tree, compare what is governed with what was meant.\n[spec](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fspec.md) states how a path selects its specs.\n\n- Each changed spec appears under its corpus. A file whose name does not parse — a hyphen in a corpus name, a\n  dot in a spec name, a `\u003Cname>.\u003Ctoken>.json` that no file type's pattern claims — is left out silently, and\n  so is a namespace spec whose corpus has no file of its own or no directory under `docs\u002F`.\n- Each document lists the spec names intended. A namespace matches a filename that equals it or continues it\n  with a hyphen: `code-python` governs `python-typing.md`, not `pythonic.md`.\n- A namespace spec matches at least one document. One that matches none still loads and governs nothing,\n  usually after a rename.\n- For each part the corpus means to govern, the documents meant are governed, as\n  [check](https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fdocs\u002Ffeat\u002Fcli-check.md#key-concepts) defines it. A namespace\n  file never governs alone: the checks read it only once the corpus spec has a structure file, and its\n  `frontmatter` only once that file states the key.\n\n**Agreement.** Nothing detects drift between a spec's prose and its JSON, so read both:\n\n- Frontmatter: every frontmatter field the prose describes is in the `frontmatter` schema's `properties`, and\n  none is only in the schema; required fields, vocabularies and patterns match the prose's wording.\n- Structure: the prose's section list, order, and optional sections match `outline`; any word cap, token\n  budget, forbidden section or empty-section requirement in one is in the other, with the same number.\n- Layering: a namespace file states only what it adds, and does not restate or contradict its base. A\n  namespace written as though it could relax a corpus requirement is a finding.\n- Direction: the base names none of its extensions, in prose, `description`, or references.\n- A checklist: the prose ends with checklist items for the requirements no JSON file holds, since those are checked by\n  reading or not at all.\n\n**Consequence.** Run `lorecraft check`. A spec change that breaks existing documents must fix them in the same\nchange, or say why they are left: a finding the changed spec introduced belongs to this changeset.\n\n## 7. Report\n\nClean:\n\n> Docs rules check clean. Applied: `docs\u002F__meta__\u002Fcode.md`, `docs\u002F__meta__\u002Fcode-python.md`.\n\nFindings, per document or spec, most severe first, one per line, with the fix:\n\n> `docs\u002Fcode\u002Fpython-typing.md:3` — **code.md, Frontmatter**: `description` has no trigger clause. Name the\n> situations the document should be read in.\n>\n> `docs\u002F__meta__\u002Fcode.spec.json` — **drift**: its `frontmatter` schema allows `status`, which `code.md`'s\n> frontmatter section does not describe. Describe it in the prose, or remove it from the schema.\n\n- **Every document finding cites the spec and section that states the requirement.** A finding with no\n  spec behind it is a style opinion — drop it.\n- Quote the checklist item when the violation is not self-evident.\n- A drift finding cites both halves; a load error is quoted as `lorecraft` printed it.\n- A requirement that seems wrong, or contradicts another spec, is a finding against the spec.\n\n## Setting the checks up in CI\n\n`lorecraft check` is the whole gate: it runs every rule over every document and every skill, and exits\nnon-zero on an error or a spec that cannot load. Run it in CI and in a pre-commit\nhook as is; do not narrow it to changed files, since a change to one document or spec can break\nanother.\n",{"name":5,"description":7,"allowed-tools":24,"compatibility":25},"Bash(lorecraft check*) Bash(lorecraft inspect*) Bash(uvx lorecraft *) Bash(uv run lorecraft *) Bash(git diff *) Bash(git status *) Bash(git merge-base *) Bash(grep *) Bash(ls docs\u002F*)","Requires the lorecraft command, on PATH or run through uvx lorecraft, or uv run lorecraft in a uv project that declares Lorecraft as a dependency, and a git checkout","main","d2f3a5835a8673ccf134ae62f0a5e84104ff7098","skills\u002Fdocs-rules-check",1,"https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft","https:\u002F\u002Fgithub.com\u002FLNSD","2026-11-10 04:14:00",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add LNSD\u002Florecraft --skill docs-rules-check",{"tool":39,"command":40},"bunx","bunx skills add LNSD\u002Florecraft --skill docs-rules-check",{"tool":42,"command":43},"pnpm","pnpm dlx skills add LNSD\u002Florecraft --skill docs-rules-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Fskills\u002Fdocs-rules-check\u002FSKILL.md",true,[],[48,55,60,65,70,75],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DASA0R4R68AVTZJFJJBYDB","review","Review a change. Use when asked to review.","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC504\u002Ftrigger\u002Freference-link-to-parent-skill-file\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":56,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7DAS1YXJQ8FGABR8BGX9FAT","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC504\u002Fnear_miss\u002Fclimb-that-stays-inside-and-document-climb\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":61,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DAS0TCKQFF2YJ5VY9SWHV2","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC503\u002Ftrigger\u002Fskill-reference-link-read-from-skill-root\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":66,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7DARZNA9QGXHAY17142R8YT","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC503\u002Fnear_miss\u002Fskill-link-climbing-above-skill-root\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":71,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DARYHB7WBR44AJXFJSZQ7X","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC502\u002Ftrigger\u002Fskill-fragment-in-file-without-headings\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[],{"skillNo":76,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7DARXCTFKMH92FHVV8H30MM","https:\u002F\u002Fgithub.com\u002FLNSD\u002Florecraft\u002Fblob\u002Fmain\u002Ftests\u002Fit\u002Frule_cases\u002FLC501\u002Ftrigger\u002Fskill-link-starting-with-slash\u002Froot\u002F.agents\u002Fskills\u002Freview\u002FSKILL.md",[],[]]