SkillAgentSearch skills...

open-core-boundary

Review Exeris changes through the Open-Core boundary — SPI/Core/Community/Enterprise placement, leakage risks, and smallest boundary-safe approach.

Install / Use

npx skills add exeris-systems/exeris-kernel

Installs into whichever agent you are using.

About this skill

Claude Commands

Claude Code slash commands

Quality Score

44/100

Category

Automation

Supported Platforms

Claude Code
OpenAI Codex

DO NOT EDIT — generated from .agents/workflows/open-core-boundary.md (agents-md-schema.md rule 7). Edit the source.

description: Review Exeris changes through the Open-Core boundary — SPI/Core/Community/Enterprise placement, leakage risks, and smallest boundary-safe approach. argument-hint: Change scope to evaluate through Open-Core split

<!-- DO NOT EDIT. Generated from .agents/workflows/open-core-boundary.md by the AGENTS.md adapter step (agents-md-schema.md rule 7). Edit the source, not this file. -->

Review this change specifically through the Exeris Open-Core boundary.

Change: $ARGUMENTS

Questions to answer:

  1. Is this capability part of SPI contract, Core shared infrastructure, Community OSS implementation, or Enterprise-only specialization?
  2. Does this change accidentally move Enterprise-specific detail into Core or SPI?
  3. Does this change weaken the Community experience in a way that violates the open-core intent?
  4. Does this align with the current Core/Community/Enterprise split?
  5. What is the smallest boundary-safe implementation approach?

Optimize for open-core clarity: Community should remain strong, but Enterprise-only implementation detail must not leak upward.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
UpdatedNaNy ago
Forks0

Security Score

68/100

Audited on Invalid Date

2 medium1 low