[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758AX4NH324X897BWACE3FB":3,"skill-same:01M758AX4NH324X897BWACE3FB":106},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M758AX4NH324X897BWACE3FB","skillset-adrs",null,"Author, update, and manage Skillset ADRs. Use when creating new ADRs, promoting drafts, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.","outfitter-dev\u002Fskillset","outfitter-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206289526?v=4","01M7589FBAPHBH5CX8XMH1MPJV","Outfitter","01M7589FCJ31KF5STHVN4XKY79",1,"MIT","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\ndescription: Author, update, and manage Skillset ADRs. Use when creating new ADRs, promoting drafts, updating the ADR index, renaming or renumbering ADRs, or when the user mentions ADR, architecture decision, or decision record.\nmetadata:\n  skillset.schema: \"1\"\n  version: 0.1.0\nname: skillset-adrs\n---\n\n# Skillset ADR Authoring\n\nADRs document the significant design decisions behind Skillset: choices that, if reversed, would change the source contract, target rendering model, compiler promises, or authoring workflow.\n\n## Core Principles\n\nRead `docs\u002Fproject\u002Ftenets.md` before writing or changing an ADR. Every ADR must be consistent with the tenets, or it must explicitly argue for changing them.\n\nUse the tenets in that file as the review lens. Read them from `docs\u002Fproject\u002Ftenets.md` each time rather than from memory or a copied list; they change as decisions are accepted.\n\nWhen an ADR proposes something new, test it against these questions. Does it reduce repeated authoring? Does it preserve target-native truth? Does it make unsupported behavior easier to see? Does it keep activation separate from compilation?\n\n## Before Writing\n\nRead related ADRs before drafting. Use `docs\u002Fadrs\u002Fdecision-map.json` or browse `docs\u002Fadrs\u002F` and `docs\u002Fadrs\u002Fdrafts\u002F` to find records that touch similar concerns. Good ADRs build on the existing decision graph: they reference specific sections of prior ADRs, link to their headings, and explain how the new decision compounds with, specializes, or supersedes what is already decided.\n\nWhen your ADR relates to an existing one:\n\n- Link to it in References with a one-line description of the relationship.\n- Link to specific headings when referencing a particular decision.\n- Explain whether you are extending, specializing, or building on the prior decision.\n- If you contradict a prior ADR, call that out explicitly and use the supersedes mechanism.\n\n## Script\n\nAll ADR operations go through the skill-local `scripts\u002Fadr.ts` helper when available.\n\nDestructive commands preview by default. Pass `--yes` to apply changes.\n\n```bash\n# Create a new draft (applies immediately because it is non-destructive)\nbun scripts\u002Fadr.ts create --title \"Compile Target Selection\"\n\n# Preview a promote, then apply\nbun scripts\u002Fadr.ts promote compile-target-selection\nbun scripts\u002Fadr.ts promote compile-target-selection --yes\n\n# Promote a draft that replaces an earlier ADR as a whole\nbun scripts\u002Fadr.ts promote compile-target-selection --supersedes 0013 --yes\n\n# Update title, slug, status, or number\nbun scripts\u002Fadr.ts update source-first-loadouts --title \"Source-First Loadouts\"\nbun scripts\u002Fadr.ts update 013 --renumber 0013\nbun scripts\u002Fadr.ts update compile-target-selection --slug compile-targets\nbun scripts\u002Fadr.ts update compile-targets --status proposed --yes\n\n# Demote a numbered ADR back to drafts\nbun scripts\u002Fadr.ts demote 0014 --yes\n\n# Auto-fix common issues (number padding, cross-refs): preview, then apply\nbun scripts\u002Fadr.ts fix\nbun scripts\u002Fadr.ts fix --yes\n\n# Validate format and consistency\nbun scripts\u002Fadr.ts check\n\n# Regenerate decision maps and draft index\nbun scripts\u002Fadr.ts map\n```\n\nThe script handles file creation, git moves, title\u002Fslug\u002Fnumber updates, index rebuilding, decision-map generation for numbered and draft ADRs, and cross-reference updates.\n\nFor manual ADR management without the script, see [assets\u002Fadr-management.md](assets\u002Fadr-management.md).\n\n## Titles\n\n1. MUST use an H1 `#`.\n2. MUST lead with `ADR-NNNN` unless in `draft` status, which omits the number.\n3. MUST be descriptive enough to recall without opening the file. A good title makes a claim or names the durable decision, not just the topic.\n4. Prefer a single clear phrase over `Topic - Explanation` structure. A subtitle is a fallback when the short title cannot stand alone.\n5. A project-specific name is fine when the concept is established. A generic noun needs to say what the decision is.\n\nExamples:\n\n- Good: \"Source-First Loadouts\"\n- Good: \"Deterministic Target Renderings\"\n- Good: \"Compile Target Selection\"\n- Good: \"Unsupported Destination Must Be Provenanced\"\n- Avoid: \"Targets\"\n- Avoid: \"Config\"\n- Avoid: \"Codex and Claude\"\n\n## Locations\n\n- Numbered: `docs\u002Fadrs\u002FNNNN-slug.md`\n- Drafts: `docs\u002Fadrs\u002Fdrafts\u002FYYYYMMDD-slug.md`\n- Index: `docs\u002Fadrs\u002FREADME.md`\n- Template: `docs\u002Fadrs\u002Ftemplate.md`\n- Numbered decision map: `docs\u002Fadrs\u002Fdecision-map.json`\n- Draft decision map: `docs\u002Fadrs\u002Fdrafts\u002Fdecision-map.json`\n- Tenets: `docs\u002Fproject\u002Ftenets.md`\n\n## Statuses\n\n| Status | Location | Numbered | Meaning |\n| --- | --- | --- | --- |\n| `draft` | `docs\u002Fadrs\u002Fdrafts\u002F` | No | Decision proposed, open for discussion |\n| `proposed` | `docs\u002Fadrs\u002F` | Yes | Decision refined, ready for review |\n| `accepted` | `docs\u002Fadrs\u002F` | Yes | Decision approved, guides implementation |\n| `rejected` | `docs\u002Fadrs\u002F` | Yes | Decision considered and declined, with reasoning preserved |\n| `superseded` | `docs\u002Fadrs\u002F` | Yes | Replaced by a later ADR, with successor linked |\n\n## Frontmatter\n\n```yaml\n---\nid: NNNN\nslug: short-kebab-slug\ntitle: Title in Title Case\nstatus: proposed\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\nowners: ['[galligan](https:\u002F\u002Fgithub.com\u002Fgalligan)']\n# depends_on: [0, compile-target-selection]\n# amends: [0]\n---\n```\n\n`depends_on` accepts numbered ADR IDs and draft slugs (the filename without date prefix and `.md`). Use integers for numbered ADRs and slugs for drafts. The decision map renders these as graph edges.\n\n`amends` records a narrow change to one or more existing accepted decisions without replacing their historical body or status. Authors may declare it while the successor is a draft or numbered proposal, but targets must be accepted, numbered ADRs; draft slugs are not valid amendment identities. The relationship becomes active only when the successor is accepted. Decision maps preserve the authored `amends` list and derive the reciprocal `amended_by` list; never author `amended_by` directly.\n\nUse `supersedes` when the successor replaces the earlier decision as a whole. Supersession marks the predecessor `superseded` and records `superseded_by`; accepted later replacements, including recursively evidenced supersession chains, preserve previously accepted amendment history. A bare `status: superseded` edit or a proposed\u002Frejected replacement is not acceptance-history evidence. Amendment leaves predecessor source unchanged.\n\n## Content\n\n### Minimal ADR\n\n```markdown\n# ADR-NNNN: Descriptive Title\n\n## Context\n\nWhat problem, tension, or drift prompted the decision.\n\n## Decision\n\nWhat we chose and why. Include concrete source or output examples when they make the decision clearer.\n\n## Consequences\n\nWhat this enables, what it constrains, and what remains open.\n\n## References\n\n- [Tenets](..\u002Fproject\u002Ftenets.md) - governing design principles.\n```\n\n### Detailed ADR\n\n```markdown\n# ADR-NNNN: Descriptive Title\n\n## Context\n\n## Decision\n\nThe decision in one declarative sentence.\n\n### Focused Subsection\n\nUse subsections when the reasoning has distinct parts.\n\n## Non-Goals\n\nWhat this ADR is not trying to solve.\n\n## Consequences\n\n### Positive\n\nWhat this enables.\n\n### Tradeoffs\n\nKnown costs or constraints we accept.\n\n### Risks\n\nUncertain outcomes we are watching, with mitigation.\n\n## Non-Decisions\n\nExplicitly deferred decisions.\n\n## References\n```\n\n## Reference Format\n\n```markdown\nFor numbered ADRs:\n- [ADR-NNNN: Title](NNNN-slug.md) - one-line relationship\n\nFor draft ADRs:\n- ADR: Title (draft) - one-line relationship\n\nFor docs:\n- [Doc title](..\u002Fpath.md) - one-line relationship\n```\n\n## Style Guide\n\n### Voice\n\n- **Declarative, not tentative.** State the decision. If there is uncertainty, name it as a risk or non-decision.\n- **Conversational but precise.** Write like a sharp maintainer explaining what future agents and contributors must preserve.\n- **Active voice.** Skillset derives, renders, validates, rejects, and explains. Authors declare, opt out, and review.\n- **First person sparingly.** Use it in Context when grounding the problem in real experience. Drop it in Decision.\n\n### Structure\n\n- **Context tells a story.** Start with the pressure that made the decision necessary, not abstract background.\n- **Decision subsections start with a one-sentence thesis.** The first sentence should stand alone as a summary.\n- **Show the concrete failure.** Explain what breaks without the decision: duplicated config, silent target skips, fake portability, stale output, or unsafe activation.\n- **Code examples are primary evidence.** Source and generated-output snippets often explain the contract better than prose.\n- **Claims must be backed up.** Reference code, docs, ADRs, official docs, or live verification. If you cannot back a claim, soften or remove it.\n\n### Patterns To Use\n\n- \"This means:\" lists after a principle.\n- \"The test:\" heuristics that future agents can apply.\n- Good\u002FBad examples for contract shape.\n- Tables for structured tradeoffs.\n- Footnotes for external references.\n- Heading links for internal cross-references.\n\n### Patterns To Avoid\n\n- No hedging.\n- No restating the title.\n- No wall-of-text paragraphs.\n- No future benefit claims without present justification.\n- No \"as mentioned above\"; link directly.\n- No disparaging other tools or agent surfaces.\n- No numbered headings; descriptive headings preserve stable markdown anchors.\n\n### Consequences Style\n\n- Positive items are capabilities, not restatements.\n- Tradeoffs are honest. Name what we gave up.\n- \"What this does NOT decide\" is useful to future authors. Be specific and explain why it is deferred.\n\n### Vocabulary\n\nUse accepted Skillset vocabulary consistently:\n\n- `source`, not generated output, when discussing `.skillset\u002F`.\n- `target` or `provider`, not runtime, when discussing provider build destinations.\n- `render`\u002F`rendering`, not copying, when source intent becomes target-native output.\n- `rendered output`, not source truth, for generated provider files.\n- `compile.targets`, not bare `targets`, for root provider selection.\n- `compile.unsupportedDestination`, not silent fallback, for unsupported destination policy.\n- `provenance`, not comments, for lock\u002Fstatus evidence.\n\nRead `docs\u002Fproject\u002Ftenets.md` before writing. Every ADR must be consistent with the tenets.\n\n### Tone Calibration\n\nRead the draft aloud. If it sounds like a corporate design document, rewrite it. If it sounds like a blog post, tighten it. The target is the precision of a spec with the readability of a well-written README: someone who knows the domain deeply explaining the reasoning to someone who will have to live with the consequences.\n","# Skillset ADR Authoring\n\nADRs document the significant design decisions behind Skillset: choices that, if reversed, would change the source contract, target rendering model, compiler promises, or authoring workflow.\n\n## Core Principles\n\nRead `docs\u002Fproject\u002Ftenets.md` before writing or changing an ADR. Every ADR must be consistent with the tenets, or it must explicitly argue for changing them.\n\nUse the tenets in that file as the review lens. Read them from `docs\u002Fproject\u002Ftenets.md` each time rather than from memory or a copied list; they change as decisions are accepted.\n\nWhen an ADR proposes something new, test it against these questions. Does it reduce repeated authoring? Does it preserve target-native truth? Does it make unsupported behavior easier to see? Does it keep activation separate from compilation?\n\n## Before Writing\n\nRead related ADRs before drafting. Use `docs\u002Fadrs\u002Fdecision-map.json` or browse `docs\u002Fadrs\u002F` and `docs\u002Fadrs\u002Fdrafts\u002F` to find records that touch similar concerns. Good ADRs build on the existing decision graph: they reference specific sections of prior ADRs, link to their headings, and explain how the new decision compounds with, specializes, or supersedes what is already decided.\n\nWhen your ADR relates to an existing one:\n\n- Link to it in References with a one-line description of the relationship.\n- Link to specific headings when referencing a particular decision.\n- Explain whether you are extending, specializing, or building on the prior decision.\n- If you contradict a prior ADR, call that out explicitly and use the supersedes mechanism.\n\n## Script\n\nAll ADR operations go through the skill-local `scripts\u002Fadr.ts` helper when available.\n\nDestructive commands preview by default. Pass `--yes` to apply changes.\n\n```bash\n# Create a new draft (applies immediately because it is non-destructive)\nbun scripts\u002Fadr.ts create --title \"Compile Target Selection\"\n\n# Preview a promote, then apply\nbun scripts\u002Fadr.ts promote compile-target-selection\nbun scripts\u002Fadr.ts promote compile-target-selection --yes\n\n# Promote a draft that replaces an earlier ADR as a whole\nbun scripts\u002Fadr.ts promote compile-target-selection --supersedes 0013 --yes\n\n# Update title, slug, status, or number\nbun scripts\u002Fadr.ts update source-first-loadouts --title \"Source-First Loadouts\"\nbun scripts\u002Fadr.ts update 013 --renumber 0013\nbun scripts\u002Fadr.ts update compile-target-selection --slug compile-targets\nbun scripts\u002Fadr.ts update compile-targets --status proposed --yes\n\n# Demote a numbered ADR back to drafts\nbun scripts\u002Fadr.ts demote 0014 --yes\n\n# Auto-fix common issues (number padding, cross-refs): preview, then apply\nbun scripts\u002Fadr.ts fix\nbun scripts\u002Fadr.ts fix --yes\n\n# Validate format and consistency\nbun scripts\u002Fadr.ts check\n\n# Regenerate decision maps and draft index\nbun scripts\u002Fadr.ts map\n```\n\nThe script handles file creation, git moves, title\u002Fslug\u002Fnumber updates, index rebuilding, decision-map generation for numbered and draft ADRs, and cross-reference updates.\n\nFor manual ADR management without the script, see [assets\u002Fadr-management.md](assets\u002Fadr-management.md).\n\n## Titles\n\n1. MUST use an H1 `#`.\n2. MUST lead with `ADR-NNNN` unless in `draft` status, which omits the number.\n3. MUST be descriptive enough to recall without opening the file. A good title makes a claim or names the durable decision, not just the topic.\n4. Prefer a single clear phrase over `Topic - Explanation` structure. A subtitle is a fallback when the short title cannot stand alone.\n5. A project-specific name is fine when the concept is established. A generic noun needs to say what the decision is.\n\nExamples:\n\n- Good: \"Source-First Loadouts\"\n- Good: \"Deterministic Target Renderings\"\n- Good: \"Compile Target Selection\"\n- Good: \"Unsupported Destination Must Be Provenanced\"\n- Avoid: \"Targets\"\n- Avoid: \"Config\"\n- Avoid: \"Codex and Claude\"\n\n## Locations\n\n- Numbered: `docs\u002Fadrs\u002FNNNN-slug.md`\n- Drafts: `docs\u002Fadrs\u002Fdrafts\u002FYYYYMMDD-slug.md`\n- Index: `docs\u002Fadrs\u002FREADME.md`\n- Template: `docs\u002Fadrs\u002Ftemplate.md`\n- Numbered decision map: `docs\u002Fadrs\u002Fdecision-map.json`\n- Draft decision map: `docs\u002Fadrs\u002Fdrafts\u002Fdecision-map.json`\n- Tenets: `docs\u002Fproject\u002Ftenets.md`\n\n## Statuses\n\n| Status | Location | Numbered | Meaning |\n| --- | --- | --- | --- |\n| `draft` | `docs\u002Fadrs\u002Fdrafts\u002F` | No | Decision proposed, open for discussion |\n| `proposed` | `docs\u002Fadrs\u002F` | Yes | Decision refined, ready for review |\n| `accepted` | `docs\u002Fadrs\u002F` | Yes | Decision approved, guides implementation |\n| `rejected` | `docs\u002Fadrs\u002F` | Yes | Decision considered and declined, with reasoning preserved |\n| `superseded` | `docs\u002Fadrs\u002F` | Yes | Replaced by a later ADR, with successor linked |\n\n## Frontmatter\n\n```yaml\n---\nid: NNNN\nslug: short-kebab-slug\ntitle: Title in Title Case\nstatus: proposed\ncreated: YYYY-MM-DD\nupdated: YYYY-MM-DD\nowners: ['[galligan](https:\u002F\u002Fgithub.com\u002Fgalligan)']\n# depends_on: [0, compile-target-selection]\n# amends: [0]\n---\n```\n\n`depends_on` accepts numbered ADR IDs and draft slugs (the filename without date prefix and `.md`). Use integers for numbered ADRs and slugs for drafts. The decision map renders these as graph edges.\n\n`amends` records a narrow change to one or more existing accepted decisions without replacing their historical body or status. Authors may declare it while the successor is a draft or numbered proposal, but targets must be accepted, numbered ADRs; draft slugs are not valid amendment identities. The relationship becomes active only when the successor is accepted. Decision maps preserve the authored `amends` list and derive the reciprocal `amended_by` list; never author `amended_by` directly.\n\nUse `supersedes` when the successor replaces the earlier decision as a whole. Supersession marks the predecessor `superseded` and records `superseded_by`; accepted later replacements, including recursively evidenced supersession chains, preserve previously accepted amendment history. A bare `status: superseded` edit or a proposed\u002Frejected replacement is not acceptance-history evidence. Amendment leaves predecessor source unchanged.\n\n## Content\n\n### Minimal ADR\n\n```markdown\n# ADR-NNNN: Descriptive Title\n\n## Context\n\nWhat problem, tension, or drift prompted the decision.\n\n## Decision\n\nWhat we chose and why. Include concrete source or output examples when they make the decision clearer.\n\n## Consequences\n\nWhat this enables, what it constrains, and what remains open.\n\n## References\n\n- [Tenets](..\u002Fproject\u002Ftenets.md) - governing design principles.\n```\n\n### Detailed ADR\n\n```markdown\n# ADR-NNNN: Descriptive Title\n\n## Context\n\n## Decision\n\nThe decision in one declarative sentence.\n\n### Focused Subsection\n\nUse subsections when the reasoning has distinct parts.\n\n## Non-Goals\n\nWhat this ADR is not trying to solve.\n\n## Consequences\n\n### Positive\n\nWhat this enables.\n\n### Tradeoffs\n\nKnown costs or constraints we accept.\n\n### Risks\n\nUncertain outcomes we are watching, with mitigation.\n\n## Non-Decisions\n\nExplicitly deferred decisions.\n\n## References\n```\n\n## Reference Format\n\n```markdown\nFor numbered ADRs:\n- [ADR-NNNN: Title](NNNN-slug.md) - one-line relationship\n\nFor draft ADRs:\n- ADR: Title (draft) - one-line relationship\n\nFor docs:\n- [Doc title](..\u002Fpath.md) - one-line relationship\n```\n\n## Style Guide\n\n### Voice\n\n- **Declarative, not tentative.** State the decision. If there is uncertainty, name it as a risk or non-decision.\n- **Conversational but precise.** Write like a sharp maintainer explaining what future agents and contributors must preserve.\n- **Active voice.** Skillset derives, renders, validates, rejects, and explains. Authors declare, opt out, and review.\n- **First person sparingly.** Use it in Context when grounding the problem in real experience. Drop it in Decision.\n\n### Structure\n\n- **Context tells a story.** Start with the pressure that made the decision necessary, not abstract background.\n- **Decision subsections start with a one-sentence thesis.** The first sentence should stand alone as a summary.\n- **Show the concrete failure.** Explain what breaks without the decision: duplicated config, silent target skips, fake portability, stale output, or unsafe activation.\n- **Code examples are primary evidence.** Source and generated-output snippets often explain the contract better than prose.\n- **Claims must be backed up.** Reference code, docs, ADRs, official docs, or live verification. If you cannot back a claim, soften or remove it.\n\n### Patterns To Use\n\n- \"This means:\" lists after a principle.\n- \"The test:\" heuristics that future agents can apply.\n- Good\u002FBad examples for contract shape.\n- Tables for structured tradeoffs.\n- Footnotes for external references.\n- Heading links for internal cross-references.\n\n### Patterns To Avoid\n\n- No hedging.\n- No restating the title.\n- No wall-of-text paragraphs.\n- No future benefit claims without present justification.\n- No \"as mentioned above\"; link directly.\n- No disparaging other tools or agent surfaces.\n- No numbered headings; descriptive headings preserve stable markdown anchors.\n\n### Consequences Style\n\n- Positive items are capabilities, not restatements.\n- Tradeoffs are honest. Name what we gave up.\n- \"What this does NOT decide\" is useful to future authors. Be specific and explain why it is deferred.\n\n### Vocabulary\n\nUse accepted Skillset vocabulary consistently:\n\n- `source`, not generated output, when discussing `.skillset\u002F`.\n- `target` or `provider`, not runtime, when discussing provider build destinations.\n- `render`\u002F`rendering`, not copying, when source intent becomes target-native output.\n- `rendered output`, not source truth, for generated provider files.\n- `compile.targets`, not bare `targets`, for root provider selection.\n- `compile.unsupportedDestination`, not silent fallback, for unsupported destination policy.\n- `provenance`, not comments, for lock\u002Fstatus evidence.\n\nRead `docs\u002Fproject\u002Ftenets.md` before writing. Every ADR must be consistent with the tenets.\n\n### Tone Calibration\n\nRead the draft aloud. If it sounds like a corporate design document, rewrite it. If it sounds like a blog post, tighten it. The target is the precision of a spec with the readability of a well-written README: someone who knows the domain deeply explaining the reasoning to someone who will have to live with the consequences.\n",{"name":5,"metadata":24,"description":7},{"version":25,"skillset.schema":26},"0.1.0","1","main","24800e02ed4e7150ea1bc7130c35603c98ea9da2",".cursor\u002Fskills\u002Fskillset-adrs",0,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset","https:\u002F\u002Fgithub.com\u002Foutfitter-dev","https:\u002F\u002Foutfitter.dev","Making things to help agents & devs make things.","2026-11-01 12:23:53",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add outfitter-dev\u002Fskillset --skill skillset-adrs",{"tool":42,"command":43},"bunx","bunx skills add outfitter-dev\u002Fskillset --skill skillset-adrs",{"tool":45,"command":46},"pnpm","pnpm dlx skills add outfitter-dev\u002Fskillset --skill skillset-adrs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002FSKILL.md",true,[50,56,62,66,70,74,78,82,86,90,94,98,102],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Fadr-management.md","ASSET","资产文件",3571,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fassets\u002Fadr-management.md",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"scripts\u002F__tests__\u002Famendments.test.ts","SCRIPT","脚本",25151,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002F__tests__\u002Famendments.test.ts",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"scripts\u002F__tests__\u002Fpromote-rewrite.test.ts",4691,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002F__tests__\u002Fpromote-rewrite.test.ts",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fadr.ts",21186,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Fadr.ts",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Flib\u002Famendments.ts",6285,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Famendments.ts",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Flib\u002Fcli.ts",3148,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Fcli.ts",{"path":79,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Flib\u002Fdecision-map.ts",12366,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Fdecision-map.ts",{"path":83,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Flib\u002Fdiscovery.ts",2765,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Fdiscovery.ts",{"path":87,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Flib\u002Ffrontmatter.ts",3449,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Ffrontmatter.ts",{"path":91,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Flib\u002Fgit.ts",323,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Fgit.ts",{"path":95,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Flib\u002Findex.ts",1867,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Findex.ts",{"path":99,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Flib\u002Fpaths.ts",779,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Fpaths.ts",{"path":103,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Flib\u002Freferences.ts",6576,"https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002F.cursor\u002Fskills\u002Fskillset-adrs\u002Fscripts\u002Flib\u002Freferences.ts",[107,115,122,129,136,143],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M758DGFEVX68J2QSQHSN08JB","use-skillset","Use the skillset compiler in a repo with skillset.yaml or a .skillset\u002F directory. Covers creating a workspace, adding skills, rules, agents, hooks, and plugins, building and checking Claude, Codex, and Cursor output, repairing stale or hand-edited generated files, recording changes, cutting releases, importing existing skills, and marketplaces. Use when asked to add a rule, record a change, cut a release, or fix generated output.","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Fplugins\u002Fskillset\u002Fskills\u002Fuse-skillset\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Fplugins\u002Fskillset\u002Fskills\u002Fuse-skillset\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M758DEEVQ3DGGJDRTMJKTPKP","broken","42","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Ffixtures\u002Fworkbench-invalid\u002F.skillset\u002Fskills\u002Fbroken\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M758DCJQYNK9E0DSKPD7JX1S","reference","Keep project references organized for review.","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Ffixtures\u002Fworkbench-clean\u002F.skillset\u002Fskills\u002Freference\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M758D9JB3PE4806K3J0TJFJN","portable-proof","Proves that generated Agent Skills are accepted by pinned external consumers.","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Ffixtures\u002Fstandards-adoption\u002F.skillset\u002Fskills\u002Fportable-proof\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M758D6ZT3PJVNPPZ5RF0BPM6","plugin-proof","Proves immediate-child skill fidelity inside an Agent Plugins package.","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Ffixtures\u002Fstandards-adoption\u002F.skillset\u002Fplugins\u002Fportable-proof\u002Fskills\u002Fplugin-proof\u002FSKILL.md",[],[],{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M758D46M0FV8A6EBG9K6NDN0","sink","Kitchen-sink skill exercising shared resources and custom resource mappings.","https:\u002F\u002Fgithub.com\u002Foutfitter-dev\u002Fskillset\u002Fblob\u002Fmain\u002Ffixtures\u002Fkitchen-sink\u002F.skillset\u002Fplugins\u002Fkitchen\u002Fskills\u002Fsink\u002FSKILL.md",[],[]]