affaan-m/ecc

automation-audit-ops

Evidence-first automation inventory and overlap audit workflow for ECC.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/affaan-m/ecc --skill automation-audit-ops

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Automation Audit Ops

Use 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.

This is an audit-first operator skill. The job is to produce an evidence-backed inventory and a keep / merge / cut / fix-next recommendation set before rewriting anything.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • workspace-surface-audit for connector, MCP, hook, and app inventory
  • knowledge-ops when the audit needs to reconcile live repo truth with durable context
  • github-ops when the answer depends on CI, scheduled workflows, issues, or PR automation
  • ecc-tools-cost-audit when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app repo
  • research-ops when local inventory must be compared against current platform support or public docs
  • verification-loop for proving post-fix state instead of relying on assumed recovery

When to Use

  • user asks "what automations do I have", "what is live", "what is broken", or "what overlaps"
  • the task spans cron jobs, GitHub Actions, local hooks, MCP servers, connectors, wrappers, or app integrations
  • the user wants to know what was ported from another agent system and what still needs to be rebuilt inside ECC
  • the workspace has accumulated multiple ways to do the same thing and the user wants one canonical lane

Guardrails

  • start read-only unless the user explicitly asked for fixes
  • separate:
  • configured
  • authenticated
  • recently verified
  • stale or broken
  • missing entirely
  • do not claim a tool is live just because a skill or config references it
  • do not merge or delete overlapping surfaces until the evidence table exists

Workflow

1. Inventory the real surface

Read the current live surface before theorizing:

  • repo hooks and local hook scripts
  • GitHub Actions and scheduled workflows
  • MCP configs and enabled servers
  • connector- or app-backed integrations
  • wrapper scripts and repo-specific automation entrypoints

Group them by surface:

  • local runtime
  • repo CI / automation
  • connected external systems
  • messaging / notifications
  • billing / customer operations
  • research / monitoring

2. Classify each item by live state

For every surfaced automation, mark:

  • configured
  • authenticated
  • recently verified
  • stale or broken
  • missing

Then classify the problem type:

  • active breakage
  • auth outage
  • stale status
  • overlap or redundancy
  • missing capability

3. Trace the proof path

Back every important claim with a concrete source:

  • file path
  • workflow run
  • hook log
  • config entry
  • recent command output
  • exact failure signature

If the current state is ambiguous, say so directly instead of pretending the audit is complete.

4. End with keep / merge / cut / fix-next

For each overlapping or suspect surface, return one call:

  • keep
  • merge
  • cut
  • fix next

The value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.

Output Format

text
CURRENT SURFACE
- automation
- source
- live state
- proof

FINDINGS
- active breakage
- overlap
- stale status
- missing capability

RECOMMENDATION
- keep
- merge
- cut
- fix next

NEXT ECC MOVE
- exact skill / hook / workflow / app lane to strengthen

Pitfalls

  • do not answer from memory when the live inventory can be read
  • do not treat "present in config" as "working"
  • do not fix lower-value redundancy before naming the broken high-signal path
  • do not widen the task into a repo rewrite if the user asked for inventory first

Verification

  • important claims cite a live proof path
  • each surfaced automation is labeled with a clear live-state category
  • the final recommendation distinguishes keep / merge / cut / fix-next

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
affaan-m
社区

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24小时安装量
489
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1小时安装量
5
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日
affaan-m
社区

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1小时安装量
2
GitHub Stars
30.8万
最近更新
11月20日