Project vendor boundary
Skill n-n-code/n-n-code-skills/.agents/skills/project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.From its SKILL.md
npx -y skills add n-n-code/n-n-code-skills --skill project-vendor-boundaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 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.3 KB, 210 tokens by cl100k_base, as published. Nobody here has run it
Project Vendor Boundary
This is a composable overlay, not a standalone workflow. Use alongside the repo's implementation skill when work touches vendored dependencies or their integration boundary.
When to use
The change involves vendored third-party code, the boundary between app-owned and vendored code, or dependency integration (subtrees, vendor directories, copied sources).
Not for
App-owned code that does not touch vendor boundaries (use the implementation skill directly), or release/packaging concerns (use project-release-maintainer).
Rules
- prefer app-side integration changes before editing vendored code
- treat vendored code as subtree/vendor content, not normal project code
- keep notices, provenance, upstream version/source, local patch rationale, and install rules aligned with vendor changes
- prefer adapter or wrapper changes in app-owned code before patching vendored sources; patch vendor code only when the seam cannot reasonably absorb the change
- avoid unrelated churn inside vendor trees
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 210 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- prefer app-side integration changes before editing vendored code
- treat vendored code as subtree content
- keep notices and provenance aligned with vendor changes
- record local patch rationale
- record upstream version and source
- align install rules with vendor changes
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.