Lean on oss standards

Skill selamy-labs/agent-skills/skills/lean-on-oss-standards

Reusable public SKILL.md workflows for AI agents

Install

npx -y skills add selamy-labs/agent-skills --skill lean-on-oss-standards

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when choosing implementation patterns for observability, runtime configuration, API typing, CI, auth, or infrastructure. Biases toward proven open standards before custom machinery.

SKILL.md

2.1 KB, 415 tokens by cl100k_base, as published. Nobody here has run it

Lean On OSS Standards

Before building custom machinery, reach for the battle-tested open standard that already solves the problem. Most cross-cutting concerns — how a service emits telemetry, flips a flag at runtime, types an API, gates CI — have a standard the ecosystem has already hardened. Adopt it; spend your invention budget on the domain logic that is actually yours.

The test

For any infrastructure-shaped decision, ask: is there a proven open standard for this exact concern?

Yes → adopt it, even if it is slightly heavier than a hand-rolled version today. You inherit its tooling, docs, integrations, and bug fixes.
No, but the repo already has a strong local pattern → follow the local pattern; consistency beats a second standard.
Genuinely no standard → only then build, and keep the surface small so a standard can replace it later.

Examples of the standards to reach for

These are illustrations of the discipline, not the point:

Observability: OpenTelemetry traces, metrics, and structured logs.
Runtime knobs: OpenFeature or the repository's existing flag client.
API typing: shared types and typed RPC clients.
Infrastructure: declarative IaC, package-native charts, GitOps, managed secret stores, keyless workload identity.
CI/test policy: ecosystem-native test tools plus required status checks.

Anti-pattern: bespoke reinvention

The smell is a homegrown component that re-implements what a standard already does — a custom metrics wire format instead of OTel, a hand-rolled flag service instead of OpenFeature, a one-off secret loader instead of a managed store. It costs nothing the day you write it and everything later: no ecosystem, no integrations, and a maintenance burden only you carry. If you find yourself designing protocol-level plumbing for a solved concern, stop and adopt the standard.