跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 automation-audit-ops

Automation Audit Ops

证据-首次自动化盘存和ECC审计工作流程重叠。 当用户想要知道哪些工作,钩子,连接器,MCP服务器,或包装器在修复任何东西之前是活的,破损的,冗余的,或缺失的时使用.

7432 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

证据首次自动化盘存和ECC重叠审计工作流程

何时用

- 用户询问"我有什么自动化设备","什么是活的","什么是被打破",或者"什么是重叠的"

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Automation Audit Ops、Skill Stack、When to Use、Guardrails、Workflow、1. Inventory the real surface。 其中含规范建议的小节:分步指令。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

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.

Automation Audit OpsSkill StackWhen to UseGuardrailsWorkflow1. Inventory the real surface2. Classify each item by live state3. Trace the proof path4. End with keep / merge / cut / fix-nextOutput FormatPitfallsVerification

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
automation-audit-ops
description
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.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「automation-audit-ops」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-d5f00a726d67ca3e-%E8%87%AA%E5%8A%A8%E5%8C%96%E5%AE%A1%E8%AE%A1%E4%B8%9A%E5%8A%A1.html
请存为 .cursor/skills/automation-audit-ops/SKILL.md 或 .claude/skills/automation-audit-ops/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/affaan-m/ecc' --list

npx skills add 'https://github.com/affaan-m/ecc' --skill 'automation-audit-ops'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版

name: automation-audit-ops description: 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. metadata: origin: ECC

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

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

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…