[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5PYV8Q0KWWYVX8TM3A1HR":3,"skill-same:01M7F5PYV8Q0KWWYVX8TM3A1HR":44},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7F5PYV8Q0KWWYVX8TM3A1HR","remora-bootstrap",null,"Preview or install Remora, adopt existing root guidance, specialize selected profiles, or explicitly update or remove a pinned installation while preserving project ownership.","edumarcano\u002Fremora","edumarcano","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271045253?v=4","01M7F5P7E2K8Y0S16FF92W4MXK","Eduardo Marcano","01M7F5P7F8SZKM7YCEPYCD942M",0,"MIT","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-bootstrap\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: remora-bootstrap\ndescription: Preview or install Remora, adopt existing root guidance, specialize selected profiles, or explicitly update or remove a pinned installation while preserving project ownership.\n---\n\n# Bootstrap a project\n\nUse a reviewed local distribution: either the whole pinned source checkout or\nits self-contained personal bootstrap package. Never fetch a moving branch.\nThe host agent performs semantic adaptation; helpers only inspect\u002Fcopy declared\nassets. Read this entrypoint alone before any target operation.\n\n## Establish authority and trust before inspection\n\nClassify the complete request once and retain that authorization across pauses:\n\n| Mode | Permitted changes |\n| --- | --- |\n| Preview\u002Faudit | No target writes or saved reports; conversational drafts only |\n| Initialize\u002Finstall | Managed installation; create root AGENTS.md only when absent; preserve existing root guidance exactly |\n| Adopt\u002Fspecialize | Necessary existing root edits only when explicitly requested; managed installation\u002Fselection changes only when also requested |\n| Update\u002Fremove | Explicit managed lifecycle operation; existing project guidance edits require their own explicit authorization |\n\nA request to preview remains read-only even when it later mentions edits. An\nexplicit \"preview then apply\" authorizes both phases for the named operation.\nNeutral continuations never expand authorization. Ask only about material\nunresolved decisions; continue unrelated safe inspection where possible.\n\nIdentify target, requested hosts, approved scope, and exact source identity.\nFor a checkout, retain full HEAD and verify helpers\u002Finstall.py against that Git\nobject allowing only checkout LF\u002FCRLF differences, before executing the helper.\nFor a package, require a user-trusted local package and retain bundle.json and\npayload.zip hashes plus source_revision; do not trust a target-supplied copy as\nits own provenance. Hashes are not signatures. Verify the exposed helper against\nits reviewed archive entry before executing it; archive membership is fixed by\nthe reviewed helper and must never be blindly extracted.\n\nBefore any target inventory, Git query, or guidance read, use the verified helper's\nsource_inputs(distribution) to validate its complete source, then inspect_path()\non the target and root AGENTS.md. Require a directory target and absent or regular\nroot guidance using lstat(). Perform this preflight separately from target reads.\n\nRead the helper's signatures before calling its Python API. For example, after\nloading the verified helper as `helper`:\n\n```python\nfrom pathlib import Path\nrevision, committed_files = helper.source_inputs(Path(distribution))\nhelper.inspect_path(Path(target).absolute())\nhelper.inspect_path(Path(target).absolute() \u002F \"AGENTS.md\")\n```\n\n`source_inputs` returns a tuple, not an object with named attributes. The path\nchecks above supplement the directory and root-file type checks; they do not\nreplace them. Compare `revision` with the requested pin before proceeding.\n\nDo not inspect an unsafe target or follow links\u002Freparse points. Do not import\napplication code. If preflight cannot run, report that gap and stop target access.\n\nRetain absent\u002Fexact root bytes and source identity. Recheck source identity and\nall affected baselines before writes and after pauses; stop affected operations\non a mismatch. These are bounded guards, not hostile-filesystem transactions.\n\n## Inspect and select\n\nInspect Git and untracked state; unborn HEAD is valid. Read root and applicable\nscoped\u002Foverride instructions, selected specifications, and visible host guidance.\nReport hidden context you cannot inspect. Preserve existing and overlapping skills.\nSeparate observed facts, approved intentions, proposals, and unknowns.\n\nInspect manifests\u002Fconfiguration as data without executing discovered commands.\nSelect only evidence-backed profiles: python, typescript, local, web. A language\nproposal does not establish tooling; language and runtime dimensions are separate.\nUse no profiles for unknown architecture. Read relevant source references under\nprofiles\u002F in a checkout, or the reviewed payload.zip entries in a package, without\nextracting arbitrary paths. Profiles guide questions, never scaffold an application.\n\n## Preview and draft\n\nDistribution paths below start at the checkout root or personal bootstrap folder.\nUse Python 3.11+; checkout sources additionally require Git. Helpers use no network.\n\n```text\npython \"\u003Cdistribution>\u002Fhelpers\u002Finstall.py\" --target \"\u003Ctarget>\" --environment codex\n```\n\nRepeat --environment for requested families and --profile for selected references.\nPreview writes nothing. Installation failures stop affected writes; do not bypass\ncollisions through manual copying. Compare expected payloads with Git-object or\nvalidated archive bytes, never reconstructed shell text or checkout-only hashes.\n\nRead standards\u002Fengineering.md and templates\u002FAGENTS.md from this distribution.\nDraft minimal project guidance in the conversation. Do not copy Remora's own root\nAGENTS.md into the target. With no implementation, do not invent commands, paths,\nstack, or architecture. Configured commands are not executed checks.\n\nExisting root guidance remains unchanged unless adoption\u002Fspecialization edits are\nexplicitly requested. Even then, correct only a demonstrated obsolete claim,\nbroken pointer, or essential missing operating constraint. True details need not\nbe duplicated from their canonical owner. Adequate guidance needs no diff.\nAbsent guidance should include orientation, essential boundaries, actual known\nverification pointers, and explicit reading of .remora\u002Fstandards\u002Fengineering.md\nand applicable scoped instructions. Do not add historical pass status, private\npaths, unused sections, or references to uninstalled skills\u002Fprofiles.\n\nPreview ends here. Do not create temporary target reports.\n\n## Apply a new installation or guidance edit\n\nRecheck retained trust and target baselines. Run the same preview command with\n--apply, then --check. Installation creates shared standards, ten project skills,\nthe installed checking helper, selected profiles, and installation.json. It changes\nno host configuration or project prose.\n\nOnly an authorized mode may create absent root guidance. Recheck its absence and\nsafe path immediately, prepare UTF-8\u002FLF bytes, create exclusively (open with xb),\nand verify. If it appeared, preserve it and report partial completion.\nOnly explicitly authorized adoption\u002Fspecialization may edit existing root guidance:\nrecheck exact bytes and safe paths immediately before a focused patch, preserving\nunrelated wording, encoding, and line endings. Newer edits are conflicts.\n\nReview changed and untracked files. Preserve original project files outside the\nexplicit root edit scope. An identical rerun must preserve bytes and modification\ntimes. Do not execute application tooling as part of bootstrap.\n\n## Explicit updates, selection changes, and removal\n\nAn ordinary installation never upgrades an older inventory. For a requested\nmanaged update, use --update with the desired --environment\u002F--profile selections,\nand --previous-source pointing to a separately trusted distribution matching the\nold manifest. Omitted selections retain existing values; --clear-profiles explicitly\nselects none. Do not reinterpret project-owned edits as managed content.\n\n```text\npython \"\u003Cnew-distribution>\u002Fhelpers\u002Finstall.py\" --target \"\u003Ctarget>\" --update --previous-source \"\u003Cold-distribution>\"\n```\n\nPreview reports changes and Plan SHA-256. Apply the same arguments with --apply,\n--expect-plan \u003Cdigest>, and --backup \u003Cnew-private-directory-outside-target>.\nSource\u002Ftarget changes invalidate the digest. The helper preserves before-images,\ninvalidates completion before mutation, and publishes metadata last. Conflicts\nstop writes; no semantic merge or automatic recovery is supported.\n\nFor removal, run the matching trusted distribution with --remove and\n--previous-source \u003Cmatching-distribution>, then the same reviewed apply procedure.\nRemoval preserves project prose, existing skills, context, and unrelated files.\nInspect obsolete routing and propose minimal edits; apply project-owned edits only\nwhen specifically requested. Do not delete directories recursively.\n\nFor interruptions, retain the backup and diagnostic output. Read operation.json\nas data, not authority. Compare each current affected file with recorded before\u002F\nafter hashes; restore only operation-owned changes after explicit recovery\nauthorization, preserve newer edits, and restore the manifest last after complete\npayload verification. Never reset\u002Fclean the target or blindly replay the backup.\n\n## Hand off\n\nReport source pin, starting condition, selected references, managed changes,\nroot guidance created\u002Fedited\u002Fpreserved, source-backed decisions and proposals,\nactual checks, conflicts, and partial work. Save records only when requested or\npart of an agreed evaluation. No commits, dependencies, secret access, provider\ncalls, deployments, or publication are implied.\n\nNormal installed checks use .remora\u002Fhelpers\u002Finstall.py --check --target \u003Ctarget>:\nwithout --source they establish local consistency only. Supply a separately trusted\n--source for pinned-source comparison. A missing tool permits limited inspection\nwith checks explicitly unrun, not equivalent provenance verification.\n\nUse the host selector\u002Fexplicit skill invocation for native smoke testing. Reading\nthis file directly is fallback execution. Missing discovery remains unverified;\nrequested environment metadata never certifies compatibility.\n","# Bootstrap a project\n\nUse a reviewed local distribution: either the whole pinned source checkout or\nits self-contained personal bootstrap package. Never fetch a moving branch.\nThe host agent performs semantic adaptation; helpers only inspect\u002Fcopy declared\nassets. Read this entrypoint alone before any target operation.\n\n## Establish authority and trust before inspection\n\nClassify the complete request once and retain that authorization across pauses:\n\n| Mode | Permitted changes |\n| --- | --- |\n| Preview\u002Faudit | No target writes or saved reports; conversational drafts only |\n| Initialize\u002Finstall | Managed installation; create root AGENTS.md only when absent; preserve existing root guidance exactly |\n| Adopt\u002Fspecialize | Necessary existing root edits only when explicitly requested; managed installation\u002Fselection changes only when also requested |\n| Update\u002Fremove | Explicit managed lifecycle operation; existing project guidance edits require their own explicit authorization |\n\nA request to preview remains read-only even when it later mentions edits. An\nexplicit \"preview then apply\" authorizes both phases for the named operation.\nNeutral continuations never expand authorization. Ask only about material\nunresolved decisions; continue unrelated safe inspection where possible.\n\nIdentify target, requested hosts, approved scope, and exact source identity.\nFor a checkout, retain full HEAD and verify helpers\u002Finstall.py against that Git\nobject allowing only checkout LF\u002FCRLF differences, before executing the helper.\nFor a package, require a user-trusted local package and retain bundle.json and\npayload.zip hashes plus source_revision; do not trust a target-supplied copy as\nits own provenance. Hashes are not signatures. Verify the exposed helper against\nits reviewed archive entry before executing it; archive membership is fixed by\nthe reviewed helper and must never be blindly extracted.\n\nBefore any target inventory, Git query, or guidance read, use the verified helper's\nsource_inputs(distribution) to validate its complete source, then inspect_path()\non the target and root AGENTS.md. Require a directory target and absent or regular\nroot guidance using lstat(). Perform this preflight separately from target reads.\n\nRead the helper's signatures before calling its Python API. For example, after\nloading the verified helper as `helper`:\n\n```python\nfrom pathlib import Path\nrevision, committed_files = helper.source_inputs(Path(distribution))\nhelper.inspect_path(Path(target).absolute())\nhelper.inspect_path(Path(target).absolute() \u002F \"AGENTS.md\")\n```\n\n`source_inputs` returns a tuple, not an object with named attributes. The path\nchecks above supplement the directory and root-file type checks; they do not\nreplace them. Compare `revision` with the requested pin before proceeding.\n\nDo not inspect an unsafe target or follow links\u002Freparse points. Do not import\napplication code. If preflight cannot run, report that gap and stop target access.\n\nRetain absent\u002Fexact root bytes and source identity. Recheck source identity and\nall affected baselines before writes and after pauses; stop affected operations\non a mismatch. These are bounded guards, not hostile-filesystem transactions.\n\n## Inspect and select\n\nInspect Git and untracked state; unborn HEAD is valid. Read root and applicable\nscoped\u002Foverride instructions, selected specifications, and visible host guidance.\nReport hidden context you cannot inspect. Preserve existing and overlapping skills.\nSeparate observed facts, approved intentions, proposals, and unknowns.\n\nInspect manifests\u002Fconfiguration as data without executing discovered commands.\nSelect only evidence-backed profiles: python, typescript, local, web. A language\nproposal does not establish tooling; language and runtime dimensions are separate.\nUse no profiles for unknown architecture. Read relevant source references under\nprofiles\u002F in a checkout, or the reviewed payload.zip entries in a package, without\nextracting arbitrary paths. Profiles guide questions, never scaffold an application.\n\n## Preview and draft\n\nDistribution paths below start at the checkout root or personal bootstrap folder.\nUse Python 3.11+; checkout sources additionally require Git. Helpers use no network.\n\n```text\npython \"\u003Cdistribution>\u002Fhelpers\u002Finstall.py\" --target \"\u003Ctarget>\" --environment codex\n```\n\nRepeat --environment for requested families and --profile for selected references.\nPreview writes nothing. Installation failures stop affected writes; do not bypass\ncollisions through manual copying. Compare expected payloads with Git-object or\nvalidated archive bytes, never reconstructed shell text or checkout-only hashes.\n\nRead standards\u002Fengineering.md and templates\u002FAGENTS.md from this distribution.\nDraft minimal project guidance in the conversation. Do not copy Remora's own root\nAGENTS.md into the target. With no implementation, do not invent commands, paths,\nstack, or architecture. Configured commands are not executed checks.\n\nExisting root guidance remains unchanged unless adoption\u002Fspecialization edits are\nexplicitly requested. Even then, correct only a demonstrated obsolete claim,\nbroken pointer, or essential missing operating constraint. True details need not\nbe duplicated from their canonical owner. Adequate guidance needs no diff.\nAbsent guidance should include orientation, essential boundaries, actual known\nverification pointers, and explicit reading of .remora\u002Fstandards\u002Fengineering.md\nand applicable scoped instructions. Do not add historical pass status, private\npaths, unused sections, or references to uninstalled skills\u002Fprofiles.\n\nPreview ends here. Do not create temporary target reports.\n\n## Apply a new installation or guidance edit\n\nRecheck retained trust and target baselines. Run the same preview command with\n--apply, then --check. Installation creates shared standards, ten project skills,\nthe installed checking helper, selected profiles, and installation.json. It changes\nno host configuration or project prose.\n\nOnly an authorized mode may create absent root guidance. Recheck its absence and\nsafe path immediately, prepare UTF-8\u002FLF bytes, create exclusively (open with xb),\nand verify. If it appeared, preserve it and report partial completion.\nOnly explicitly authorized adoption\u002Fspecialization may edit existing root guidance:\nrecheck exact bytes and safe paths immediately before a focused patch, preserving\nunrelated wording, encoding, and line endings. Newer edits are conflicts.\n\nReview changed and untracked files. Preserve original project files outside the\nexplicit root edit scope. An identical rerun must preserve bytes and modification\ntimes. Do not execute application tooling as part of bootstrap.\n\n## Explicit updates, selection changes, and removal\n\nAn ordinary installation never upgrades an older inventory. For a requested\nmanaged update, use --update with the desired --environment\u002F--profile selections,\nand --previous-source pointing to a separately trusted distribution matching the\nold manifest. Omitted selections retain existing values; --clear-profiles explicitly\nselects none. Do not reinterpret project-owned edits as managed content.\n\n```text\npython \"\u003Cnew-distribution>\u002Fhelpers\u002Finstall.py\" --target \"\u003Ctarget>\" --update --previous-source \"\u003Cold-distribution>\"\n```\n\nPreview reports changes and Plan SHA-256. Apply the same arguments with --apply,\n--expect-plan \u003Cdigest>, and --backup \u003Cnew-private-directory-outside-target>.\nSource\u002Ftarget changes invalidate the digest. The helper preserves before-images,\ninvalidates completion before mutation, and publishes metadata last. Conflicts\nstop writes; no semantic merge or automatic recovery is supported.\n\nFor removal, run the matching trusted distribution with --remove and\n--previous-source \u003Cmatching-distribution>, then the same reviewed apply procedure.\nRemoval preserves project prose, existing skills, context, and unrelated files.\nInspect obsolete routing and propose minimal edits; apply project-owned edits only\nwhen specifically requested. Do not delete directories recursively.\n\nFor interruptions, retain the backup and diagnostic output. Read operation.json\nas data, not authority. Compare each current affected file with recorded before\u002F\nafter hashes; restore only operation-owned changes after explicit recovery\nauthorization, preserve newer edits, and restore the manifest last after complete\npayload verification. Never reset\u002Fclean the target or blindly replay the backup.\n\n## Hand off\n\nReport source pin, starting condition, selected references, managed changes,\nroot guidance created\u002Fedited\u002Fpreserved, source-backed decisions and proposals,\nactual checks, conflicts, and partial work. Save records only when requested or\npart of an agreed evaluation. No commits, dependencies, secret access, provider\ncalls, deployments, or publication are implied.\n\nNormal installed checks use .remora\u002Fhelpers\u002Finstall.py --check --target \u003Ctarget>:\nwithout --source they establish local consistency only. Supply a separately trusted\n--source for pinned-source comparison. A missing tool permits limited inspection\nwith checks explicitly unrun, not equivalent provenance verification.\n\nUse the host selector\u002Fexplicit skill invocation for native smoke testing. Reading\nthis file directly is fallback execution. Missing discovery remains unverified;\nrequested environment metadata never certifies compatibility.\n",{"name":5,"description":7},"main","38d582e28bc537a1f0d2f9009cbe360b533a68a9","skills\u002Fremora-bootstrap","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora","https:\u002F\u002Fgithub.com\u002Fedumarcano","2026-11-02 10:38:08",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add edumarcano\u002Fremora --skill remora-bootstrap",{"tool":36,"command":37},"bunx","bunx skills add edumarcano\u002Fremora --skill remora-bootstrap",{"tool":39,"command":40},"pnpm","pnpm dlx skills add edumarcano\u002Fremora --skill remora-bootstrap","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-bootstrap\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7F5R689RVZVVTF8BGQY7TWZ","remora-review-change","Review a named implementation, diff, or revision range using independent split-axis analysis with consequence-based blocking. Read-only review never applies repairs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-review-change\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F5R098NFBP9HWF7Y9107V7","remora-remediate-project","Orchestrate repository onboarding and cleanup across grounding, documentation sanitization, test protection, and scoped debt remediation through checkpointed review gates.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-remediate-project\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F5QTDVXZDTYCB302QA7WAE","remora-prepare-release","Prepare a verified software release, updating CHANGELOG.md, proposing a semantic tag, and generating concise GitHub release notes under the anti-slop standard.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-release\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7F5QMX7CHP9QPKCF8EA119Z","remora-prepare-pr","Prepare a concise, reviewer-friendly pull request brief adhering to the anti-slop standard, emphasizing artifact proof and reviewer verification over redundant CI logs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-pr\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F5QFF5Z5XM0EMA8MB5P708","remora-plan-change","Investigate and plan a scoped development change into phased, verifiable work packets using repository evidence, requirements, and acceptance criteria. Planning remains read-only unless saving a plan is requested.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-plan-change\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"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},"01M7F5QA8C5DKW4FTA71KYYB7Q","remora-implement-plan","Implement an approved plan or clear scoped development request across phased work packets, including checkpoint verification, empirical artifact proof, and split-axis review.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-implement-plan\u002FSKILL.md",[],[]]