[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETF007983WMRZNHQKHFP2W":3,"skill-same:01M7ETF007983WMRZNHQKHFP2W":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ETF007983WMRZNHQKHFP2W","terminal-ops",null,"Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.","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\u002F04-安全渗透\u002Fterminal-ops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: terminal-ops\ndescription: Evidence-first repo execution workflow for ECC. Use when the user wants a command run, a repo checked, a CI failure debugged, or a narrow fix pushed with exact proof of what was executed and verified.\nmetadata:\n  origin: ECC\n---\n\n# Terminal Ops\n\nUse this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.\n\nThis skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `verification-loop` for exact proving steps after changes\n- `tdd-workflow` when the right fix needs regression coverage\n- `security-review` when secrets, auth, or external inputs are involved\n- `github-ops` when the task depends on CI runs, PR state, or release status\n- `knowledge-ops` when the verified outcome needs to be captured into durable project context\n\n## When to Use\n\n- user says \"fix\", \"debug\", \"run this\", \"check the repo\", or \"push it\"\n- the task depends on command output, git state, test results, or a verified local fix\n- the answer must distinguish changed locally, verified locally, committed, and pushed\n\n## Guardrails\n\n- inspect before editing\n- stay read-only if the user asked for audit\u002Freview only\n- prefer repo-local scripts and helpers over improvised ad hoc wrappers\n- do not claim fixed until the proving command was rerun\n- do not claim pushed unless the branch actually moved upstream\n\n## Workflow\n\n### 1. Resolve the working surface\n\nSettle:\n\n- exact repo path\n- branch\n- local diff state\n- requested mode:\n  - inspect\n  - fix\n  - verify\n  - push\n\n### 2. Read the failing surface first\n\nBefore changing anything:\n\n- inspect the error\n- inspect the file or test\n- inspect git state\n- use any already-supplied logs or context before re-reading blindly\n\n### 3. Keep the fix narrow\n\nSolve one dominant failure at a time:\n\n- use the smallest useful proving command first\n- only escalate to a bigger build\u002Ftest pass after the local failure is addressed\n- if a command keeps failing with the same signature, stop broad retries and narrow scope\n\n### 4. Report exact execution state\n\nUse exact status words:\n\n- inspected\n- changed locally\n- verified locally\n- committed\n- pushed\n- blocked\n\n## Output Format\n\n```text\nSURFACE\n- repo\n- branch\n- requested mode\n\nEVIDENCE\n- failing command \u002F diff \u002F test\n\nACTION\n- what changed\n\nSTATUS\n- inspected \u002F changed locally \u002F verified locally \u002F committed \u002F pushed \u002F blocked\n```\n\n## Pitfalls\n\n- do not work from stale memory when the live repo state can be read\n- do not widen a narrow fix into repo-wide churn\n- do not use destructive git commands\n- do not ignore unrelated local work\n\n## Verification\n\n- the response names the proving command or test\n- git-related work names the repo path and branch\n- any push claim includes the target branch and exact result\n","# Terminal Ops\n\nUse this when the user wants real repo execution: run commands, inspect git state, debug CI or builds, make a narrow fix, and report exactly what changed and what was verified.\n\nThis skill is intentionally narrower than general coding guidance. It is an operator workflow for evidence-first terminal execution.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `verification-loop` for exact proving steps after changes\n- `tdd-workflow` when the right fix needs regression coverage\n- `security-review` when secrets, auth, or external inputs are involved\n- `github-ops` when the task depends on CI runs, PR state, or release status\n- `knowledge-ops` when the verified outcome needs to be captured into durable project context\n\n## When to Use\n\n- user says \"fix\", \"debug\", \"run this\", \"check the repo\", or \"push it\"\n- the task depends on command output, git state, test results, or a verified local fix\n- the answer must distinguish changed locally, verified locally, committed, and pushed\n\n## Guardrails\n\n- inspect before editing\n- stay read-only if the user asked for audit\u002Freview only\n- prefer repo-local scripts and helpers over improvised ad hoc wrappers\n- do not claim fixed until the proving command was rerun\n- do not claim pushed unless the branch actually moved upstream\n\n## Workflow\n\n### 1. Resolve the working surface\n\nSettle:\n\n- exact repo path\n- branch\n- local diff state\n- requested mode:\n  - inspect\n  - fix\n  - verify\n  - push\n\n### 2. Read the failing surface first\n\nBefore changing anything:\n\n- inspect the error\n- inspect the file or test\n- inspect git state\n- use any already-supplied logs or context before re-reading blindly\n\n### 3. Keep the fix narrow\n\nSolve one dominant failure at a time:\n\n- use the smallest useful proving command first\n- only escalate to a bigger build\u002Ftest pass after the local failure is addressed\n- if a command keeps failing with the same signature, stop broad retries and narrow scope\n\n### 4. Report exact execution state\n\nUse exact status words:\n\n- inspected\n- changed locally\n- verified locally\n- committed\n- pushed\n- blocked\n\n## Output Format\n\n```text\nSURFACE\n- repo\n- branch\n- requested mode\n\nEVIDENCE\n- failing command \u002F diff \u002F test\n\nACTION\n- what changed\n\nSTATUS\n- inspected \u002F changed locally \u002F verified locally \u002F committed \u002F pushed \u002F blocked\n```\n\n## Pitfalls\n\n- do not work from stale memory when the live repo state can be read\n- do not widen a narrow fix into repo-wide churn\n- do not use destructive git commands\n- do not ignore unrelated local work\n\n## Verification\n\n- the response names the proving command or test\n- git-related work names the repo path and branch\n- any push claim includes the target branch and exact result\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fterminal-ops",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill terminal-ops",{"tool":40,"command":41},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill terminal-ops",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill terminal-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fterminal-ops\u002FSKILL.md",true,[],[49,57,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"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",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":56},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":56},"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":56},"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":56},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":56},"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",[],[]]