[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FMM99CJ743GQVFVAC3DPC":3,"skill-same:01M70FMM99CJ743GQVFVAC3DPC":73},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70FMM99CJ743GQVFVAC3DPC","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fautomation-audit-ops\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"audit","ops","automation","automation audit","automation audit ops","first","connectors","audit workflow","use","missing","for","evidence","live","workflow","when","MCP","hooks","inventory","which","broken","2026-11-10 10:12:30",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":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fautomation-audit-ops",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill automation-audit-ops",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill automation-audit-ops",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill automation-audit-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fautomation-audit-ops\u002FSKILL.md",true,[],[74,82,90,97,104,111],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":89},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":89},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":89},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":89},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":89},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]