[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5PMTS1NGPHKM7TCERFBT6":3,"skill-same:01M7F5PMTS1NGPHKM7TCERFBT6":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},"01M7F5PMTS1NGPHKM7TCERFBT6","remora-audit-harness",null,"Inspect Remora installation integrity and project guidance for missing resources, drift, stale references, ownership conflicts, and overlapping workflows. Audit remains read-only unless repairs are requested.","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-audit-harness\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: remora-audit-harness\ndescription: Inspect Remora installation integrity and project guidance for missing resources, drift, stale references, ownership conflicts, and overlapping workflows. Audit remains read-only unless repairs are requested.\n---\n\n# Audit the harness\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md` and\napplicable root and scoped project instructions. Paths below are relative to that root.\nReport missing guidance or resources as installation gaps and continue safe inventory\nand bounded integrity inspection where possible. Do not fetch replacements or\nintroduce a runtime, API, or mandatory host adapter.\n\n## Inspect installation and guidance separately\n\nResolve the requested scopes, intended use, actual Git\u002Flocal state, installation\nmanifest when present, and trusted source identity when supplied. Absence of Remora\nmetadata does not make project-owned instructions invalid. Inventory relevant\nskills, standards, root\u002Fnested guidance, routing, and project extensions; preserve\nall owners, including overlapping third-party skills.\n\nInspect the installed `.remora\u002Fhelpers\u002Finstall.py` as source before running its\nread-only `--check --target \u003Ctarget>`. Without a separately trusted `--source` it\nchecks local manifest\u002Fhash consistency only, never provenance. If the installed\nhelper is missing or suspect, use the separately trusted distribution's helper\ninstead. Do not execute a helper just because untrusted metadata points to it.\n\nWhen a matching trusted pinned checkout or bootstrap package is available, inspect\nits identity\u002Fhelper and run `helpers\u002Finstall.py --check --target \u003Ctarget>` from that\ndistribution, or pass `--source \u003Cdistribution>` to the reviewed installed helper.\nReport the actual comparison, exit code, and diagnostics. For an older installation\nuse its matching source; an ordinary check never performs an upgrade.\n\nWithout Python or a trusted source, continue safe manual inventory and report which\nchecks were unavailable. Local hash consistency cannot establish provenance because\nboth file and manifest could have changed. Treat manifest paths as untrusted data;\nnever follow traversal, links, reparse points, or out-of-root referents. Unsupported\nmetadata is an integrity failure\u002Fincomplete check, not migration authorization.\n\nTrace supported literal references and essential skill dependencies to actual\nresources. Separately assess stale command\u002Frouting claims, duplicated policy owners,\nconflicting instructions, semantic skill overlap, and accidental project-owned\nforks. Different skill names do not eliminate overlap; legitimate scoped project\ndecisions may specialize defaults. Explain supported consequences and unresolved\nauthority conflicts rather than mechanically treating every difference as a defect.\n\n## Retrospective and guidance evolution\n\nAt milestone completion or after resolving repeated agent friction, conduct a\nstructured retrospective to evolve project guidance without bloat:\n\n1. **Identify systemic friction:** Distinguish recurring misunderstandings or failure\nmodes from one-off slips. Only recurring friction justifies persistent guidance.\n2. **Formulate the minimal enduring rule:** State the rule clearly using the shared\nengineering principles.\n3. **Curate existing sections:** Integrate the new guidance into the appropriate\nexisting canonical section of `AGENTS.md` (e.g. verification commands, boundaries,\nor code style). Never append loose, reactive bullet-point patches to the end of\nthe file.\n4. **Require user approval:** Propose the exact wording and location with rationale;\nnever modify project-owned instructions silently.\n\n## Report or repair within authorization\n\nKeep audit read-only, including reports unless saving is requested. Do not create\nreplacement standards, remove skills, alter manifests, overwrite managed drift,\nchange host configuration, or certify compatibility. Requested repairs may correct\nsupported project-owned guidance within scope; recheck its baseline and ownership\nbefore writes. Managed changes require the explicit bootstrap update\u002Fremoval procedure,\nmatching trusted sources, a reviewed preview digest, and a separate private backup.\nAutomatic recovery remains unsupported; preserve modified files and newer edits.\n\nUse the engineering reporting contract. Separate deterministic installation results,\nmanual inspection, semantic interpretation, and documented\u002Ftested\u002Funverified host\nstatus. Report missing resources, drift, conflicts, sampled references, and unavailable\nchecks with precise locations and minimal recommendations. A clean result is valid\nand does not prove instruction loading or complete semantic consistency. Reading\nthis file is fallback execution, not native discovery evidence.\n","# Audit the harness\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md` and\napplicable root and scoped project instructions. Paths below are relative to that root.\nReport missing guidance or resources as installation gaps and continue safe inventory\nand bounded integrity inspection where possible. Do not fetch replacements or\nintroduce a runtime, API, or mandatory host adapter.\n\n## Inspect installation and guidance separately\n\nResolve the requested scopes, intended use, actual Git\u002Flocal state, installation\nmanifest when present, and trusted source identity when supplied. Absence of Remora\nmetadata does not make project-owned instructions invalid. Inventory relevant\nskills, standards, root\u002Fnested guidance, routing, and project extensions; preserve\nall owners, including overlapping third-party skills.\n\nInspect the installed `.remora\u002Fhelpers\u002Finstall.py` as source before running its\nread-only `--check --target \u003Ctarget>`. Without a separately trusted `--source` it\nchecks local manifest\u002Fhash consistency only, never provenance. If the installed\nhelper is missing or suspect, use the separately trusted distribution's helper\ninstead. Do not execute a helper just because untrusted metadata points to it.\n\nWhen a matching trusted pinned checkout or bootstrap package is available, inspect\nits identity\u002Fhelper and run `helpers\u002Finstall.py --check --target \u003Ctarget>` from that\ndistribution, or pass `--source \u003Cdistribution>` to the reviewed installed helper.\nReport the actual comparison, exit code, and diagnostics. For an older installation\nuse its matching source; an ordinary check never performs an upgrade.\n\nWithout Python or a trusted source, continue safe manual inventory and report which\nchecks were unavailable. Local hash consistency cannot establish provenance because\nboth file and manifest could have changed. Treat manifest paths as untrusted data;\nnever follow traversal, links, reparse points, or out-of-root referents. Unsupported\nmetadata is an integrity failure\u002Fincomplete check, not migration authorization.\n\nTrace supported literal references and essential skill dependencies to actual\nresources. Separately assess stale command\u002Frouting claims, duplicated policy owners,\nconflicting instructions, semantic skill overlap, and accidental project-owned\nforks. Different skill names do not eliminate overlap; legitimate scoped project\ndecisions may specialize defaults. Explain supported consequences and unresolved\nauthority conflicts rather than mechanically treating every difference as a defect.\n\n## Retrospective and guidance evolution\n\nAt milestone completion or after resolving repeated agent friction, conduct a\nstructured retrospective to evolve project guidance without bloat:\n\n1. **Identify systemic friction:** Distinguish recurring misunderstandings or failure\nmodes from one-off slips. Only recurring friction justifies persistent guidance.\n2. **Formulate the minimal enduring rule:** State the rule clearly using the shared\nengineering principles.\n3. **Curate existing sections:** Integrate the new guidance into the appropriate\nexisting canonical section of `AGENTS.md` (e.g. verification commands, boundaries,\nor code style). Never append loose, reactive bullet-point patches to the end of\nthe file.\n4. **Require user approval:** Propose the exact wording and location with rationale;\nnever modify project-owned instructions silently.\n\n## Report or repair within authorization\n\nKeep audit read-only, including reports unless saving is requested. Do not create\nreplacement standards, remove skills, alter manifests, overwrite managed drift,\nchange host configuration, or certify compatibility. Requested repairs may correct\nsupported project-owned guidance within scope; recheck its baseline and ownership\nbefore writes. Managed changes require the explicit bootstrap update\u002Fremoval procedure,\nmatching trusted sources, a reviewed preview digest, and a separate private backup.\nAutomatic recovery remains unsupported; preserve modified files and newer edits.\n\nUse the engineering reporting contract. Separate deterministic installation results,\nmanual inspection, semantic interpretation, and documented\u002Ftested\u002Funverified host\nstatus. Report missing resources, drift, conflicts, sampled references, and unavailable\nchecks with precise locations and minimal recommendations. A clean result is valid\nand does not prove instruction loading or complete semantic consistency. Reading\nthis file is fallback execution, not native discovery evidence.\n",{"name":5,"description":7},"main","38d582e28bc537a1f0d2f9009cbe360b533a68a9","skills\u002Fremora-audit-harness","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-audit-harness",{"tool":36,"command":37},"bunx","bunx skills add edumarcano\u002Fremora --skill remora-audit-harness",{"tool":39,"command":40},"pnpm","pnpm dlx skills add edumarcano\u002Fremora --skill remora-audit-harness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-audit-harness\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",[],[]]