Skip to content

[Phase 1] Agent-native discovery and compatibility #33

Closed

Description

@mrgoonie

Depends on

Objective

Make SkillX equally useful to humans and agents for discovery, inspection, and compatibility reasoning.

Scope

  • Compatibility-aware search/detail UI and API.
  • Declared vs verified support.
  • Structured CLI JSON output.
  • Remote read-only MCP.
  • WebMCP read tools as progressive enhancement.
  • Markdown variants of public content routes.
  • Copy Markdown, llms.txt, llms-full.txt, canonical/sitemap work.

Implementation tasks

  • Add --compatible <runtime> search filter.
  • Add skillx inspect.
  • Add skillx check --target.
  • Standardize CLI JSON/error envelope/exit codes.
  • Add compatibility badges with evidence details.
  • Build remote MCP package/server.
  • Implement search_packages, get_package, get_release, check_compatibility, get_kit.
  • Add WebMCP feature detection and read tools.
  • Implement route-level Markdown renderers.
  • Add Link: rel=alternate/canonical behavior where appropriate.
  • Add Copy page as Markdown.
  • Add authorization-aware Copy SKILL.md.
  • Add /llms.txt and /llms-full.txt.
  • Add publisher/harness landing docs.
  • Add parity tests across API/CLI/MCP/Markdown.

Acceptance criteria

An agent can discover a package, inspect requirements, see evidence, and understand incompatibility without scraping HTML.

Browser support for WebMCP is optional; normal web remains fully functional.

Activity

  1. self-assigned this
    on Oct 19, 2026
  2. added and removed on Oct 19, 2026
  3. mrgoonie commented on Oct 20, 2026

    @mrgoonie
    ContributorAuthor

    Production receipt (2026-10-20)

    Delivered by #97 (squash 79f98fb). It went through 3 isolated review rounds; the last was CLEAN at 2be37c3.

    • One JSON envelope and one exit-code table for every CLI command. The installer uses the shared runCommand. There is no process.exit on command paths. The exit codes are 0 ok, 2 usage, 3 not found, 5 auth, and 7 rate limited (including a registry 429 on install, update, sync, promote and publish).
    • MCP get_kit.
    • WebMCP get_release and get_package. They mirror POST /api/mcp with the same names, schemas and access codes.
    • Parity tests, plus the contracts in the CLI.
    • Tests: pnpm test reported 116 files, 2357 passed and 2 skipped. Typecheck and build passed.

    Production (worker version 7d29ff0a, smoke at 09:57 +07):

    • tools/list lists search_packages, get_package, get_release, check_compatibility and get_kit.
    • get_release {package: "@bestagentkits/plan", version: "0.1.0"} is found, with releaseDigest sha256:08b0fce1…cbac65, state published.
    • get_package returns a live listing slug as found.
    • get_kit returns not_found for anonymous callers and found for the owner key (a private kit, effective revision 2).

    The CLI ships to npm when the next release-please PR merges.

  4. added
    shippedMerged/deployed
    and removed on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestshippedMerged/deployed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions