agentleFS
toddcox-doittoddcox-doit/claude-skills/automation-potential-analysis-v1-v2.0/SKILL.md

automation-potential-analysis-v1-v2.0

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Analyze the automation POTENTIAL of a PerfectScale cluster, CLI-first via `pscli` for cluster totals/waste/custom-grouping candidates — find every workload that is NOT yet automated but IS eligible (excluding "Not Supported"), then report how many could be automated and the aggregate potential savings, where that savings is concentrated, and which repeated workload names are custom-grouping candidates. Use this whenever the user asks about automation potential, automation opportunity, "what could we automate", "how much could we save by automating", non-automated workloads, "what's not automated yet", automation candidates, or wants a pre-automation / proof-of-value savings estimate for a customer's cluster. This is forward-looking (what automation COULD do) — distinct from the automation-impact-analyzer skill (what automation HAS already done). Trigger even if the user just names a cluster and asks "how much automation upside is here".

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.