[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FHENP54SMGZHCT8MYKEYE":3,"skill-same:01M78FHENP54SMGZHCT8MYKEYE":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78FHENP54SMGZHCT8MYKEYE","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.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\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.\norigin: 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,"origin":24,"description":7},"ECC","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fterminal-ops","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill terminal-ops",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill terminal-ops",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill terminal-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fterminal-ops\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"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},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]