[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M782M3P4PQ5Q6NNRQVCD3F1M":3,"skill-same:01M782M3P4PQ5Q6NNRQVCD3F1M":57},{"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":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M782M3P4PQ5Q6NNRQVCD3F1M","rollback",null,"Plan a safe history-preserving reversal of a completed feature from its archive and exact commit, including later-dependency risk, then stop before implementation. Use for \u002Frollback or requests to undo, remove, or reverse a completed feature.","bradtraversy\u002Fskillpass","bradtraversy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5550850?v=4","01M782H8BT6A97A17XDFHDABWZ","Brad Traversy","01M782H8CDJZW3HYDHX23FA9VF",26,"MIT","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frollback\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: rollback\ndescription: Plan a safe history-preserving reversal of a completed feature from its archive and exact commit, including later-dependency risk, then stop before implementation. Use for \u002Frollback or requests to undo, remove, or reverse a completed feature.\n---\n\n# rollback - safely reverse a completed feature\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    completed feature + git history  ->  [rollback]  ->  \u002Fimplement  ->  \u002Fcheck  ->  \u002Fcomplete\n    (archive + squashed commit)           (risk review     (reverse       (prove)     (log + merge)\n                                           + spec)          product diff)\n\nThis skill plans a rollback. It does not change product code, create a branch,\ncommit, merge, or push. It identifies the completed feature and its exact git\ncommit, checks what changed afterward, writes a guarded rollback spec, then stops\nfor review. `\u002Fimplement` performs the reversal only after the user approves that\nspec.\n\n## Input\n\nA completed feature by build-plan number, name, or archive path, plus an optional\nreason. Examples:\n\n    \u002Frollback 4 because the new export flow is corrupting files\n    \u002Frollback \"PDF export\"\n    \u002Frollback blueprint\u002Fhistory\u002Ffeatures\u002F04-pdf-export.md\n\nWith no target, list a short set of recent completed feature archives and ask the\nuser to choose. Never silently pick the latest feature. If the reason is missing,\nask for one before writing the spec because the rollback archive must explain why\nthe feature was removed.\n\n## Step 0 - preflight\n\nRead `AGENTS.md`, `blueprint\u002Fbuild-plan.md`,\n`blueprint\u002Fcontext\u002Fcurrent-feature.md`, the completed feature archives, and git\nstate.\n\nStop before writing when:\n\n- the directory is not a git repository\n- `current-feature.md` already holds active work\n- the working tree is dirty, including unrelated untracked work\n- the current branch is not the local main or default branch\n- the target is not a checked build-plan feature with a matching archive\n- the archive or its introducing commit cannot be identified unambiguously\n\nDo not stash, discard, fetch, pull, switch branches, or clean the tree from this\nskill.\n\n## Step 1 - resolve the exact feature\n\nResolve the requested number or name to one checked build-plan ID; for an archive\npath, read its exact spec identity first and match that checked item. Then gather\nall exact-ID feature archive candidates using `..\u002Ffeature\u002Freference\u002Fbuild-history.md`.\nNormalize the stable ID, retaining its letter, and read attempts from verified\nspec metadata\u002Fhistory proof, never arbitrary title or filename suffixes.\n\nFor each candidate, require its unique introducing commit on the local default\nand prove the archive blob and mode have not changed since that addition. Exclude\nbuilds with a proven completed reachable rollback naming that exact archive and\nintroducing commit. The checked item must have exactly one unreversed build.\nAn explicit archive request stays bound to that exact path: reject it if already\nreversed, rather than silently choosing another build. Ambiguous, orphan,\noverwritten, multiply-added, or missing records stop with their exact paths and\nmissing proof. Do not select by newest commit, filename order, or rollback date.\n\nConfirm the selected commit's diff is consistent with the requested feature.\nIf the target is a merge commit, stop before Step 2 and before\nwriting or changing `blueprint\u002Fcontext\u002Fcurrent-feature.md`. Do not record a\ntarget parent or choose a mainline. Publish `blocked` to\n`blueprint\u002F.state\u002Frun.json`, explain that Blueprint cannot safely infer which\nmerge parent represents the pre-feature state, and include the exact `\u002Frollback`\ncommand the user can rerun after choosing a safe remediation or mainline\nstrategy. `\u002Fimplement` retains its merge-target stop as defense in depth. If the\narchive was never committed, explain that git cannot reconstruct a safe rollback\nfrom it.\n\n## Step 2 - separate product changes from Blueprint history\n\nInspect the target commit and build the product-path set from the files it\nchanged. Exclude these protected workflow paths:\n\n- `.agents\u002F**`\n- `.claude\u002F**`\n- `blueprint\u002F**`\n- `AGENTS.md`\n- `CLAUDE.md`\n- `prototypes\u002F**`\n\nThe rollback must preserve the original feature archive, later planning changes,\nthe active rollback spec, adapter skills, and throwaway prototype history. Root\n`README.md` and ordinary app docs are product files unless the project says\notherwise.\n\nIf no product paths remain, stop. Do not create an empty rollback that only\nrewrites Blueprint records.\n\n## Step 3 - review later-change risk\n\nInspect every commit after the target through `HEAD` that touches one of the\nproduct paths. Also read later completed feature specs when they mention the\ntarget, its contracts, routes, data, or files.\n\nClassify the result:\n\n- **No overlap** - no later commit touched the target product paths.\n- **Overlap, likely compatible** - later edits touched the same paths, but the\n  target change can be reversed without removing their behavior.\n- **Dependency risk** - later work appears to require the target's API, schema,\n  route, component, or data.\n- **Blocked** - safe behavior after reversal is unclear, data migration would be\n  destructive, or a cascading rollback would be required.\n\nPath overlap is a warning signal, not proof of dependency. Explain the concrete\nlater commit and contract involved. Never silently cascade into reverting other\nfeatures. For a blocked case, stop and ask the user to choose a narrower\nremediation or explicitly plan the dependent rollbacks.\n\n## Step 4 - write the rollback spec\n\nWrite `blueprint\u002Fcontext\u002Fcurrent-feature.md` using\n`reference\u002Frollback-spec-template.md`. Its first heading must be exactly\n`# Rollback: Feature \u003Cid> - \u003Ctitle>`, and it must retain the existing\n`**Type:** Rollback` contract. Fill in:\n\n- the full rollback branch from the configured prefix plus the rollback title in\n  lowercase kebab-case, appending `--build-N` for target attempt N > 1 proved above\n- target feature and archive\n- target commit and parent commit as full 40-character SHA values\n- user's reason\n- product paths introduced or changed by the target\n- protected workflow paths\n- later commits reviewed and the risk classification\n- compatibility work that is allowed, if any\n- exact verification commands and observable removal criteria\n\nBefore freezing a new rollback spec, apply the archive-path and branch-availability\nchecks in `..\u002Ffeature\u002Freference\u002Fbuild-history.md` to its planned branch and\n`YYYY-MM-DD-\u003Cexact-target-archive-stem>.md` destination. Retain `--build-N` in the\ntarget stem when present. A collision stops for an explicit decision; never\nrenumber the target or silently rename reviewed work. Existing completion recovery runs first.\n\nThe first build step must apply the target commit's product diff in reverse using\nthe guarded Type: Rollback behavior in `\u002Fimplement`. Later steps may repair only\nthe specific downstream compatibility issues named in the spec. Do not use a\nrollback as permission for unrelated cleanup.\n\nOlder installations may not have `blueprint\u002Fhistory\u002Frollbacks\u002F` yet because\nupdates preserve user history. That is not a planning blocker; `\u002Fcomplete`\ncreates the directory when it archives the approved rollback.\n\nRed-team the draft before presenting it:\n\n- does it preserve all Blueprint history and later plan changes?\n- could it remove data or require a destructive migration?\n- does later code import or call something the target introduced?\n- are the removal criteria observable rather than phrased as \"feature gone\"?\n- can each compatibility edit be reviewed separately?\n\nTighten the spec, then stop. Summarize the target commit, affected product paths,\nlater-change risk, and what the critique changed. Tell the user to review the\nspec, then run `\u002Fimplement` to create the rollback branch and apply it.\n\n## Rules\n\n- Preserve history. Never delete or rewrite the original feature archive.\n- Plan only. This skill writes the rollback spec and nothing else.\n- One completed feature per rollback.\n- Record both the target commit and its parent as full 40-character SHA values.\n  Each value must resolve to the recorded commit in the current repository.\n- Never use `git reset --hard`, force-push, history rewriting, or broad file\n  restoration.\n- Never infer permission to cascade into later features or destroy stored data.\n- A rollback still uses `\u002Fimplement`, `\u002Fcheck`, and `\u002Fcomplete` review gates.\n\n## Formatting\n\nFormat the output to match `blueprint\u002Fcontext\u002Fai-interaction.md`: concise,\nscannable markdown with a small risk table when later commits overlap.\n","# rollback - safely reverse a completed feature\n\n**Context reuse:** Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.\n\n**First action:** Before project inspection, preflight, or any other tool call,\npublish `running` to `blueprint\u002F.state\u002Frun.json` using the dashboard activity\ncontract in `AGENTS.md`.\n\nWhere this sits in the workflow:\n\n    completed feature + git history  ->  [rollback]  ->  \u002Fimplement  ->  \u002Fcheck  ->  \u002Fcomplete\n    (archive + squashed commit)           (risk review     (reverse       (prove)     (log + merge)\n                                           + spec)          product diff)\n\nThis skill plans a rollback. It does not change product code, create a branch,\ncommit, merge, or push. It identifies the completed feature and its exact git\ncommit, checks what changed afterward, writes a guarded rollback spec, then stops\nfor review. `\u002Fimplement` performs the reversal only after the user approves that\nspec.\n\n## Input\n\nA completed feature by build-plan number, name, or archive path, plus an optional\nreason. Examples:\n\n    \u002Frollback 4 because the new export flow is corrupting files\n    \u002Frollback \"PDF export\"\n    \u002Frollback blueprint\u002Fhistory\u002Ffeatures\u002F04-pdf-export.md\n\nWith no target, list a short set of recent completed feature archives and ask the\nuser to choose. Never silently pick the latest feature. If the reason is missing,\nask for one before writing the spec because the rollback archive must explain why\nthe feature was removed.\n\n## Step 0 - preflight\n\nRead `AGENTS.md`, `blueprint\u002Fbuild-plan.md`,\n`blueprint\u002Fcontext\u002Fcurrent-feature.md`, the completed feature archives, and git\nstate.\n\nStop before writing when:\n\n- the directory is not a git repository\n- `current-feature.md` already holds active work\n- the working tree is dirty, including unrelated untracked work\n- the current branch is not the local main or default branch\n- the target is not a checked build-plan feature with a matching archive\n- the archive or its introducing commit cannot be identified unambiguously\n\nDo not stash, discard, fetch, pull, switch branches, or clean the tree from this\nskill.\n\n## Step 1 - resolve the exact feature\n\nResolve the requested number or name to one checked build-plan ID; for an archive\npath, read its exact spec identity first and match that checked item. Then gather\nall exact-ID feature archive candidates using `..\u002Ffeature\u002Freference\u002Fbuild-history.md`.\nNormalize the stable ID, retaining its letter, and read attempts from verified\nspec metadata\u002Fhistory proof, never arbitrary title or filename suffixes.\n\nFor each candidate, require its unique introducing commit on the local default\nand prove the archive blob and mode have not changed since that addition. Exclude\nbuilds with a proven completed reachable rollback naming that exact archive and\nintroducing commit. The checked item must have exactly one unreversed build.\nAn explicit archive request stays bound to that exact path: reject it if already\nreversed, rather than silently choosing another build. Ambiguous, orphan,\noverwritten, multiply-added, or missing records stop with their exact paths and\nmissing proof. Do not select by newest commit, filename order, or rollback date.\n\nConfirm the selected commit's diff is consistent with the requested feature.\nIf the target is a merge commit, stop before Step 2 and before\nwriting or changing `blueprint\u002Fcontext\u002Fcurrent-feature.md`. Do not record a\ntarget parent or choose a mainline. Publish `blocked` to\n`blueprint\u002F.state\u002Frun.json`, explain that Blueprint cannot safely infer which\nmerge parent represents the pre-feature state, and include the exact `\u002Frollback`\ncommand the user can rerun after choosing a safe remediation or mainline\nstrategy. `\u002Fimplement` retains its merge-target stop as defense in depth. If the\narchive was never committed, explain that git cannot reconstruct a safe rollback\nfrom it.\n\n## Step 2 - separate product changes from Blueprint history\n\nInspect the target commit and build the product-path set from the files it\nchanged. Exclude these protected workflow paths:\n\n- `.agents\u002F**`\n- `.claude\u002F**`\n- `blueprint\u002F**`\n- `AGENTS.md`\n- `CLAUDE.md`\n- `prototypes\u002F**`\n\nThe rollback must preserve the original feature archive, later planning changes,\nthe active rollback spec, adapter skills, and throwaway prototype history. Root\n`README.md` and ordinary app docs are product files unless the project says\notherwise.\n\nIf no product paths remain, stop. Do not create an empty rollback that only\nrewrites Blueprint records.\n\n## Step 3 - review later-change risk\n\nInspect every commit after the target through `HEAD` that touches one of the\nproduct paths. Also read later completed feature specs when they mention the\ntarget, its contracts, routes, data, or files.\n\nClassify the result:\n\n- **No overlap** - no later commit touched the target product paths.\n- **Overlap, likely compatible** - later edits touched the same paths, but the\n  target change can be reversed without removing their behavior.\n- **Dependency risk** - later work appears to require the target's API, schema,\n  route, component, or data.\n- **Blocked** - safe behavior after reversal is unclear, data migration would be\n  destructive, or a cascading rollback would be required.\n\nPath overlap is a warning signal, not proof of dependency. Explain the concrete\nlater commit and contract involved. Never silently cascade into reverting other\nfeatures. For a blocked case, stop and ask the user to choose a narrower\nremediation or explicitly plan the dependent rollbacks.\n\n## Step 4 - write the rollback spec\n\nWrite `blueprint\u002Fcontext\u002Fcurrent-feature.md` using\n`reference\u002Frollback-spec-template.md`. Its first heading must be exactly\n`# Rollback: Feature \u003Cid> - \u003Ctitle>`, and it must retain the existing\n`**Type:** Rollback` contract. Fill in:\n\n- the full rollback branch from the configured prefix plus the rollback title in\n  lowercase kebab-case, appending `--build-N` for target attempt N > 1 proved above\n- target feature and archive\n- target commit and parent commit as full 40-character SHA values\n- user's reason\n- product paths introduced or changed by the target\n- protected workflow paths\n- later commits reviewed and the risk classification\n- compatibility work that is allowed, if any\n- exact verification commands and observable removal criteria\n\nBefore freezing a new rollback spec, apply the archive-path and branch-availability\nchecks in `..\u002Ffeature\u002Freference\u002Fbuild-history.md` to its planned branch and\n`YYYY-MM-DD-\u003Cexact-target-archive-stem>.md` destination. Retain `--build-N` in the\ntarget stem when present. A collision stops for an explicit decision; never\nrenumber the target or silently rename reviewed work. Existing completion recovery runs first.\n\nThe first build step must apply the target commit's product diff in reverse using\nthe guarded Type: Rollback behavior in `\u002Fimplement`. Later steps may repair only\nthe specific downstream compatibility issues named in the spec. Do not use a\nrollback as permission for unrelated cleanup.\n\nOlder installations may not have `blueprint\u002Fhistory\u002Frollbacks\u002F` yet because\nupdates preserve user history. That is not a planning blocker; `\u002Fcomplete`\ncreates the directory when it archives the approved rollback.\n\nRed-team the draft before presenting it:\n\n- does it preserve all Blueprint history and later plan changes?\n- could it remove data or require a destructive migration?\n- does later code import or call something the target introduced?\n- are the removal criteria observable rather than phrased as \"feature gone\"?\n- can each compatibility edit be reviewed separately?\n\nTighten the spec, then stop. Summarize the target commit, affected product paths,\nlater-change risk, and what the critique changed. Tell the user to review the\nspec, then run `\u002Fimplement` to create the rollback branch and apply it.\n\n## Rules\n\n- Preserve history. Never delete or rewrite the original feature archive.\n- Plan only. This skill writes the rollback spec and nothing else.\n- One completed feature per rollback.\n- Record both the target commit and its parent as full 40-character SHA values.\n  Each value must resolve to the recorded commit in the current repository.\n- Never use `git reset --hard`, force-push, history rewriting, or broad file\n  restoration.\n- Never infer permission to cascade into later features or destroy stored data.\n- A rollback still uses `\u002Fimplement`, `\u002Fcheck`, and `\u002Fcomplete` review gates.\n\n## Formatting\n\nFormat the output to match `blueprint\u002Fcontext\u002Fai-interaction.md`: concise,\nscannable markdown with a small risk table when later commits overlap.\n",{"name":5,"description":7},"main","0007775402258962018a93be4dbf1cbcbc1536d8",".agents\u002Fskills\u002Frollback",3,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass","https:\u002F\u002Fgithub.com\u002Fbradtraversy","traversymedia.com","Full stack web developer and online instructor at https:\u002F\u002Ftraversymedia.com and https:\u002F\u002Fstart.dev","2026-10-06 00:26:26",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add bradtraversy\u002Fskillpass --skill rollback",{"tool":39,"command":40},"bunx","bunx skills add bradtraversy\u002Fskillpass --skill rollback",{"tool":42,"command":43},"pnpm","pnpm dlx skills add bradtraversy\u002Fskillpass --skill rollback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frollback\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",188,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frollback\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"reference\u002Frollback-spec-template.md",2550,"https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frollback\u002Freference\u002Frollback-spec-template.md",[58,64,70,75,81,87],{"skillNo":59,"name":60,"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":61,"categories":62,"keywords":63,"publishedAt":19},"01M782QBBKH3WTBZDE9DP52XH4","plan","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"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":67,"categories":68,"keywords":69,"publishedAt":19},"01M782Q980Y1KP1J77TNJHD5H8","apply","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002Fskills\u002Fapply\u002FSKILL.md",[],[],{"skillNo":71,"name":60,"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":72,"categories":73,"keywords":74,"publishedAt":19},"01M782Q75AS3P8SW7D819TACVD","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fworkflow-pack\u002F.claude\u002Fskills\u002Fplan\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"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":78,"categories":79,"keywords":80,"publishedAt":19},"01M782Q5WAP9DQH14TEKG5ZFX5","undeclared-network","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fundeclared-network\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M782Q424YF4TAYYX9TCCZCS8","prompt-injection","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fprompt-injection\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"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":90,"categories":91,"keywords":92,"publishedAt":19},"01M782Q28RQV6MJM98J6EN7XFF","missing-manifest","https:\u002F\u002Fgithub.com\u002Fbradtraversy\u002Fskillpass\u002Fblob\u002Fmain\u002Fpackages\u002Fvalidator\u002Ffixtures\u002Fmissing-manifest\u002FSKILL.md",[],[]]