[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79QCF22XB95E4QABXASF8K8":3,"skill-same:01M79QCF22XB95E4QABXASF8K8":47},{"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":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79QCF22XB95E4QABXASF8K8","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.","JunMystery\u002FAgent-Guidance","JunMystery","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F161468934?v=4","01M79MTMV8F0BY8NK1A92RA8A0","Jun","01M79MTMWCFBKPHN5B25E6V20B",0,"MIT","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\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","5d0a87185c0e172c3901e2a6e5916b6d544b8b94","skills\u002Fterminal-ops","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance","https:\u002F\u002Fgithub.com\u002FJunMystery","AI is the typist, I am the architect. Building efficient, secure, and user-centric products through disciplined AI prompt engineering.","2026-11-13 17:41:25",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add JunMystery\u002FAgent-Guidance --skill terminal-ops",{"tool":39,"command":40},"bunx","bunx skills add JunMystery\u002FAgent-Guidance --skill terminal-ops",{"tool":42,"command":43},"pnpm","pnpm dlx skills add JunMystery\u002FAgent-Guidance --skill terminal-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fterminal-ops\u002FSKILL.md",true,[],[48,54,60,66,72,78],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M79QR1E309VJ6CTQKB32AWWA","zero-trust-architecture-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-architecture-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"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":57,"categories":58,"keywords":59,"publishedAt":19},"01M79QQV7GHYR02DYGN41S23WN","xss-filter-evasion-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxss-filter-evasion-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"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":63,"categories":64,"keywords":65,"publishedAt":19},"01M79QQNSN7YB8XB61FFSCS3WH","xs-leaks-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxs-leaks-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M79QQHZZJKFDY9132G5A65C2","xpath-injection-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxpath-injection-prevention-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"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":75,"categories":76,"keywords":77,"publishedAt":19},"01M79QQB9ZSD3DJG8658EHQXR1","xml-security-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-security-cheat-sheet\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"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":81,"categories":82,"keywords":83,"publishedAt":19},"01M79QQ60WKV7PFMXWT9CW8PM6","xml-external-entity-prevention-cheat-sheet","https:\u002F\u002Fgithub.com\u002FJunMystery\u002FAgent-Guidance\u002Fblob\u002Fmain\u002Fskills\u002Fxml-external-entity-prevention-cheat-sheet\u002FSKILL.md",[],[]]