[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JDME1DAW3CS0CE0HKTZ2CX":3,"skill-same:01M6JDME1DAW3CS0CE0HKTZ2CX":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6JDME1DAW3CS0CE0HKTZ2CX","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.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fterminal-ops\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"terminal ops","ops","terminal","fix","for","verified","with","proof","evidence","use","user","command","repo","first","execution","ci","run","workflow","2026-11-10 10:12:30",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":46,"description":7},"ECC","master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fterminal-ops",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add S3YED\u002Fappie-kit --skill terminal-ops",{"tool":61,"command":62},"bunx","bunx skills add S3YED\u002Fappie-kit --skill terminal-ops",{"tool":64,"command":65},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill terminal-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fterminal-ops\u002FSKILL.md",true,[],[70,102,137,163,194,216],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":83,"publishedAt":41},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[76,79,82],{"categoryNo":77,"categoryName":78,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":116,"publishedAt":41},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"publishedAt":41},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[143,144],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},[118,146,122,147,148,149,124,150,151,152,153,154,155,156,157,158,159,160,161,162],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":41},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"publishedAt":41},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[200],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[202,203,204,205,206,207,40,208,209,210,211,212,213,214,33,215,27],"workflows","quality","software","software quality workflows","review","tdd","commit","debugging","code","debugger","pre-commit","investigation","code simplification","simplification",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":229,"publishedAt":41},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[222,225,228],{"categoryNo":223,"categoryName":224,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":226,"categoryName":227,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[230,231,232,233,234,235,236,237,177,238,239,124,240,180,241,210,242,243,244,245],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","safe","typescript","react components","modular","refactor","simplify","patterns","test-driven-development"]