[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD3906J6X4DNPNM14E8KA3":3,"skill-same:01M7FD3906J6X4DNPNM14E8KA3":67},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7FD3906J6X4DNPNM14E8KA3","decision-write",null,"Write, update, land, or supersede decision records. Use for resolved alternatives, missing rationale, reversed decisions, or record-file changes. Land finds and verifies the implementation; Review-only updates keep the current status.","l246804\u002Fdsh-pstack","l246804","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53589602?v=4","01M7FD2TFY24A2KKK55FSQWJ47","leihaohao","01M7FD2TGRS2ZCQ68BRY93D89D",23,"MIT","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: decision-write\ndescription: Write, update, land, or supersede decision records. Use for resolved alternatives, missing rationale, reversed decisions, or record-file changes. Land finds and verifies the implementation; Review-only updates keep the current status.\n---\n\n# Write or update a decision record\n\nDeliver one settled choice as a verified record and evidence report. All record edits go through this skill; `decision-audit` only reports.\n\n## Entry rule\n\nUse this procedure for every change to `Status`, `Implemented-by`, `Superseded-by`, `Review`, body, or links. If it cannot run, stop and report; this rule overrides `\u003Cdir>\u002FAGENTS.md` conventions permitting direct edits.\n\n## Locate the records\n\nResolve `\u003Cdir>` in this order:\n\n1. Use a caller-supplied record or directory path.\n2. Otherwise, resolve the decision pointer in root `AGENTS.md` under `## Project docs` when it points to an existing `\u003Cdir>\u002FAGENTS.md`.\n3. Otherwise, inspect `docs\u002Fdecisions\u002F`, `docs\u002Fadr\u002F`, and `doc\u002Fadr\u002F`.\n\nUse the selected directory, follow its naming convention, and read its `AGENTS.md` and `README.md` conventions when present. If several candidates remain, ask which is current and wait. If none exists, report that no decision directory was found, suggest `\u002Fsetup-project-docs`, and stop.\n\n`AGENTS.md` and `README.md` are conventions, not records; exclude both from searches, classification, and updates.\n\n## Choose the mode\n\n- **Draft:** no record owns this decision, a new record replaces an old one, or an existing record needs substantive body or relationship updates. Duplicate and overlapping dispositions stay in Draft; explicit status-field updates use Land. Do steps 1–5, present the approval gate in step 6, then write only after confirmation and report with step 7.\n- **Land:** the user explicitly asks to mark an existing record `accepted` or update its status fields. Read the full target record, then do steps 4, 5, and 7. A record path plus `accepted` is sufficient input; never enter Land autonomously. Without a path, list records whose `Scope` matches the landed change and ask which to update. For a Review-only update, preserve `Status` and `Implemented-by`, skip steps 4 and 5, and report with step 7.\n\n## 1. Establish the choice\n\nObtain all three from the change and discussion; ask only about missing items and wait:\n\n- **Goal:** the problem this decision answers.\n- **Constraint:** the boundary that eliminates an option.\n- **Alternative:** an option actually rejected, or the explicit fact that only one candidate was considered.\n\n## 2. Find related records\n\nSearch for distinctive terms from the topic, affected modules, and alternatives:\n\n```bash\ngrep -ril --exclude=AGENTS.md --exclude=README.md \\\n  -e \"\u003Ckeyword-1>\" -e \"\u003Ckeyword-2>\" \u003Cdir>\u002F*.md\n```\n\nRead each hit through its first `## ` heading; read the body only when the header cannot distinguish its disposition or cannot supply the content needed for an update. Tighten broad searches rather than reading the whole directory. Classify every hit:\n\n- **Duplicate:** the existing record owns this decision. Update it instead of writing a second one.\n- **Replaced:** draft the new record and cross-link both records. Include the old record's supersession in the approval gate.\n- **Overlapping:** keep both, cross-link them, and reconcile changed facts.\n- **Unrelated:** leave it unchanged.\n- **Unresolved:** carry the relationship and human question into the report.\n\nThis step is complete when every hit has a disposition and every resulting edit is explicit.\n\n## 3. Draft the record\n\nFollow `\u003Cdir>\u002FAGENTS.md`, including heading language. In its absence, use:\n\n```markdown\n# Decision: \u003Cone-line title>\n\nStatus: proposed | accepted | superseded\nDate: YYYY-MM-DD\nScope: \u003Cglob>[, \u003Cglob>...]\nImplemented-by: \u003CPR #N | commit:SHA | ->\nReview: YYYY-MM-DD\nSuperseded-by: \u003Crecord path> — \u003Cone-line reason>   (only when Status is superseded)\n\n## Background\n## Decision\n## Alternatives\n## Consequences\n```\n\nWrite `Background` independently of the chosen solution. For an accepted record, write `Decision` in the present tense. Give every considered alternative its own paragraph and rejection reason; when there was only one candidate, state that fact.\n\n## 4. Set status and verify the anchor\n\n`Status` and `Implemented-by` are one pair. Select the row supported by evidence and write both fields together:\n\n| Evidence | Status | Implemented-by |\n|---|---|---|\n| No verified landing anchor | `proposed` | `-` |\n| `PR #N` is `MERGED` | `accepted` | `PR #N` |\n| `commit:SHA` is an ancestor of the default branch | `accepted` | `commit:SHA` |\n| Confirmed record-only exception | `accepted` | `commit:\u003Crecord-commit>` |\n| Replaced by a newer draft | `superseded` | Keep the existing value |\n\nA new record stays `proposed` until it lands. `Implemented-by` identifies the implementing change, including an earlier implementation for a retrospective record; a record-only commit requires the confirmed exception. Prefer a merged PR in a squash-merged repository.\n\nFor Land without an anchor, or the record-only exception, read [Find and verify the implementation](references\u002Fland.md) before editing. For any other proposed anchor, use that reference's verification procedure without its discovery steps.\n\nResolve `\u003Cbase>` as the repository's default branch and report the selected ref. Verify every anchor. In Draft, unavailable evidence or an unresolved base leaves a new record `proposed` + `-`; in Land, stop and report without editing. If an existing `accepted` record's anchor fails verification, stop and report it rather than silently demoting it. Change only fields required by evidence; advancing `Review` alone leaves status unchanged.\n\nWhen a new draft replaces an old record, set the old record to `superseded` in the same approved edit set, even when it was `accepted`. Keep its body and anchor, add the cross-link, and write `Superseded-by: \u003Cnew record path> — \u003Cone-line reason>` below `Review`. Ask for a missing reason and wait. A `proposed` old record keeps `Implemented-by: -`.\n\n## 5. Check scope covers the change\n\nUse [Match Scope paths](references\u002Fscope.md) for every glob\u002Fpath check, including anchor discovery in Land. Use caller-supplied `scope` paths when present. For Land with a verified implementing change, list its paths with:\n\n```bash\ngh pr view N --json files --jq '.files[].path'\ngit show --pretty=format: --name-only SHA\n```\n\nFor the confirmed record-only fallback, skip this check and report the exception. For every other mode, collect base-relative commits and uncommitted changes:\n\n```bash\ngit diff --name-only \"$(git merge-base HEAD \u003Cbase>)\"..HEAD\ngit status --porcelain=v1 --untracked-files=all\n```\n\nDecode `git status` paths, including the destination of a rename. Require each new or updated record to match at least one selected path to a `Scope` glob. When none matches, ask whether to widen the glob or omit the record. Record matched paths for the report.\n\n## 6. Draft approval gate\n\nFor every Draft write, including a Duplicate update, present the complete resulting content of every new or updated record and every related-record disposition. Include each proposed supersession with its `Superseded-by` path and reason. Request explicit confirmation and wait. After confirmation, apply exactly the approved edits; a declined draft leaves every file unchanged.\n\n## 7. Report\n\nWhen root `AGENTS.md` has no resolving decision pointer for the selected `\u003Cdir>`, suggest `\u002Fsetup-project-docs` to register it. Account for every search hit, changed record, relationship, anchor verification, scope match, and unresolved question. A `proposed` record awaiting landing needs a Land update after merge. Name any discovered implementation and its changed paths; mark a record-only anchor as a confirmed exception. Include every `Superseded-by` path and reason.\n\n```text\nRecord: docs\u002Fdecisions\u002F2026-10-27-use-postgres.md\nStatus: accepted\nRelated: 2026-03-02-mysql-setup.md -> overlapping, cross-linked\nAnchor: PR #412 -> MERGED (gh pr view 412 --json state,files)\nScope: src\u002Fdb\u002F** matched src\u002Fdb\u002Fclient.ts\nOpen: none\n```\n","# Write or update a decision record\n\nDeliver one settled choice as a verified record and evidence report. All record edits go through this skill; `decision-audit` only reports.\n\n## Entry rule\n\nUse this procedure for every change to `Status`, `Implemented-by`, `Superseded-by`, `Review`, body, or links. If it cannot run, stop and report; this rule overrides `\u003Cdir>\u002FAGENTS.md` conventions permitting direct edits.\n\n## Locate the records\n\nResolve `\u003Cdir>` in this order:\n\n1. Use a caller-supplied record or directory path.\n2. Otherwise, resolve the decision pointer in root `AGENTS.md` under `## Project docs` when it points to an existing `\u003Cdir>\u002FAGENTS.md`.\n3. Otherwise, inspect `docs\u002Fdecisions\u002F`, `docs\u002Fadr\u002F`, and `doc\u002Fadr\u002F`.\n\nUse the selected directory, follow its naming convention, and read its `AGENTS.md` and `README.md` conventions when present. If several candidates remain, ask which is current and wait. If none exists, report that no decision directory was found, suggest `\u002Fsetup-project-docs`, and stop.\n\n`AGENTS.md` and `README.md` are conventions, not records; exclude both from searches, classification, and updates.\n\n## Choose the mode\n\n- **Draft:** no record owns this decision, a new record replaces an old one, or an existing record needs substantive body or relationship updates. Duplicate and overlapping dispositions stay in Draft; explicit status-field updates use Land. Do steps 1–5, present the approval gate in step 6, then write only after confirmation and report with step 7.\n- **Land:** the user explicitly asks to mark an existing record `accepted` or update its status fields. Read the full target record, then do steps 4, 5, and 7. A record path plus `accepted` is sufficient input; never enter Land autonomously. Without a path, list records whose `Scope` matches the landed change and ask which to update. For a Review-only update, preserve `Status` and `Implemented-by`, skip steps 4 and 5, and report with step 7.\n\n## 1. Establish the choice\n\nObtain all three from the change and discussion; ask only about missing items and wait:\n\n- **Goal:** the problem this decision answers.\n- **Constraint:** the boundary that eliminates an option.\n- **Alternative:** an option actually rejected, or the explicit fact that only one candidate was considered.\n\n## 2. Find related records\n\nSearch for distinctive terms from the topic, affected modules, and alternatives:\n\n```bash\ngrep -ril --exclude=AGENTS.md --exclude=README.md \\\n  -e \"\u003Ckeyword-1>\" -e \"\u003Ckeyword-2>\" \u003Cdir>\u002F*.md\n```\n\nRead each hit through its first `## ` heading; read the body only when the header cannot distinguish its disposition or cannot supply the content needed for an update. Tighten broad searches rather than reading the whole directory. Classify every hit:\n\n- **Duplicate:** the existing record owns this decision. Update it instead of writing a second one.\n- **Replaced:** draft the new record and cross-link both records. Include the old record's supersession in the approval gate.\n- **Overlapping:** keep both, cross-link them, and reconcile changed facts.\n- **Unrelated:** leave it unchanged.\n- **Unresolved:** carry the relationship and human question into the report.\n\nThis step is complete when every hit has a disposition and every resulting edit is explicit.\n\n## 3. Draft the record\n\nFollow `\u003Cdir>\u002FAGENTS.md`, including heading language. In its absence, use:\n\n```markdown\n# Decision: \u003Cone-line title>\n\nStatus: proposed | accepted | superseded\nDate: YYYY-MM-DD\nScope: \u003Cglob>[, \u003Cglob>...]\nImplemented-by: \u003CPR #N | commit:SHA | ->\nReview: YYYY-MM-DD\nSuperseded-by: \u003Crecord path> — \u003Cone-line reason>   (only when Status is superseded)\n\n## Background\n## Decision\n## Alternatives\n## Consequences\n```\n\nWrite `Background` independently of the chosen solution. For an accepted record, write `Decision` in the present tense. Give every considered alternative its own paragraph and rejection reason; when there was only one candidate, state that fact.\n\n## 4. Set status and verify the anchor\n\n`Status` and `Implemented-by` are one pair. Select the row supported by evidence and write both fields together:\n\n| Evidence | Status | Implemented-by |\n|---|---|---|\n| No verified landing anchor | `proposed` | `-` |\n| `PR #N` is `MERGED` | `accepted` | `PR #N` |\n| `commit:SHA` is an ancestor of the default branch | `accepted` | `commit:SHA` |\n| Confirmed record-only exception | `accepted` | `commit:\u003Crecord-commit>` |\n| Replaced by a newer draft | `superseded` | Keep the existing value |\n\nA new record stays `proposed` until it lands. `Implemented-by` identifies the implementing change, including an earlier implementation for a retrospective record; a record-only commit requires the confirmed exception. Prefer a merged PR in a squash-merged repository.\n\nFor Land without an anchor, or the record-only exception, read [Find and verify the implementation](references\u002Fland.md) before editing. For any other proposed anchor, use that reference's verification procedure without its discovery steps.\n\nResolve `\u003Cbase>` as the repository's default branch and report the selected ref. Verify every anchor. In Draft, unavailable evidence or an unresolved base leaves a new record `proposed` + `-`; in Land, stop and report without editing. If an existing `accepted` record's anchor fails verification, stop and report it rather than silently demoting it. Change only fields required by evidence; advancing `Review` alone leaves status unchanged.\n\nWhen a new draft replaces an old record, set the old record to `superseded` in the same approved edit set, even when it was `accepted`. Keep its body and anchor, add the cross-link, and write `Superseded-by: \u003Cnew record path> — \u003Cone-line reason>` below `Review`. Ask for a missing reason and wait. A `proposed` old record keeps `Implemented-by: -`.\n\n## 5. Check scope covers the change\n\nUse [Match Scope paths](references\u002Fscope.md) for every glob\u002Fpath check, including anchor discovery in Land. Use caller-supplied `scope` paths when present. For Land with a verified implementing change, list its paths with:\n\n```bash\ngh pr view N --json files --jq '.files[].path'\ngit show --pretty=format: --name-only SHA\n```\n\nFor the confirmed record-only fallback, skip this check and report the exception. For every other mode, collect base-relative commits and uncommitted changes:\n\n```bash\ngit diff --name-only \"$(git merge-base HEAD \u003Cbase>)\"..HEAD\ngit status --porcelain=v1 --untracked-files=all\n```\n\nDecode `git status` paths, including the destination of a rename. Require each new or updated record to match at least one selected path to a `Scope` glob. When none matches, ask whether to widen the glob or omit the record. Record matched paths for the report.\n\n## 6. Draft approval gate\n\nFor every Draft write, including a Duplicate update, present the complete resulting content of every new or updated record and every related-record disposition. Include each proposed supersession with its `Superseded-by` path and reason. Request explicit confirmation and wait. After confirmation, apply exactly the approved edits; a declined draft leaves every file unchanged.\n\n## 7. Report\n\nWhen root `AGENTS.md` has no resolving decision pointer for the selected `\u003Cdir>`, suggest `\u002Fsetup-project-docs` to register it. Account for every search hit, changed record, relationship, anchor verification, scope match, and unresolved question. A `proposed` record awaiting landing needs a Land update after merge. Name any discovered implementation and its changed paths; mark a record-only anchor as a confirmed exception. Include every `Superseded-by` path and reason.\n\n```text\nRecord: docs\u002Fdecisions\u002F2026-10-27-use-postgres.md\nStatus: accepted\nRelated: 2026-03-02-mysql-setup.md -> overlapping, cross-linked\nAnchor: PR #412 -> MERGED (gh pr view 412 --json state,files)\nScope: src\u002Fdb\u002F** matched src\u002Fdb\u002Fclient.ts\nOpen: none\n```\n",{"name":5,"description":7},"main","df33da1bb4942fbd2761c305edb3785093ec1055",".agents\u002Fskills\u002Fdecision-write",4,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack","https:\u002F\u002Fgithub.com\u002Fl246804","2026-11-15 16:09:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add l246804\u002Fdsh-pstack --skill decision-write",{"tool":37,"command":38},"bunx","bunx skills add l246804\u002Fdsh-pstack --skill decision-write",{"tool":40,"command":41},"pnpm","pnpm dlx skills add l246804\u002Fdsh-pstack --skill decision-write","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fland.md","REFERENCE","参考文档",3417,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002Freferences\u002Fland.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fland.zh.md",3153,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002Freferences\u002Fland.zh.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fscope.md",1502,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002Freferences\u002Fscope.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fscope.zh.md",1426,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002Freferences\u002Fscope.zh.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"SKILL.zh.md",7677,"https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdecision-write\u002FSKILL.zh.md",[68,75,82,87,94,101],{"skillNo":69,"name":70,"nameZh":6,"description":71,"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},"01M7FDC7PA7ACJ95HW5T1N9ZJ3","setup-project-docs","Bootstrap architecture, glossary, decision-record conventions, and root agent-doc pointers; rerun to fill approved gaps.","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fauthored\u002Fsetup-project-docs\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FDC35BXG4PW3HG16BXF5FG","docs-drift","Audit living project documentation for drift and redundancy; repair approved findings.","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fauthored\u002Fdocs-drift\u002FSKILL.md",[],[],{"skillNo":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M7FDBZ7PP5T1V4Q1MEP95BGM","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fauthored\u002Fdecision-write\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7FDBVXYSHCB2E52HKS2TH2E","decision-audit","Read-only audit of decision records for a PR, local changes, or the whole repository. Report routing, status, scope, anchor, supersession, and overdue-review findings with command evidence.","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002Fauthored\u002Fdecision-audit\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FDBSF0V6HTFHD5PHDC6BAM","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7FDBQPY2F8PSNJKTGZ6AYD6","retro","Conduct a retrospective on a coding session.","https:\u002F\u002Fgithub.com\u002Fl246804\u002Fdsh-pstack\u002Fblob\u002Fmain\u002Fskills\u002F.agents\u002Fskills\u002Fretro\u002FSKILL.md",[],[]]