Skip to content

[P2] Define cross-library skill compatibility and publication boundaries #37

Closed

Description

@anthonyandrei

Problem

grill-with-docs and offload have different responsibilities. Vendor-specific instructions in the published grilling skill would force every skill library to understand every worker vendor.

Deliverable

Document and test the publication boundary:

  • grill-with-docs defines the interview and documentation workflow.
  • offload provides optional secure worker delegation.
  • Vendor adapters stay in offload or its adapter packages.
  • Published consumers depend on stable profiles and capabilities, not model IDs or vendor names.

Define versioning, compatibility, and release guidance for the source skill and each adapter.

Acceptance criteria

  • grill-with-docs works without offload, AGY, Codex, Claude, or any vendor CLI.
  • grill-with-docs contains no vendor-specific model routing or security claims.
  • offload integration is explicit and optional.
  • The adapter contract, helper-family contracts, and skill instructions have documented compatibility rules.
  • Vendor model releases can update an adapter without requiring a PR to every consumer skill.
  • A compatibility check detects a published skill that imports an unavailable adapter or names an unsupported vendor feature.
  • Release instructions identify the source of truth and the generated or installed copies that must not be edited directly.
  • The documentation distinguishes capability support from security enforcement.
  • A migration note explains how existing AGY-only consumers move to the vendor-neutral contract.

Dependencies

Out of scope

  • Publishing to external libraries as part of this issue.
  • Implementing every vendor adapter.
  • Making all vendors behave identically.

Implementation pointers

  • SKILL.md
  • README.md
  • CONTEXT.md
  • docs/adr/
  • .github/workflows/ci.yml

Activity

  1. anthonyandrei commented on Sep 4, 2026

    @anthonyandrei
    OwnerAuthor

    Resolved by PR #39 (#39). The merged implementation covers this issue, and the targeted acceptance tests pass. Closing as completed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions