[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1G033D658FWHRC5ATB9VZ":3,"skill-same:01M7F1G033D658FWHRC5ATB9VZ":52},{"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":30,"updatedAt":31,"install":32,"resources":45},"01M7F1G033D658FWHRC5ATB9VZ","loopx-material",null,"Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate\u002Farchive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off reading or research when the project has not activated Material Lifecycle.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Floopx-material\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: loopx-material\ndescription: Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate\u002Farchive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off reading or research when the project has not activated Material Lifecycle.\n---\n\n# LoopX Material\n\nUse this skill for the lifecycle and authority of a project's durable material\nstore. Source discovery, domain-specific scoring, and note writing may be\nprovided by project skills; this skill owns the generic lossless lifecycle.\n\nLoopX ships the canonical source for this skill, but does not install it into\nthe user's global skill directory. Install a managed copy only in a connected\nproject that explicitly enables Material Lifecycle:\n\n```bash\nloopx project-skill install \\\n  --project . \\\n  --skill loopx-material \\\n  --surface codex \\\n  --execute\n```\n\nUse `--surface claude-code` or `--surface opencode` for those hosts; repeat the\nflag to install multiple host-native copies in one transaction. Managed copies\nlive under `.agents\u002Fskills\u002F`, `.claude\u002Fskills\u002F`, or `.opencode\u002Fskills\u002F` and are\nupgraded or removed through the same CLI. Project-local discovery does not\nitself activate material-store writes; the selected goal still needs explicit\nMaterial Lifecycle authority.\n\n## Activation Gate\n\nBefore changing a material store:\n\n1. Resolve the current project, `goal_id`, registered agent, and active todo\n   through `loopx start-goal --guided`, `loopx status`, or `loopx diagnose`.\n2. Run `loopx project-skill status --project . --skill loopx-material` and\n   confirm the required host surfaces are current.\n3. Confirm the selected todo explicitly targets `material_lifecycle`, or that\n   the goal authority declares an active Material Lifecycle profile and its\n   source store. A catalog entry or project-local skill is not activation.\n4. Confirm the goal boundary covers the exact private adapter and authority\n   paths. Public LoopX contracts never grant access to private source content.\n5. Run `loopx material-lifecycle architecture --format json` and preserve its\n   default-off, owner-gated, provider-neutral boundaries.\n\nIf the project-local skill is missing, preview an explicit project install; do\nnot fall back to a global copy. If activation or authority is missing, stop\nbefore source mutation. Create a bounded setup todo or owner gate; do not\ninvent a store or treat chat history as authority.\n\n## Ownership Boundary\n\nKeep these responsibilities separate:\n\n- **Project source adapter**: locates and reads the project's private source\n  files, database, documents, or provider.\n- **Research\u002Freader skill**: recalls candidates, performs exact reads, and\n  produces source-quality and domain-value evidence.\n- **Decision Context**: supplies revision-bound objectives, changed facts,\n  conflicts, and accepted decisions.\n- **Material Lifecycle**: owns inventory, migration, lifecycle transitions,\n  ranked-entry rebuild, rerank proposals, apply receipts, and rollback.\n- **Content or notes workflow**: consumes selected material and produces an\n  artifact; it does not rewrite candidate\u002Farchive\u002Franking truth by itself.\n\n## Workflow\n\n### 1. Snapshot And Inventory\n\nRead the source authority before proposing structural change.\n\n- Record source revision, byte\u002Fcontent digest, lifecycle counts, parse errors,\n  stable material references, and a verified backup.\n- Keep raw content, private paths, URLs, provider payloads, and credentials out\n  of public packets and commits.\n- Preserve the original source until a verified cutover and rollback rehearsal\n  have both succeeded.\n\nNo migration, rebuild, or rerank may begin from an unverified partial parse.\n\n### 2. Normalize Lifecycle\n\nUse stable material references across:\n\n```text\ncandidate -> active -> archived\n                 \\-> carryover\narchived -> active\n```\n\nEvery transition needs a revisioned evidence or decision reference. Archiving\nmust preserve the original source reference and an archive reference. Reading,\nsummarizing, or publishing a note does not implicitly archive a material.\n\n### 3. Promote Exact-Read Evidence\n\nRecall is advisory. Before a material affects ranking or lifecycle:\n\n1. retrieve the candidate through the configured provider or local search;\n2. exact-read the authoritative source;\n3. record source revision and read scope;\n4. reject stale, conflicting, unreadable, or only-secondary claims;\n5. pass only promoted evidence into Decision Context or ranking.\n\nDo not start Explore merely because the current list feels incomplete. Explore\nbegins only from a named evidence gap, bounded query plan, budget, and stop\ncondition.\n\n### 4. Settle Candidate Ranking\n\nBefore reporting candidate intake complete, settle its ranking against the\ncurrent Decision Context:\n\n- record exactly one disposition: `top_window`, `ranked_backlog`, or\n  `no_change`;\n- let the project adapter classify value from exact-read evidence, current\n  objectives, overlap, and artifact convertibility rather than tier alone;\n- require high-value materials to gain verified membership in the Top-N or\n  explicit ranked backlog;\n- require a reason for `no_change` and use it only for standard-value or\n  substantially duplicative materials;\n- keep candidate intake and ranking as separate receipts and, when ranking\n  changes, separate authority revisions; then join them with an intake-ranking\n  settlement receipt;\n- preserve displaced Top-N entries in the ranked backlog and preserve protected\n  anchors unless changed Decision Context or explicit owner authority moves\n  them.\n\nIf ranking apply, readback, projection, or rollback readiness fails, repair or\nroll back before reporting the intake as complete.\n\n### 5. Rebuild Ranked Entries\n\nA ranked entry must represent one independently sortable reading or action\nunit, not a display bucket.\n\n- Default to at most three primary materials per ranked entry.\n- When an entry exceeds the limit, create deterministic child entries and rank\n  them independently.\n- Do not hide overflow in an unranked supporting index.\n- Preserve exact membership: every selected material appears exactly once\n  across the ranked set.\n- Preserve stable material references and canonical source records.\n- Keep an explicit ranked backlog beyond a visible Top-N.\n\nSplitting is semantic, not mechanical. Group materials only when they jointly\nsupport one decision or learning outcome; separate materials whose value,\nurgency, reader action, or evidence maturity differs.\n\n### 6. Propose A Bounded Rerank\n\nRerank from revision-bound Decision Context evidence.\n\n- Protect pinned entries and the project's declared stable prefix.\n- Limit moved entries and rank displacement unless the owner explicitly\n  approves a structural rebuild.\n- Distinguish a rank move from lifecycle change and from new candidate intake.\n- Emit a no-change proposal when evidence does not justify movement.\n- Keep proposal and apply receipt separate.\n\n### 7. Build A Readable Projection\n\nThe managed catalog remains authority, but operators need a readable view.\nBuild that view from exact-read-backed presentation records:\n\n- preserve contiguous ranks and the explicit ranked backlog;\n- keep at most three primary materials per entry;\n- require every expected selected material exactly once;\n- keep project-specific taxonomy, summaries, judgments, links, and language in\n  the private project adapter;\n- emit a content-free receipt with revision, counts, digest, and verification;\n- never treat the readable Markdown as ranking or source authority.\n\nLoopX owns validation, rendering, and the content-free receipt contract. The\nproject adapter owns source parsing and supplies already-promoted display\nrecords. One-time legacy parsing and migration scripts remain project-local.\n\n### 8. Apply With A Lossless Gate\n\nPreview first. Apply only when all are true:\n\n- source and backup digests still match the inventory;\n- parse errors are zero or explicitly owner-approved;\n- expected source\u002Fcanonical counts match;\n- ranked coverage and unique membership are exact;\n- protected entries remain valid;\n- compare-and-swap revision matches;\n- rollback has been rehearsed;\n- the owner gate authorizes this exact plan.\n\nAfter apply, read the destination back and write an audited receipt. On any\nmismatch, restore the previous authority and record the blocker. Never report\n\"migration complete\" from a preparation plan alone.\n\n## Project Adapter Contract\n\nA project-specific skill or `AGENTS.md` may define:\n\n- source locations and private provider setup;\n- topic taxonomy and domain scoring;\n- reading tools and source-specific fallbacks;\n- user-specific priorities;\n- note\u002Farchive destinations and public\u002Fprivate redaction;\n- concrete backup and restore commands.\n\nIt should reference this skill instead of duplicating generic migration,\nranking, rebuild, apply, or rollback rules. Project rules may tighten these\ninvariants but must not weaken them.\n\n## Completion Evidence\n\nA complete material operation reports:\n\n- source and destination revisions;\n- backup and source-digest verification;\n- parsed and canonical counts;\n- lifecycle-count delta;\n- intake ranking disposition and value classification;\n- ranked-entry count and maximum primary-member count;\n- exact coverage and duplicate count;\n- promoted\u002Frejected exact-read evidence;\n- proposal and apply receipt references;\n- intake-ranking settlement receipt reference;\n- rollback result;\n- next bounded action or explicit no-change.\n\n## Stop Conditions\n\nStop without mutating the source when:\n\n- the project or goal is ambiguous;\n- Material Lifecycle is not explicitly active for the selected goal;\n- source authority, backup, revision, or stable ids cannot be verified;\n- exact-read evidence conflicts with the proposed change;\n- overflow would be hidden rather than independently ranked;\n- a migration would lose bytes, records, references, or recoverability;\n- the required owner gate, write scope, or rollback path is absent;\n- public output would expose private material or credentials.\n","# LoopX Material\n\nUse this skill for the lifecycle and authority of a project's durable material\nstore. Source discovery, domain-specific scoring, and note writing may be\nprovided by project skills; this skill owns the generic lossless lifecycle.\n\nLoopX ships the canonical source for this skill, but does not install it into\nthe user's global skill directory. Install a managed copy only in a connected\nproject that explicitly enables Material Lifecycle:\n\n```bash\nloopx project-skill install \\\n  --project . \\\n  --skill loopx-material \\\n  --surface codex \\\n  --execute\n```\n\nUse `--surface claude-code` or `--surface opencode` for those hosts; repeat the\nflag to install multiple host-native copies in one transaction. Managed copies\nlive under `.agents\u002Fskills\u002F`, `.claude\u002Fskills\u002F`, or `.opencode\u002Fskills\u002F` and are\nupgraded or removed through the same CLI. Project-local discovery does not\nitself activate material-store writes; the selected goal still needs explicit\nMaterial Lifecycle authority.\n\n## Activation Gate\n\nBefore changing a material store:\n\n1. Resolve the current project, `goal_id`, registered agent, and active todo\n   through `loopx start-goal --guided`, `loopx status`, or `loopx diagnose`.\n2. Run `loopx project-skill status --project . --skill loopx-material` and\n   confirm the required host surfaces are current.\n3. Confirm the selected todo explicitly targets `material_lifecycle`, or that\n   the goal authority declares an active Material Lifecycle profile and its\n   source store. A catalog entry or project-local skill is not activation.\n4. Confirm the goal boundary covers the exact private adapter and authority\n   paths. Public LoopX contracts never grant access to private source content.\n5. Run `loopx material-lifecycle architecture --format json` and preserve its\n   default-off, owner-gated, provider-neutral boundaries.\n\nIf the project-local skill is missing, preview an explicit project install; do\nnot fall back to a global copy. If activation or authority is missing, stop\nbefore source mutation. Create a bounded setup todo or owner gate; do not\ninvent a store or treat chat history as authority.\n\n## Ownership Boundary\n\nKeep these responsibilities separate:\n\n- **Project source adapter**: locates and reads the project's private source\n  files, database, documents, or provider.\n- **Research\u002Freader skill**: recalls candidates, performs exact reads, and\n  produces source-quality and domain-value evidence.\n- **Decision Context**: supplies revision-bound objectives, changed facts,\n  conflicts, and accepted decisions.\n- **Material Lifecycle**: owns inventory, migration, lifecycle transitions,\n  ranked-entry rebuild, rerank proposals, apply receipts, and rollback.\n- **Content or notes workflow**: consumes selected material and produces an\n  artifact; it does not rewrite candidate\u002Farchive\u002Franking truth by itself.\n\n## Workflow\n\n### 1. Snapshot And Inventory\n\nRead the source authority before proposing structural change.\n\n- Record source revision, byte\u002Fcontent digest, lifecycle counts, parse errors,\n  stable material references, and a verified backup.\n- Keep raw content, private paths, URLs, provider payloads, and credentials out\n  of public packets and commits.\n- Preserve the original source until a verified cutover and rollback rehearsal\n  have both succeeded.\n\nNo migration, rebuild, or rerank may begin from an unverified partial parse.\n\n### 2. Normalize Lifecycle\n\nUse stable material references across:\n\n```text\ncandidate -> active -> archived\n                 \\-> carryover\narchived -> active\n```\n\nEvery transition needs a revisioned evidence or decision reference. Archiving\nmust preserve the original source reference and an archive reference. Reading,\nsummarizing, or publishing a note does not implicitly archive a material.\n\n### 3. Promote Exact-Read Evidence\n\nRecall is advisory. Before a material affects ranking or lifecycle:\n\n1. retrieve the candidate through the configured provider or local search;\n2. exact-read the authoritative source;\n3. record source revision and read scope;\n4. reject stale, conflicting, unreadable, or only-secondary claims;\n5. pass only promoted evidence into Decision Context or ranking.\n\nDo not start Explore merely because the current list feels incomplete. Explore\nbegins only from a named evidence gap, bounded query plan, budget, and stop\ncondition.\n\n### 4. Settle Candidate Ranking\n\nBefore reporting candidate intake complete, settle its ranking against the\ncurrent Decision Context:\n\n- record exactly one disposition: `top_window`, `ranked_backlog`, or\n  `no_change`;\n- let the project adapter classify value from exact-read evidence, current\n  objectives, overlap, and artifact convertibility rather than tier alone;\n- require high-value materials to gain verified membership in the Top-N or\n  explicit ranked backlog;\n- require a reason for `no_change` and use it only for standard-value or\n  substantially duplicative materials;\n- keep candidate intake and ranking as separate receipts and, when ranking\n  changes, separate authority revisions; then join them with an intake-ranking\n  settlement receipt;\n- preserve displaced Top-N entries in the ranked backlog and preserve protected\n  anchors unless changed Decision Context or explicit owner authority moves\n  them.\n\nIf ranking apply, readback, projection, or rollback readiness fails, repair or\nroll back before reporting the intake as complete.\n\n### 5. Rebuild Ranked Entries\n\nA ranked entry must represent one independently sortable reading or action\nunit, not a display bucket.\n\n- Default to at most three primary materials per ranked entry.\n- When an entry exceeds the limit, create deterministic child entries and rank\n  them independently.\n- Do not hide overflow in an unranked supporting index.\n- Preserve exact membership: every selected material appears exactly once\n  across the ranked set.\n- Preserve stable material references and canonical source records.\n- Keep an explicit ranked backlog beyond a visible Top-N.\n\nSplitting is semantic, not mechanical. Group materials only when they jointly\nsupport one decision or learning outcome; separate materials whose value,\nurgency, reader action, or evidence maturity differs.\n\n### 6. Propose A Bounded Rerank\n\nRerank from revision-bound Decision Context evidence.\n\n- Protect pinned entries and the project's declared stable prefix.\n- Limit moved entries and rank displacement unless the owner explicitly\n  approves a structural rebuild.\n- Distinguish a rank move from lifecycle change and from new candidate intake.\n- Emit a no-change proposal when evidence does not justify movement.\n- Keep proposal and apply receipt separate.\n\n### 7. Build A Readable Projection\n\nThe managed catalog remains authority, but operators need a readable view.\nBuild that view from exact-read-backed presentation records:\n\n- preserve contiguous ranks and the explicit ranked backlog;\n- keep at most three primary materials per entry;\n- require every expected selected material exactly once;\n- keep project-specific taxonomy, summaries, judgments, links, and language in\n  the private project adapter;\n- emit a content-free receipt with revision, counts, digest, and verification;\n- never treat the readable Markdown as ranking or source authority.\n\nLoopX owns validation, rendering, and the content-free receipt contract. The\nproject adapter owns source parsing and supplies already-promoted display\nrecords. One-time legacy parsing and migration scripts remain project-local.\n\n### 8. Apply With A Lossless Gate\n\nPreview first. Apply only when all are true:\n\n- source and backup digests still match the inventory;\n- parse errors are zero or explicitly owner-approved;\n- expected source\u002Fcanonical counts match;\n- ranked coverage and unique membership are exact;\n- protected entries remain valid;\n- compare-and-swap revision matches;\n- rollback has been rehearsed;\n- the owner gate authorizes this exact plan.\n\nAfter apply, read the destination back and write an audited receipt. On any\nmismatch, restore the previous authority and record the blocker. Never report\n\"migration complete\" from a preparation plan alone.\n\n## Project Adapter Contract\n\nA project-specific skill or `AGENTS.md` may define:\n\n- source locations and private provider setup;\n- topic taxonomy and domain scoring;\n- reading tools and source-specific fallbacks;\n- user-specific priorities;\n- note\u002Farchive destinations and public\u002Fprivate redaction;\n- concrete backup and restore commands.\n\nIt should reference this skill instead of duplicating generic migration,\nranking, rebuild, apply, or rollback rules. Project rules may tighten these\ninvariants but must not weaken them.\n\n## Completion Evidence\n\nA complete material operation reports:\n\n- source and destination revisions;\n- backup and source-digest verification;\n- parsed and canonical counts;\n- lifecycle-count delta;\n- intake ranking disposition and value classification;\n- ranked-entry count and maximum primary-member count;\n- exact coverage and duplicate count;\n- promoted\u002Frejected exact-read evidence;\n- proposal and apply receipt references;\n- intake-ranking settlement receipt reference;\n- rollback result;\n- next bounded action or explicit no-change.\n\n## Stop Conditions\n\nStop without mutating the source when:\n\n- the project or goal is ambiguous;\n- Material Lifecycle is not explicitly active for the selected goal;\n- source authority, backup, revision, or stable ids cannot be verified;\n- exact-read evidence conflicts with the proposed change;\n- overflow would be hidden rather than independently ranked;\n- a migration would lose bytes, records, references, or recoverability;\n- the required owner gate, write scope, or rollback path is absent;\n- public output would expose private material or credentials.\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Floopx-material",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-material",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-material",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill loopx-material","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Floopx-material\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",278,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Floopx-material\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"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},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]