Buy vs build audit
Skill stdin/buy-vs-build/plugins/buy-vs-build/skills/buy-vs-build-audit
Use when auditing a repository or subsystem for avoidable in-house implementations, unnecessary dependencies, duplicated platform features, vendor lock-in, maintenance burden, or unclear buy-vs-build ownership decisions.From its SKILL.md
npx -y skills add stdin/buy-vs-build --skill buy-vs-build-auditAssembled 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.5 KB, 252 tokens by cl100k_base, as published. Nobody here has run it
Buy vs Build Audit
Audit the repository for ownership choices that deserve a second look. This is broader than a diff review: scan dependencies, common utilities, integration code, and high-maintenance subsystems.
Workflow
- Inspect dependency manifests and major source directories.
- Find custom implementations in standardized domains: dates, parsing, auth, crypto, queues, retries, validation, file formats, email, payments, observability, and search.
- Find dependencies that duplicate built-ins, native platform features, installed packages, or small clear code.
- Separate "fix now" from "watch later"; churn without payoff is not an improvement.
- Preserve safety boundaries: validation, security, privacy, accessibility, observability, and explicit requirements.
Output
Group results by action:
- Replace with reuse: custom code that should move to a built-in, platform feature, library, or service.
- Keep in-house: code that is core, small, constrained, or safer to own.
- Remove dependency: dependency that does not earn its ownership cost.
- Needs decision note: unclear tradeoffs requiring maintainer input.
For each item, include the likely rung, owner impact, and migration risk.
What ships with it: 1 file
217 B alongside SKILL.md
agents/
- openai.yaml217 B
Gives 0 of the 12 instructions most audit compliance skills give in 252 tokens
Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06
- Read product marketing context before asking questionsin 29 of 960, across 11 files
- Rank findings by severityin 29 of 960, across 22 files
- Generate audit reportin 22 of 960
- Run the audit scriptin 20 of 960, across 19 files
- Generate a prioritized action plan reportin 19 of 960, across 11 files
- Ensure one H1 per pagein 15 of 960, across 5 files
- Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
- Verify alt text on all imagesin 12 of 960, across 3 files
- Determine the audit scope before startingin 12 of 960, across 4 files
- Verify important pages allowed in robots.txtin 11 of 960, across 2 files
- Detect business type from homepage signalsin 11 of 960, across 7 files
- Delegate specialized tasks to subagentsin 11 of 960, across 7 files
Said here and by no other author read
- Inspect dependency manifests and major source directories
- Find custom implementations in standardized domains
- Find dependencies that duplicate built-ins or native features
- Separate fix now from watch later
- Preserve safety boundaries
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.