[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757TC75F3YQFVWM19HFQQP5":3,"skill-same:01M757TC75F3YQFVWM19HFQQP5":62},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M757TC75F3YQFVWM19HFQQP5","markdown-frontmatter",null,"Use when adding, fixing, or validating YAML frontmatter on managed Markdown governed by the project-standards Markdown Frontmatter Standard; covers structure, field values, id generation, and validation.","L3DigitalNet\u002Fproject-standards","L3DigitalNet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263281676?v=4","01M757EDQ509DYAV1D9AHQXB1K","L3Digital","01M757EDQTGFYB654PNJZYJ49M",0,"MIT","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: markdown-frontmatter\ndescription: Use when adding, fixing, or validating YAML frontmatter on managed Markdown governed by the project-standards Markdown Frontmatter Standard; covers structure, field values, id generation, and validation.\ncompatibility: Claude Code and Codex CLI\nlicense: MIT\nmetadata:\n  author: Chris Purcell\n  version: '1.4'\n---\n\n# Markdown Frontmatter\n\n## Overview\n\nAuthor and fix YAML frontmatter for **managed Markdown documents** under the [project-standards Markdown Frontmatter Standard](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002FREADME.md).\n\nThis skill ships with the standard package and is installed repo-local at `.agents\u002Fskills\u002Fmarkdown-frontmatter` when a repository adopts the standard. That path is deliberate: both Claude Code and Codex CLI can discover it without a global skill owner.\n\n**Core principle: the schema is authoritative, not this file.** The machine contract is `markdown-frontmatter.schema.json` in project-standards, enforced by `project-standards validate`. This skill is the operating layer for the rules agents get wrong most often. On any conflict, the schema and current standard pages win.\n\n## When to use\n\n- Creating or editing a managed Markdown file (typically `README.md`, `docs\u002F**\u002F*.md`).\n- A `project-standards validate`, `validate-frontmatter`, or `format-frontmatter --check` run failed and you need to fix the block.\n- Deciding which `doc_type` \u002F `status` \u002F other controlled value to set.\n\n**When NOT to use: files that must NEVER carry frontmatter.** Agent-instruction and agent-skill files are harness config, not managed documents: `CLAUDE.md`, `AGENTS.md`, and anything under `.claude\u002F`, `.agents\u002F`, `.codex\u002F`. That includes this installed skill at `.agents\u002Fskills\u002Fmarkdown-frontmatter`. Exclude those paths through the package's `exclude` option in `.standards\u002Fconfig.toml` instead of adding metadata. A repo may also exclude its root `README.md` if it prefers no metadata table on its landing page.\n\n## Required fields (the eleven)\n\nEvery managed document opens with a `---` fenced YAML block carrying at least these, in this order:\n\n```yaml\n---\nschema_version: '1.1'\nid: 'note-xxxxxx-human-title'\ntitle: 'Human Title'\ndescription: 'One-sentence description of the document.'\ndoc_type: 'note'\nstatus: 'draft'\ncreated: 'YYYY-MM-DD'\nupdated: 'YYYY-MM-DD'\ntags: []\naliases: []\nrelated: []\n---\n```\n\nFor most docs, add the standard-profile optionals after `updated` in canonical order: `reviewed` (date|null), `owner` (stable person\u002Fteam\u002Frole), `consumer` (enum), then after `related`: `source` (array), `confidence` (enum), `visibility` (enum), `license` (string|null). Relationship fields are optional, used only when needed: `supersedes`, `superseded_by`, `depends_on`, `applies_to`.\n\n## Formatting rules that actually fail validation\n\nThese are the machine-checked rules an agent skips by habit:\n\n- **Quote every string, including dates.** `created: '2026-06-07'`, never `created: 2026-06-07`.\n- **Identifier-like numbers are strings.** `schema_version: '1.1'`, not `1.1`.\n- **Non-empty lists use block style** (`- 'item'` per line); **empty lists use `[]`**. No duplicate items.\n- **No unknown top-level fields.** A stray `version:` or `type:` is rejected. Project- or tool-specific keys go under the `publish`, `project`, or `x_project` extension objects only.\n- **Canonical key order** when keys are present:\n\n  ```text\n  schema_version, id, title, description, doc_type, status, created, updated,\n  reviewed, owner, consumer, tags, aliases, related, supersedes, superseded_by,\n  depends_on, applies_to, source, confidence, visibility, license,\n  publish, project, x_project\n  ```\n\n## Controlled values\n\nThese fields accept only these values (the schema is the source of truth):\n\n| Field | Allowed values |\n| --- | --- |\n| `doc_type` | `index`, `note`, `concept`, `reference`, `runbook`, `spec`, `plan`, `adr`, `decision`, `research`, `template`, `log`, `prompt`, `schema` |\n| `status` | `draft`, `active`, `review`, `deprecated`, `archived`, `superseded`, `stub` |\n| `confidence` | `high`, `medium`, `low`, `unknown` |\n| `visibility` | `private`, `internal`, `public` |\n| `consumer` | `user`, `agent`, `mix`, `unknown` |\n\n- `README.md` and `index.md` → `doc_type: 'index'`. Files under `docs\u002Fresearch\u002F` → `doc_type: 'research'`.\n- `stub` is a **status**, never a `doc_type`. Use `doc_type`, never `type`.\n- Canonical global tags include `frontmatter`, `metadata`, `standard`, `validation`, `infrastructure`, `it`, and `network`; repos may add documented local tags when the global set is insufficient.\n\n## The `id` field — standard-enforced format\n\n> **This is a standard rule, not a local addition.** `markdown-frontmatter@1.8` enforces the id format below via `validate-id` (run by `project-standards validate` and the V5 CI workflow). An id whose leading segment is not a valid `doc_type` **fails validation** with `prefix '\u003Cx>' is not a valid doc_type`. Earlier repo-name-prefixed ids no longer pass.\n\n```text\n{doc_type}-{base36-6}-{document-name}\n```\n\nThe `doc_type` (one of the controlled values above), then a random 6-character base36 token, then a readable document slug, all lower kebab-case (e.g. `runbook-0f943i-restart-netbox-after-config-change`). The token keeps the id globally unique; the slug is frozen at creation and does **not** change when the title is edited.\n\n**Generate the id with the script. Never invent the token yourself.** An LLM asked for a \"random\" base36 token produces low-entropy, collision-prone strings and reuses tokens already in context, defeating the uniqueness goal. `scripts\u002F` is this skill's own directory (invoke by absolute path if your cwd is elsewhere):\n\n```bash\nscripts\u002Fnew-doc-id \u003Cdocument-name>                        # bare id, doc_type 'note'\nscripts\u002Fnew-doc-id --doc-type runbook \u003Cdocument-name>     # bare id, 'runbook' prefix\nscripts\u002Fnew-doc-id --scaffold --doc-type runbook \u003Cname>   # full canonical frontmatter block\n```\n\nThe `--doc-type` value becomes both the id prefix and (in `--scaffold`) the `doc_type` field, so the two always agree; it defaults to `note`. `--doc-type` and `--status` must be standard-controlled values. `--scaffold` emits the eleven required fields in canonical order with today's date correctly quoted. Replace the `REPLACE:` description placeholder before committing.\n\nADRs are the exception: follow the standard's ADR id form (`adr-{NNNN}-{repo-name}-{title}`, e.g. `adr-0001-homelab-use-postgresql-for-persistent-storage`), not the `doc_type`-prefixed format. Do not use the script for ADR ids.\n\n## Worked example (compliant standard profile)\n\n```yaml\n---\nschema_version: '1.1'\nid: 'runbook-0f943i-restart-netbox-after-config-change'\ntitle: 'Restart netbox after config change'\ndescription: 'Procedure to safely reload netbox after editing its configuration.'\ndoc_type: 'runbook'\nstatus: 'active'\ncreated: '2026-03-10'\nupdated: '2026-06-07'\nreviewed: '2026-06-07'\nowner: 'platform-team'\nconsumer: 'user'\ntags:\n  - 'infrastructure'\n  - 'network'\n  - 'operations'\n  - 'runbook'\naliases:\n  - 'netbox-restart'\nrelated:\n  - 'docs\u002Farchitecture.md'\nsource: []\nconfidence: 'high'\nvisibility: 'internal'\nlicense: null\n---\n# Restart netbox after config change\n\n...document body...\n```\n\n## Validate\n\nCompliance = `project-standards validate` exits `0`. Run it from the repository root:\n\n```bash\nproject-standards validate\n```\n\nThat command runs schema validation, ID-format validation, and reference validation. Exit codes: `0` all matched files valid (or none matched); `1` one or more documents failed; `2` config\u002Fschema error.\n\nUse the formatter check for canonical quote style, key order, and list layout:\n\n```bash\nformat-frontmatter --check\n```\n\nTo check or repair a single file's id: `validate-id \u003Cfile>` (add `--fix` to rewrite an invalid id through the platform executor).\n\n## Common mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| `type:` instead of `doc_type:` | Rename; `type` is not a field. |\n| Unquoted date `created: 2026-06-07` | Quote it: `'2026-06-07'`. |\n| `doc_type: 'readme'` for a README | README\u002Findex → `doc_type: 'index'`. |\n| Extra top-level key (`version:`, `category:`) | Move under `project:`\u002F`x_project:`, or drop it. |\n| Frontmatter added to `CLAUDE.md` \u002F `.claude\u002F**` \u002F `.agents\u002F**` | Remove it; add the path to the package `exclude` option. |\n| Omitting required arrays (`tags`\u002F`aliases`\u002F`related`) | Always present; empty = `[]`. |\n| `doc_type: 'stub'` | `stub` is a `status`, not a `doc_type`. |\n\n## Authoritative references\n\n- [Standard README](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002FREADME.md) — overview and adoption surface.\n- [Structure Requirements](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fstructure.md) — hard fields, key order, scalar\u002Flist rules, IDs, and validation.\n- [Field Values](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Ffield-values.md) — lifecycle, ownership, canonical tags, aliases, relationships, sources, and extensions.\n- [Adoption guide](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fadopt.md) — unified config, CI workflow, repo-local skill install, and compliance procedure.\n- `standards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fschemas\u002Fmarkdown-frontmatter.schema.json` (in project-standards) — the selected package contract; wins on any conflict.\n","# Markdown Frontmatter\n\n## Overview\n\nAuthor and fix YAML frontmatter for **managed Markdown documents** under the [project-standards Markdown Frontmatter Standard](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002FREADME.md).\n\nThis skill ships with the standard package and is installed repo-local at `.agents\u002Fskills\u002Fmarkdown-frontmatter` when a repository adopts the standard. That path is deliberate: both Claude Code and Codex CLI can discover it without a global skill owner.\n\n**Core principle: the schema is authoritative, not this file.** The machine contract is `markdown-frontmatter.schema.json` in project-standards, enforced by `project-standards validate`. This skill is the operating layer for the rules agents get wrong most often. On any conflict, the schema and current standard pages win.\n\n## When to use\n\n- Creating or editing a managed Markdown file (typically `README.md`, `docs\u002F**\u002F*.md`).\n- A `project-standards validate`, `validate-frontmatter`, or `format-frontmatter --check` run failed and you need to fix the block.\n- Deciding which `doc_type` \u002F `status` \u002F other controlled value to set.\n\n**When NOT to use: files that must NEVER carry frontmatter.** Agent-instruction and agent-skill files are harness config, not managed documents: `CLAUDE.md`, `AGENTS.md`, and anything under `.claude\u002F`, `.agents\u002F`, `.codex\u002F`. That includes this installed skill at `.agents\u002Fskills\u002Fmarkdown-frontmatter`. Exclude those paths through the package's `exclude` option in `.standards\u002Fconfig.toml` instead of adding metadata. A repo may also exclude its root `README.md` if it prefers no metadata table on its landing page.\n\n## Required fields (the eleven)\n\nEvery managed document opens with a `---` fenced YAML block carrying at least these, in this order:\n\n```yaml\n---\nschema_version: '1.1'\nid: 'note-xxxxxx-human-title'\ntitle: 'Human Title'\ndescription: 'One-sentence description of the document.'\ndoc_type: 'note'\nstatus: 'draft'\ncreated: 'YYYY-MM-DD'\nupdated: 'YYYY-MM-DD'\ntags: []\naliases: []\nrelated: []\n---\n```\n\nFor most docs, add the standard-profile optionals after `updated` in canonical order: `reviewed` (date|null), `owner` (stable person\u002Fteam\u002Frole), `consumer` (enum), then after `related`: `source` (array), `confidence` (enum), `visibility` (enum), `license` (string|null). Relationship fields are optional, used only when needed: `supersedes`, `superseded_by`, `depends_on`, `applies_to`.\n\n## Formatting rules that actually fail validation\n\nThese are the machine-checked rules an agent skips by habit:\n\n- **Quote every string, including dates.** `created: '2026-06-07'`, never `created: 2026-06-07`.\n- **Identifier-like numbers are strings.** `schema_version: '1.1'`, not `1.1`.\n- **Non-empty lists use block style** (`- 'item'` per line); **empty lists use `[]`**. No duplicate items.\n- **No unknown top-level fields.** A stray `version:` or `type:` is rejected. Project- or tool-specific keys go under the `publish`, `project`, or `x_project` extension objects only.\n- **Canonical key order** when keys are present:\n\n  ```text\n  schema_version, id, title, description, doc_type, status, created, updated,\n  reviewed, owner, consumer, tags, aliases, related, supersedes, superseded_by,\n  depends_on, applies_to, source, confidence, visibility, license,\n  publish, project, x_project\n  ```\n\n## Controlled values\n\nThese fields accept only these values (the schema is the source of truth):\n\n| Field | Allowed values |\n| --- | --- |\n| `doc_type` | `index`, `note`, `concept`, `reference`, `runbook`, `spec`, `plan`, `adr`, `decision`, `research`, `template`, `log`, `prompt`, `schema` |\n| `status` | `draft`, `active`, `review`, `deprecated`, `archived`, `superseded`, `stub` |\n| `confidence` | `high`, `medium`, `low`, `unknown` |\n| `visibility` | `private`, `internal`, `public` |\n| `consumer` | `user`, `agent`, `mix`, `unknown` |\n\n- `README.md` and `index.md` → `doc_type: 'index'`. Files under `docs\u002Fresearch\u002F` → `doc_type: 'research'`.\n- `stub` is a **status**, never a `doc_type`. Use `doc_type`, never `type`.\n- Canonical global tags include `frontmatter`, `metadata`, `standard`, `validation`, `infrastructure`, `it`, and `network`; repos may add documented local tags when the global set is insufficient.\n\n## The `id` field — standard-enforced format\n\n> **This is a standard rule, not a local addition.** `markdown-frontmatter@1.8` enforces the id format below via `validate-id` (run by `project-standards validate` and the V5 CI workflow). An id whose leading segment is not a valid `doc_type` **fails validation** with `prefix '\u003Cx>' is not a valid doc_type`. Earlier repo-name-prefixed ids no longer pass.\n\n```text\n{doc_type}-{base36-6}-{document-name}\n```\n\nThe `doc_type` (one of the controlled values above), then a random 6-character base36 token, then a readable document slug, all lower kebab-case (e.g. `runbook-0f943i-restart-netbox-after-config-change`). The token keeps the id globally unique; the slug is frozen at creation and does **not** change when the title is edited.\n\n**Generate the id with the script. Never invent the token yourself.** An LLM asked for a \"random\" base36 token produces low-entropy, collision-prone strings and reuses tokens already in context, defeating the uniqueness goal. `scripts\u002F` is this skill's own directory (invoke by absolute path if your cwd is elsewhere):\n\n```bash\nscripts\u002Fnew-doc-id \u003Cdocument-name>                        # bare id, doc_type 'note'\nscripts\u002Fnew-doc-id --doc-type runbook \u003Cdocument-name>     # bare id, 'runbook' prefix\nscripts\u002Fnew-doc-id --scaffold --doc-type runbook \u003Cname>   # full canonical frontmatter block\n```\n\nThe `--doc-type` value becomes both the id prefix and (in `--scaffold`) the `doc_type` field, so the two always agree; it defaults to `note`. `--doc-type` and `--status` must be standard-controlled values. `--scaffold` emits the eleven required fields in canonical order with today's date correctly quoted. Replace the `REPLACE:` description placeholder before committing.\n\nADRs are the exception: follow the standard's ADR id form (`adr-{NNNN}-{repo-name}-{title}`, e.g. `adr-0001-homelab-use-postgresql-for-persistent-storage`), not the `doc_type`-prefixed format. Do not use the script for ADR ids.\n\n## Worked example (compliant standard profile)\n\n```yaml\n---\nschema_version: '1.1'\nid: 'runbook-0f943i-restart-netbox-after-config-change'\ntitle: 'Restart netbox after config change'\ndescription: 'Procedure to safely reload netbox after editing its configuration.'\ndoc_type: 'runbook'\nstatus: 'active'\ncreated: '2026-03-10'\nupdated: '2026-06-07'\nreviewed: '2026-06-07'\nowner: 'platform-team'\nconsumer: 'user'\ntags:\n  - 'infrastructure'\n  - 'network'\n  - 'operations'\n  - 'runbook'\naliases:\n  - 'netbox-restart'\nrelated:\n  - 'docs\u002Farchitecture.md'\nsource: []\nconfidence: 'high'\nvisibility: 'internal'\nlicense: null\n---\n# Restart netbox after config change\n\n...document body...\n```\n\n## Validate\n\nCompliance = `project-standards validate` exits `0`. Run it from the repository root:\n\n```bash\nproject-standards validate\n```\n\nThat command runs schema validation, ID-format validation, and reference validation. Exit codes: `0` all matched files valid (or none matched); `1` one or more documents failed; `2` config\u002Fschema error.\n\nUse the formatter check for canonical quote style, key order, and list layout:\n\n```bash\nformat-frontmatter --check\n```\n\nTo check or repair a single file's id: `validate-id \u003Cfile>` (add `--fix` to rewrite an invalid id through the platform executor).\n\n## Common mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| `type:` instead of `doc_type:` | Rename; `type` is not a field. |\n| Unquoted date `created: 2026-06-07` | Quote it: `'2026-06-07'`. |\n| `doc_type: 'readme'` for a README | README\u002Findex → `doc_type: 'index'`. |\n| Extra top-level key (`version:`, `category:`) | Move under `project:`\u002F`x_project:`, or drop it. |\n| Frontmatter added to `CLAUDE.md` \u002F `.claude\u002F**` \u002F `.agents\u002F**` | Remove it; add the path to the package `exclude` option. |\n| Omitting required arrays (`tags`\u002F`aliases`\u002F`related`) | Always present; empty = `[]`. |\n| `doc_type: 'stub'` | `stub` is a `status`, not a `doc_type`. |\n\n## Authoritative references\n\n- [Standard README](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002FREADME.md) — overview and adoption surface.\n- [Structure Requirements](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fstructure.md) — hard fields, key order, scalar\u002Flist rules, IDs, and validation.\n- [Field Values](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Ffield-values.md) — lifecycle, ownership, canonical tags, aliases, relationships, sources, and extensions.\n- [Adoption guide](https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fv5.14.0\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fadopt.md) — unified config, CI workflow, repo-local skill install, and compliance procedure.\n- `standards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fschemas\u002Fmarkdown-frontmatter.schema.json` (in project-standards) — the selected package contract; wins on any conflict.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":27},{"author":25,"version":26},"Chris Purcell","1.4","Claude Code and Codex CLI","main","14fc7f97e8eb0eaeb6ec4af770ff187d1c490e87","standards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fskills\u002Fmarkdown-frontmatter","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards","https:\u002F\u002Fgithub.com\u002FL3DigitalNet","https:\u002F\u002Fl3digital.net","Tools for AI integration, home automation, and self-hosted infrastructure.","2026-10-07 19:35:03",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add L3DigitalNet\u002Fproject-standards --skill markdown-frontmatter",{"tool":42,"command":43},"bunx","bunx skills add L3DigitalNet\u002Fproject-standards --skill markdown-frontmatter",{"tool":45,"command":46},"pnpm","pnpm dlx skills add L3DigitalNet\u002Fproject-standards --skill markdown-frontmatter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",158,"https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fskills\u002Fmarkdown-frontmatter\u002Fagents\u002Fopenai.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002Fnew-doc-id","SCRIPT","脚本",6904,"https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.8\u002Fskills\u002Fmarkdown-frontmatter\u002Fscripts\u002Fnew-doc-id",[63,70,75,80,85,90],{"skillNo":64,"name":65,"nameZh":6,"description":66,"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},"01M757TMB5M4RPWJ4SSZ05284W","project-toolbox","Use when running a periodic repository housekeeping sweep or checking whether the repository's actual state still matches what its standards, configuration, and documentation claim; routes to the packaged Project Toolbox workflow documents.","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fproject-toolbox\u002Fversions\u002F1.1\u002Fskills\u002Fproject-toolbox\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"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},"01M757TJ46RKQZA01Q7Y7BFGX5","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fproject-toolbox\u002Fversions\u002F1.0\u002Fskills\u002Fproject-toolbox\u002FSKILL.md",[],[],{"skillNo":76,"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":77,"categories":78,"keywords":79,"publishedAt":19},"01M757TFHVJVE905V6C8QG60R1","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.9\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",[],[],{"skillNo":81,"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":82,"categories":83,"keywords":84,"publishedAt":19},"01M757T9J5HGP2DZN7AMJDYQGH","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.7\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",[],[],{"skillNo":86,"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":87,"categories":88,"keywords":89,"publishedAt":19},"01M757T6T4CPCEKG0YA9F57ADW","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.6\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",[],[],{"skillNo":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M757T3EHX6GN0YF4SGRBGHHS","https:\u002F\u002Fgithub.com\u002FL3DigitalNet\u002Fproject-standards\u002Fblob\u002Fmain\u002Fstandards\u002Fmarkdown-frontmatter\u002Fversions\u002F1.5\u002Fskills\u002Fmarkdown-frontmatter\u002FSKILL.md",[],[]]