agentleFS
toddcox-doittoddcox-doit/claude-skills/perfectscale-optimization-plan/SKILL.md

perfectscale-optimization-plan

Skill0 starsChanged 2 months agoNo licenceView on GitHub

Produce a sequenced, ROI-ranked PerfectScale optimization plan for a customer tenant — a working-session worksheet (Markdown + self-contained HTML, plus XLSX/CSV and JSON) that a solutions engineer screen-shares with the customer's platform/K8s and FinOps team to decide what to do first, second, and third. Converts findings into discrete Actions, scores each as (monthly savings x confidence) / effort, assigns owner + prerequisite + verification method, groups into Phase 1 (0-30d quick wins) / Phase 2 (30-90d structural) / Phase 3 (90d+ govern), and promotes unblocker actions whose own dollar value understates what they release. Use for: "optimization plan", "optimization strategy", "optimization roadmap", "detailed optimization steps", "optimization session", "where do we start", "what's the highest ROI", "prioritized action plan", "how do we capture these savings", "sequence the work", "quick wins", "90-day plan", "phased rollout plan", "customer working session", "drive the conversation with the customer", "regenerate the plan", "re-run the analysis for this tenant". Distinct from perfectscale-tenant-savings-report-v2.0 (finds and reports the opportunity, organized by cluster — this skill consumes that and organizes by what you DO, in order). Also covers the executive one-pager: `scripts/exec_summary.js` renders a one-page buying-decision summary (.docx) straight from the plan JSON, so use this skill for "executive brief", "exec summary", "one-pager" or "buying-decision brief" too. The separate perfectscale-executive-1pager skill was retired on 2026-10-21 and now lives in `~/.claude/skills-archive`.

  • Installs packages

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    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.