oxy-compile-boundary

oxy-compile-boundary is a Design patterns & component architecture skill for AI agents, published by oxy-hq in the oxygen repository on GitHub. Skillspace rates oxy-compile-boundary D (68/100) and it passed the safety scan; the rating is based on static analysis only.

Use when adding a new YAML entity type to Oxy (e.g. a new file extension under `crates/oxy-compile/src/walker.rs` like `.foo.yml`), when introducing a new runtime read site that walks the workspace filesystem, when wiring a new handler that calls `ConfigManager::resolve_*` or `fs::read_to_string(workspace_path...)`, or any time someone proposes a feature that "just reads from the workspace dir." Also triggers on phrases like "new file extension", "add a YAML config", "load this from disk", "scan the workspace for", "read the YAML file" — the compile boundary expects every NEW workspace artifact to be a row in Postgres, not a per-request FS read.

Grade
D
Quality
68 / 100
Safety
Passed
GitHub stars
203

Unproven: rated by static analysis only, not yet compared head-to-head.

Our two independent classifiers differ on this skill's category, so treat the placement as provisional.

This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.

Our review

Architecture
100 / 100
Maturity
Basic: a single SKILL.md
Security scan
No issues found
License
Apache-2.0
Adoption
Adopted by 0 other repositories, in 0 collections

Not checked yet

  • Not judged on the rubric yet (not a contender in its category)
  • No blind task eval yet
  • Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
  • Sibling files (scripts, references) not fetched; security scan covers SKILL.md only

Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.