[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EZJVHRYFHDFBHAVGFCRX98":3,"skill-same:01M7EZJVHRYFHDFBHAVGFCRX98":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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7EZJVHRYFHDFBHAVGFCRX98","automation-audit-ops",null,"Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fautomation-audit-ops\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: automation-audit-ops\ndescription: Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything.\nmetadata:\n  origin: ECC\n---\n\n# Automation Audit Ops\n\nUse this when the user asks what automations are live, which jobs are broken, where overlap exists, or what tooling and connectors are actually doing useful work right now.\n\nThis is an audit-first operator skill. The job is to produce an evidence-backed inventory and a keep \u002F merge \u002F cut \u002F fix-next recommendation set before rewriting anything.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `workspace-surface-audit` for connector, MCP, hook, and app inventory\n- `knowledge-ops` when the audit needs to reconcile live repo truth with durable context\n- `github-ops` when the answer depends on CI, scheduled workflows, issues, or PR automation\n- `ecc-tools-cost-audit` when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app repo\n- `research-ops` when local inventory must be compared against current platform support or public docs\n- `verification-loop` for proving post-fix state instead of relying on assumed recovery\n\n## When to Use\n\n- user asks \"what automations do I have\", \"what is live\", \"what is broken\", or \"what overlaps\"\n- the task spans cron jobs, GitHub Actions, local hooks, MCP servers, connectors, wrappers, or app integrations\n- the user wants to know what was ported from another agent system and what still needs to be rebuilt inside ECC\n- the workspace has accumulated multiple ways to do the same thing and the user wants one canonical lane\n\n## Guardrails\n\n- start read-only unless the user explicitly asked for fixes\n- separate:\n  - configured\n  - authenticated\n  - recently verified\n  - stale or broken\n  - missing entirely\n- do not claim a tool is live just because a skill or config references it\n- do not merge or delete overlapping surfaces until the evidence table exists\n\n## Workflow\n\n### 1. Inventory the real surface\n\nRead the current live surface before theorizing:\n\n- repo hooks and local hook scripts\n- GitHub Actions and scheduled workflows\n- MCP configs and enabled servers\n- connector- or app-backed integrations\n- wrapper scripts and repo-specific automation entrypoints\n\nGroup them by surface:\n\n- local runtime\n- repo CI \u002F automation\n- connected external systems\n- messaging \u002F notifications\n- billing \u002F customer operations\n- research \u002F monitoring\n\n### 2. Classify each item by live state\n\nFor every surfaced automation, mark:\n\n- configured\n- authenticated\n- recently verified\n- stale or broken\n- missing\n\nThen classify the problem type:\n\n- active breakage\n- auth outage\n- stale status\n- overlap or redundancy\n- missing capability\n\n### 3. Trace the proof path\n\nBack every important claim with a concrete source:\n\n- file path\n- workflow run\n- hook log\n- config entry\n- recent command output\n- exact failure signature\n\nIf the current state is ambiguous, say so directly instead of pretending the audit is complete.\n\n### 4. End with keep \u002F merge \u002F cut \u002F fix-next\n\nFor each overlapping or suspect surface, return one call:\n\n- keep\n- merge\n- cut\n- fix next\n\nThe value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.\n\n## Output Format\n\n```text\nCURRENT SURFACE\n- automation\n- source\n- live state\n- proof\n\nFINDINGS\n- active breakage\n- overlap\n- stale status\n- missing capability\n\nRECOMMENDATION\n- keep\n- merge\n- cut\n- fix next\n\nNEXT ECC MOVE\n- exact skill \u002F hook \u002F workflow \u002F app lane to strengthen\n```\n\n## Pitfalls\n\n- do not answer from memory when the live inventory can be read\n- do not treat \"present in config\" as \"working\"\n- do not fix lower-value redundancy before naming the broken high-signal path\n- do not widen the task into a repo rewrite if the user asked for inventory first\n\n## Verification\n\n- important claims cite a live proof path\n- each surfaced automation is labeled with a clear live-state category\n- the final recommendation distinguishes keep \u002F merge \u002F cut \u002F fix-next\n","# Automation Audit Ops\n\nUse this when the user asks what automations are live, which jobs are broken, where overlap exists, or what tooling and connectors are actually doing useful work right now.\n\nThis is an audit-first operator skill. The job is to produce an evidence-backed inventory and a keep \u002F merge \u002F cut \u002F fix-next recommendation set before rewriting anything.\n\n## Skill Stack\n\nPull these ECC-native skills into the workflow when relevant:\n\n- `workspace-surface-audit` for connector, MCP, hook, and app inventory\n- `knowledge-ops` when the audit needs to reconcile live repo truth with durable context\n- `github-ops` when the answer depends on CI, scheduled workflows, issues, or PR automation\n- `ecc-tools-cost-audit` when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app repo\n- `research-ops` when local inventory must be compared against current platform support or public docs\n- `verification-loop` for proving post-fix state instead of relying on assumed recovery\n\n## When to Use\n\n- user asks \"what automations do I have\", \"what is live\", \"what is broken\", or \"what overlaps\"\n- the task spans cron jobs, GitHub Actions, local hooks, MCP servers, connectors, wrappers, or app integrations\n- the user wants to know what was ported from another agent system and what still needs to be rebuilt inside ECC\n- the workspace has accumulated multiple ways to do the same thing and the user wants one canonical lane\n\n## Guardrails\n\n- start read-only unless the user explicitly asked for fixes\n- separate:\n  - configured\n  - authenticated\n  - recently verified\n  - stale or broken\n  - missing entirely\n- do not claim a tool is live just because a skill or config references it\n- do not merge or delete overlapping surfaces until the evidence table exists\n\n## Workflow\n\n### 1. Inventory the real surface\n\nRead the current live surface before theorizing:\n\n- repo hooks and local hook scripts\n- GitHub Actions and scheduled workflows\n- MCP configs and enabled servers\n- connector- or app-backed integrations\n- wrapper scripts and repo-specific automation entrypoints\n\nGroup them by surface:\n\n- local runtime\n- repo CI \u002F automation\n- connected external systems\n- messaging \u002F notifications\n- billing \u002F customer operations\n- research \u002F monitoring\n\n### 2. Classify each item by live state\n\nFor every surfaced automation, mark:\n\n- configured\n- authenticated\n- recently verified\n- stale or broken\n- missing\n\nThen classify the problem type:\n\n- active breakage\n- auth outage\n- stale status\n- overlap or redundancy\n- missing capability\n\n### 3. Trace the proof path\n\nBack every important claim with a concrete source:\n\n- file path\n- workflow run\n- hook log\n- config entry\n- recent command output\n- exact failure signature\n\nIf the current state is ambiguous, say so directly instead of pretending the audit is complete.\n\n### 4. End with keep \u002F merge \u002F cut \u002F fix-next\n\nFor each overlapping or suspect surface, return one call:\n\n- keep\n- merge\n- cut\n- fix next\n\nThe value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.\n\n## Output Format\n\n```text\nCURRENT SURFACE\n- automation\n- source\n- live state\n- proof\n\nFINDINGS\n- active breakage\n- overlap\n- stale status\n- missing capability\n\nRECOMMENDATION\n- keep\n- merge\n- cut\n- fix next\n\nNEXT ECC MOVE\n- exact skill \u002F hook \u002F workflow \u002F app lane to strengthen\n```\n\n## Pitfalls\n\n- do not answer from memory when the live inventory can be read\n- do not treat \"present in config\" as \"working\"\n- do not fix lower-value redundancy before naming the broken high-signal path\n- do not widen the task into a repo rewrite if the user asked for inventory first\n\n## Verification\n\n- important claims cite a live proof path\n- each surfaced automation is labeled with a clear live-state category\n- the final recommendation distinguishes keep \u002F merge \u002F cut \u002F fix-next\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fecc\u002Fautomation-audit-ops","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill automation-audit-ops",{"tool":38,"command":39},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill automation-audit-ops",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill automation-audit-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fecc\u002Fautomation-audit-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},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\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},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\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},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\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},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\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},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\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},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]