agentleFS
Microsoft AzureKnown publisherAzure/git-ape/.github/community-skills/scale-and-sre/SKILL.md

scale-and-sre

Skill274 starsChanged 28 days agoMITView on GitHub

Implements production scale, reliability, and observability patterns for multi-tenant SaaS platforms.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Architect multitenant solutions on Azure to assess shared-resource limits, tenant density, blast radius, fairness, and operational …

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scale and SRE

Applies day-2 engineering best practices for growth and stability.

Focus areas

  • Horizontal scaling and partitioning strategy.
  • Deployment-stamp capacity, tenant placement, and scale-out thresholds.
  • Noisy-neighbor detection, resource governance, throttling, and per-tenant quotas.
  • Availability, backup, and disaster recovery.
  • SLO/SLI design and alerting model.
  • Tenant-aware telemetry, health, usage, and cost attribution without leaking tenant data.
  • Incident response and operational dashboards.

Use Architect multitenant solutions on Azure to assess shared-resource limits, tenant density, blast radius, fairness, and operational automation. Define both platform-wide and tenant-level service objectives where appropriate.

Deliverables

  • SRE baseline for production operations.
  • Capacity and resiliency validation checklist.
  • Per-tenant observability, quota, metering, and cost-allocation model.
  • Runbook set for common failure domains.

Download now (ZIP)

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.