Buy vs build
Use when coding, designing implementations, choosing dependencies, or reviewing whether a task should use built-ins, platform features, installed packages, open source, commercial services, or in-house code.From its SKILL.md
npx -y skills add stdin/buy-vs-build --skill buy-vs-buildAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 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.
SKILL.md
1.0 KB, 175 tokens by cl100k_base, as published. Nobody here has run it
Buy vs Build
Before writing code, decide whether the work should be bought, reused, or built.
First classify it: core (differentiation) or context, and commodity (stable) or novel. Reuse context and commodity work; build in-house only where core meets novel. Scale scrutiny to reversibility.
Stop at the first rung that satisfies the requirement:
- Do nothing.
- Use the standard library.
- Use the native platform.
- Use already-installed dependencies.
- Use mature open source.
- Use a commercial service or product.
- Build in-house only when reuse fails the real constraints.
For non-obvious decisions, compare fit, ownership, cost, security, licensing, maintenance, integration, maturity, and exit risk. Preserve validation, security, privacy, accessibility, observability, and explicit requirements.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.