[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K595XT5WRCEAS2MYHQ20F7":3,"skill-same:01M6K595XT5WRCEAS2MYHQ20F7":69},{"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":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6K595XT5WRCEAS2MYHQ20F7","release",null,"Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.","kangnam7654\u002Fstapler","kangnam7654","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F70181315?v=4","01M6K57VNJ3PFBHBRQNBTYTSJM","Kangnam Kim","01M6K57VT1NK9FARCSD23JGTMY",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"versioning","follow-up","full","leadership","across","coordinate","up","smoke","use","testing","ship","engineering","npm","announcement","verification","paperclip","github","2026-11-10 10:12:30",false,"---\nname: release\ndescription: >\n  Coordinate a full Paperclip release across engineering verification, npm,\n  GitHub, smoke testing, and announcement follow-up. Use when leadership asks\n  to ship a release, not merely to discuss versioning.\n---\n\n# Release Coordination Skill\n\nRun the full Paperclip maintainer release workflow, not just an npm publish.\n\nThis skill coordinates:\n\n- stable changelog drafting via `release-changelog`\n- canary verification and publish status from `master`\n- Docker smoke testing via `scripts\u002Fdocker-onboard-smoke.sh`\n- manual stable promotion from a chosen source ref\n- GitHub Release creation\n- website \u002F announcement follow-up tasks\n\n## Trigger\n\nUse this skill when leadership asks for:\n\n- \"do a release\"\n- \"ship the release\"\n- \"promote this canary to stable\"\n- \"cut the stable release\"\n\n## Preconditions\n\nBefore proceeding, verify all of the following:\n\n1. `.agents\u002Fskills\u002Frelease-changelog\u002FSKILL.md` exists and is usable.\n2. The repo working tree is clean, including untracked files.\n3. There is at least one canary or candidate commit since the last stable tag.\n4. The candidate SHA has passed the verification gate or is about to.\n5. If manifests changed, the CI-owned `pnpm-lock.yaml` refresh is already merged on `master`.\n6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency\u002Fmanual use.\n7. If running through Paperclip, you have issue context for status updates and follow-up task creation.\n\nIf any precondition fails, stop and report the blocker.\n\n## Inputs\n\nCollect these inputs up front:\n\n- whether the target is a canary check or a stable promotion\n- the candidate `source_ref` for stable\n- whether the stable run is dry-run or live\n- release issue \u002F company context for website and announcement follow-up\n\n## Step 0 — Release Model\n\nPaperclip now uses a commit-driven release model:\n\n1. every push to `master` publishes a canary automatically\n2. canaries use `YYYY.MDD.P-canary.N`\n3. stable releases use `YYYY.MDD.P`\n4. the middle slot is `MDD`, where `M` is the UTC month and `DD` is the zero-padded UTC day\n5. the stable patch slot increments when more than one stable ships on the same UTC date\n6. stable releases are manually promoted from a chosen tested commit or canary source commit\n7. only stable releases get `releases\u002FvYYYY.MDD.P.md`, git tag `vYYYY.MDD.P`, and a GitHub Release\n\nCritical consequences:\n\n- do not use release branches as the default path\n- do not derive major\u002Fminor\u002Fpatch bumps\n- do not create canary changelog files\n- do not create canary GitHub Releases\n\n## Step 1 — Choose the Candidate\n\nFor canary validation:\n\n- inspect the latest successful canary run on `master`\n- record the canary version and source SHA\n\nFor stable promotion:\n\n1. choose the tested source ref\n2. confirm it is the exact SHA you want to promote\n3. resolve the target stable version with `.\u002Fscripts\u002Frelease.sh stable --date YYYY-MM-DD --print-version`\n\nUseful commands:\n\n```bash\ngit tag --list 'v*' --sort=-version:refname | head -1\ngit log --oneline --no-merges\nnpm view paperclipai@canary version\n```\n\n## Step 2 — Draft the Stable Changelog\n\nStable changelog files live at:\n\n- `releases\u002FvYYYY.MDD.P.md`\n\nInvoke `release-changelog` and generate or update the stable notes only.\n\nRules:\n\n- review the draft with a human before publish\n- preserve manual edits if the file already exists\n- keep the filename stable-only\n- do not create a canary changelog file\n\n## Step 3 — Verify the Candidate SHA\n\nRun the standard gate:\n\n```bash\npnpm -r typecheck\npnpm test:run\npnpm build\n```\n\nIf the GitHub release workflow will run the publish, it can rerun this gate. Still report local status if you checked it.\n\nFor PRs that touch release logic, the repo also runs a canary release dry-run in CI. That is a release-specific guard, not a substitute for the standard gate.\n\n## Step 4 — Validate the Canary\n\nThe normal canary path is automatic from `master` via:\n\n- `.github\u002Fworkflows\u002Frelease.yml`\n\nConfirm:\n\n1. verification passed\n2. npm canary publish succeeded\n3. git tag `canary\u002FvYYYY.MDD.P-canary.N` exists\n\nUseful checks:\n\n```bash\nnpm view paperclipai@canary version\ngit tag --list 'canary\u002Fv*' --sort=-version:refname | head -5\n```\n\n## Step 5 — Smoke Test the Canary\n\nRun:\n\n```bash\nPAPERCLIPAI_VERSION=canary .\u002Fscripts\u002Fdocker-onboard-smoke.sh\n```\n\nUseful isolated variant:\n\n```bash\nHOST_PORT=3232 DATA_DIR=.\u002Fdata\u002Frelease-smoke-canary PAPERCLIPAI_VERSION=canary .\u002Fscripts\u002Fdocker-onboard-smoke.sh\n```\n\nConfirm:\n\n1. install succeeds\n2. onboarding completes without crashes\n3. the server boots\n4. the UI loads\n5. basic company creation and dashboard load work\n\nIf smoke testing fails:\n\n- stop the stable release\n- fix the issue on `master`\n- wait for the next automatic canary\n- rerun smoke testing\n\n## Step 6 — Preview or Publish Stable\n\nThe normal stable path is manual `workflow_dispatch` on:\n\n- `.github\u002Fworkflows\u002Frelease.yml`\n\nInputs:\n\n- `source_ref`\n- `stable_date`\n- `dry_run`\n\nBefore live stable:\n\n1. resolve the target stable version with `.\u002Fscripts\u002Frelease.sh stable --date YYYY-MM-DD --print-version`\n2. ensure `releases\u002FvYYYY.MDD.P.md` exists on the source ref\n3. run the stable workflow in dry-run mode first when practical\n4. then run the real stable publish\n\nThe stable workflow:\n\n- re-verifies the exact source ref\n- computes the next stable patch slot for the chosen UTC date\n- publishes `YYYY.MDD.P` under dist-tag `latest`\n- creates git tag `vYYYY.MDD.P`\n- creates or updates the GitHub Release from `releases\u002FvYYYY.MDD.P.md`\n\nLocal emergency\u002Fmanual commands:\n\n```bash\n.\u002Fscripts\u002Frelease.sh stable --dry-run\n.\u002Fscripts\u002Frelease.sh stable\ngit push public-gh refs\u002Ftags\u002FvYYYY.MDD.P\n.\u002Fscripts\u002Fcreate-github-release.sh YYYY.MDD.P\n```\n\n## Step 7 — Finish the Other Surfaces\n\nCreate or verify follow-up work for:\n\n- website changelog publishing\n- launch post \u002F social announcement\n- release summary in Paperclip issue context\n\nThese should reference the stable release, not the canary.\n\n## Failure Handling\n\nIf the canary is bad:\n\n- publish another canary, do not ship stable\n\nIf stable npm publish succeeds but tag push or GitHub release creation fails:\n\n- fix the git\u002FGitHub issue immediately from the same release result\n- do not republish the same version\n\nIf `latest` is bad after stable publish:\n\n```bash\n.\u002Fscripts\u002Frollback-latest.sh \u003Clast-good-version>\n```\n\nThen fix forward with a new stable release.\n\n## Output\n\nWhen the skill completes, provide:\n\n- candidate SHA and tested canary version, if relevant\n- stable version, if promoted\n- verification status\n- npm status\n- smoke-test status\n- git tag \u002F GitHub Release status\n- website \u002F announcement follow-up status\n- rollback recommendation if anything is still partially complete\n","# Release Coordination Skill\n\nRun the full Paperclip maintainer release workflow, not just an npm publish.\n\nThis skill coordinates:\n\n- stable changelog drafting via `release-changelog`\n- canary verification and publish status from `master`\n- Docker smoke testing via `scripts\u002Fdocker-onboard-smoke.sh`\n- manual stable promotion from a chosen source ref\n- GitHub Release creation\n- website \u002F announcement follow-up tasks\n\n## Trigger\n\nUse this skill when leadership asks for:\n\n- \"do a release\"\n- \"ship the release\"\n- \"promote this canary to stable\"\n- \"cut the stable release\"\n\n## Preconditions\n\nBefore proceeding, verify all of the following:\n\n1. `.agents\u002Fskills\u002Frelease-changelog\u002FSKILL.md` exists and is usable.\n2. The repo working tree is clean, including untracked files.\n3. There is at least one canary or candidate commit since the last stable tag.\n4. The candidate SHA has passed the verification gate or is about to.\n5. If manifests changed, the CI-owned `pnpm-lock.yaml` refresh is already merged on `master`.\n6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency\u002Fmanual use.\n7. If running through Paperclip, you have issue context for status updates and follow-up task creation.\n\nIf any precondition fails, stop and report the blocker.\n\n## Inputs\n\nCollect these inputs up front:\n\n- whether the target is a canary check or a stable promotion\n- the candidate `source_ref` for stable\n- whether the stable run is dry-run or live\n- release issue \u002F company context for website and announcement follow-up\n\n## Step 0 — Release Model\n\nPaperclip now uses a commit-driven release model:\n\n1. every push to `master` publishes a canary automatically\n2. canaries use `YYYY.MDD.P-canary.N`\n3. stable releases use `YYYY.MDD.P`\n4. the middle slot is `MDD`, where `M` is the UTC month and `DD` is the zero-padded UTC day\n5. the stable patch slot increments when more than one stable ships on the same UTC date\n6. stable releases are manually promoted from a chosen tested commit or canary source commit\n7. only stable releases get `releases\u002FvYYYY.MDD.P.md`, git tag `vYYYY.MDD.P`, and a GitHub Release\n\nCritical consequences:\n\n- do not use release branches as the default path\n- do not derive major\u002Fminor\u002Fpatch bumps\n- do not create canary changelog files\n- do not create canary GitHub Releases\n\n## Step 1 — Choose the Candidate\n\nFor canary validation:\n\n- inspect the latest successful canary run on `master`\n- record the canary version and source SHA\n\nFor stable promotion:\n\n1. choose the tested source ref\n2. confirm it is the exact SHA you want to promote\n3. resolve the target stable version with `.\u002Fscripts\u002Frelease.sh stable --date YYYY-MM-DD --print-version`\n\nUseful commands:\n\n```bash\ngit tag --list 'v*' --sort=-version:refname | head -1\ngit log --oneline --no-merges\nnpm view paperclipai@canary version\n```\n\n## Step 2 — Draft the Stable Changelog\n\nStable changelog files live at:\n\n- `releases\u002FvYYYY.MDD.P.md`\n\nInvoke `release-changelog` and generate or update the stable notes only.\n\nRules:\n\n- review the draft with a human before publish\n- preserve manual edits if the file already exists\n- keep the filename stable-only\n- do not create a canary changelog file\n\n## Step 3 — Verify the Candidate SHA\n\nRun the standard gate:\n\n```bash\npnpm -r typecheck\npnpm test:run\npnpm build\n```\n\nIf the GitHub release workflow will run the publish, it can rerun this gate. Still report local status if you checked it.\n\nFor PRs that touch release logic, the repo also runs a canary release dry-run in CI. That is a release-specific guard, not a substitute for the standard gate.\n\n## Step 4 — Validate the Canary\n\nThe normal canary path is automatic from `master` via:\n\n- `.github\u002Fworkflows\u002Frelease.yml`\n\nConfirm:\n\n1. verification passed\n2. npm canary publish succeeded\n3. git tag `canary\u002FvYYYY.MDD.P-canary.N` exists\n\nUseful checks:\n\n```bash\nnpm view paperclipai@canary version\ngit tag --list 'canary\u002Fv*' --sort=-version:refname | head -5\n```\n\n## Step 5 — Smoke Test the Canary\n\nRun:\n\n```bash\nPAPERCLIPAI_VERSION=canary .\u002Fscripts\u002Fdocker-onboard-smoke.sh\n```\n\nUseful isolated variant:\n\n```bash\nHOST_PORT=3232 DATA_DIR=.\u002Fdata\u002Frelease-smoke-canary PAPERCLIPAI_VERSION=canary .\u002Fscripts\u002Fdocker-onboard-smoke.sh\n```\n\nConfirm:\n\n1. install succeeds\n2. onboarding completes without crashes\n3. the server boots\n4. the UI loads\n5. basic company creation and dashboard load work\n\nIf smoke testing fails:\n\n- stop the stable release\n- fix the issue on `master`\n- wait for the next automatic canary\n- rerun smoke testing\n\n## Step 6 — Preview or Publish Stable\n\nThe normal stable path is manual `workflow_dispatch` on:\n\n- `.github\u002Fworkflows\u002Frelease.yml`\n\nInputs:\n\n- `source_ref`\n- `stable_date`\n- `dry_run`\n\nBefore live stable:\n\n1. resolve the target stable version with `.\u002Fscripts\u002Frelease.sh stable --date YYYY-MM-DD --print-version`\n2. ensure `releases\u002FvYYYY.MDD.P.md` exists on the source ref\n3. run the stable workflow in dry-run mode first when practical\n4. then run the real stable publish\n\nThe stable workflow:\n\n- re-verifies the exact source ref\n- computes the next stable patch slot for the chosen UTC date\n- publishes `YYYY.MDD.P` under dist-tag `latest`\n- creates git tag `vYYYY.MDD.P`\n- creates or updates the GitHub Release from `releases\u002FvYYYY.MDD.P.md`\n\nLocal emergency\u002Fmanual commands:\n\n```bash\n.\u002Fscripts\u002Frelease.sh stable --dry-run\n.\u002Fscripts\u002Frelease.sh stable\ngit push public-gh refs\u002Ftags\u002FvYYYY.MDD.P\n.\u002Fscripts\u002Fcreate-github-release.sh YYYY.MDD.P\n```\n\n## Step 7 — Finish the Other Surfaces\n\nCreate or verify follow-up work for:\n\n- website changelog publishing\n- launch post \u002F social announcement\n- release summary in Paperclip issue context\n\nThese should reference the stable release, not the canary.\n\n## Failure Handling\n\nIf the canary is bad:\n\n- publish another canary, do not ship stable\n\nIf stable npm publish succeeds but tag push or GitHub release creation fails:\n\n- fix the git\u002FGitHub issue immediately from the same release result\n- do not republish the same version\n\nIf `latest` is bad after stable publish:\n\n```bash\n.\u002Fscripts\u002Frollback-latest.sh \u003Clast-good-version>\n```\n\nThen fix forward with a new stable release.\n\n## Output\n\nWhen the skill completes, provide:\n\n- candidate SHA and tested canary version, if relevant\n- stable version, if promoted\n- verification status\n- npm status\n- smoke-test status\n- git tag \u002F GitHub Release status\n- website \u002F announcement follow-up status\n- rollback recommendation if anything is still partially complete\n",{"name":5,"description":7},"main","83f8367d44a638ab2f3cefa0eb4f2e55cf128411",".agents\u002Fskills\u002Frelease",0,"https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler","https:\u002F\u002Fgithub.com\u002Fkangnam7654","kangnam7654.github.io","AI Engineer","2026-04-21 01:56:05",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add kangnam7654\u002Fstapler --skill release",{"tool":61,"command":62},"bunx","bunx skills add kangnam7654\u002Fstapler --skill release",{"tool":64,"command":65},"pnpm","pnpm dlx skills add kangnam7654\u002Fstapler --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frelease\u002FSKILL.md",true,[],[70,96,120,144,167,174],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":41},"01M6K5BEQC9HE20WYMESKVC8FS","para-memory-files","File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns. Also handles planning files, memory decay, weekly synthesis, and recall via qmd. Trigger on any memory operation: saving facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, or managing plans.","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fskills\u002Fpara-memory-files\u002FSKILL.md",[],[77,78,79,80,81,82,83,84,85,86,28,87,88,89,90,91,92,93,94,95],"para","para memory files","files","memory","patterns","weekly","past","you","memory system","as","organize","weekly synthesis","context","knowledge","knowledge graph","graph","update","notes","writing",{"skillNo":97,"name":39,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":41},"01M6K5BAA23289JDBBR8R1WSJN","Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fskills\u002Fpaperclip\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[39,105,84,106,107,108,29,109,110,111,112,113,114,115,116,117,118,119,95,93],"only","domain","update task","plane","do","api endpoint","code","delegate","work","coordination","api","endpoint","for","tasks","status",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":41},"01M6K5B48SE9AFAM77SEPJ8R5K","paperclip-create-plugin","Create new Paperclip plugins with the current alpha SDK\u002Fruntime. Use when scaffolding a plugin package, adding a new example plugin, or updating plugin authoring docs. Covers the supported worker\u002FUI surface, route conventions, scaffold flow, and verification steps.","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fskills\u002Fpaperclip-create-plugin\u002FSKILL.md",[],[127,128,129,39,130,131,132,133,134,135,136,137,138,139,32,140,141,142,143,38],"create plugin","plugin","create","paperclip create plugin","worker","sdk","route","with","authoring","runtime","scaffolding","plugin authoring","example","flow","alpha","plugins","package",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":41},"01M6K5AZ86H1RMTNDC5XCYCEVE","paperclip-create-agent","Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt\u002Fconfig, and submit a hire request.","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fskills\u002Fpaperclip-create-agent\u002FSKILL.md",[150],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},[152,39,129,153,154,155,156,84,134,157,158,159,160,161,162,32,163,164,165,166],"paperclip create agent","create agent","new agent","Existing","inspect","hire","compare","adapter","submit","draft","options","prompt","Hiring","governance","config",{"skillNo":168,"name":169,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":41},"01M6K5AVNJ2YWX6A4YB8RM0VNW","Workspace Skill","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fnative\u002Fskills-scanner\u002Ftests\u002Ffixtures\u002Fws_project_root\u002FSKILL.md",[],[169,173],"workspace",{"skillNo":175,"name":176,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":41},"01M6K5AQYTEY5GYM79GYVYKZDG","Inline Metadata Skill","https:\u002F\u002Fgithub.com\u002Fkangnam7654\u002Fstapler\u002Fblob\u002Fmain\u002Fnative\u002Fskills-scanner\u002Ftests\u002Ffixtures\u002Fws_inline_yaml\u002FSKILL.md",[],[176,180,181,39,40],"inline","metadata"]