holocron/plugins/core/skills/provider-adapter-author/SKILL.md at a8beff7d2c33b451651fafecb2b1a51f2723a9dd

Files

Defame1297 38f1ba4e03 fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery

Claude Code's (and Copilot's) native plugin installer has zero awareness of
.apm/ nesting -- it convention-scans only flat skills/, agents/, commands/,
hooks.json at each plugin's root. Confirmed via strings on the installed
claude binary and live installs of git@holocron/gitea@holocron/kyberforge@
holocron, all reporting Skills(0) Agents(0) Hooks(0) post ADR-0015's apm
conversion. Root cause (apm_cli/core/plugin_manifest.py): apm's plugin.json
compiler deliberately strips skills/agents/commands keys, assuming the host
already auto-discovers those convention directories -- it has no model of
.apm/ being host-visible at all. Separately, apm's own bundle exporter
(apm_cli/bundle/plugin_exporter.py, behind `apm pack --format plugin`)
implements the correct .apm/ -> flat mapping, but only ever targeted
build/<name>-<version>/, a path nothing in marketplace.json's source: points
at.

scripts/sync-plugin-content.sh wraps that bundle exporter and copies its
agents/, skills/, commands/, instructions/, extensions/, and merged
hooks.json back into each plugin's own root as a second tracked
compiled-output category -- same governance status as
.claude-plugin/plugin.json: generated from .apm/, never hand-edited. tests/
subdirectories are excluded from the mirror (dev fixtures, not host-visible
runtime content; several hardcode a relative repo-root walk-up sized for the
.apm/-nested depth, which breaks when duplicated one level shallower).
Applied for real across all 6 plugins and verified two ways: `claude plugin
validate --strict` passes on every real plugin directory, and a live
`claude --plugin-dir <path> -p "list skills/agents"` behavioral test
confirms content is now actually discovered.

Also, from the same issue #90 review round:
- scripts/check-manifests.sh pointed at each plugin's root-level plugin.json
  (checking skills/hooks/mcpServers/agents pointer fields) -- that file was a
  stale near-duplicate of .claude-plugin/plugin.json nothing else read or
  wrote, now deleted across all 6 plugins. check-manifests.sh is rewritten to
  validate .claude-plugin/plugin.json instead, and drops the pointer-field
  checks entirely (nothing to check -- those fields are correctly absent by
  design). Content-presence drift is now check-plugin-content-sync's job, a
  new pre-push hook wired in .pre-commit-config.yaml.

docs/adr/0017 records the root cause and decision in full, including two
rejected alternatives (patching plugin.json's path fields directly -- apm's
compiler strips them on every run; pointing marketplace.json at apm pack's
build/ output -- a version-suffixed non-source directory nothing can install
from without an extra build step). ADR-0015 and CONTEXT.md are updated to
point at it.

Refs: #90

2026-08-13 16:59:03 +00:00

3.6 KiB

Raw Blame History

name, description, allowed-tools, metadata

name

description

allowed-tools

metadata

provider-adapter-author

Use when the user wants to convert a provider-specific AI instruction file (CLAUDE.md, .cursor/rules/*.mdc, copilot-instructions.md, etc.) into a thin adapter that defers to a repo's AGENTS.md — e.g. "reduce duplication between CLAUDE.md and AGENTS.md", "make CLAUDE.md just import AGENTS.md" — even if the pattern isn't named explicitly. Also invoke when agentsmd-author detects an existing provider file overlapping with AGENTS.md it just wrote. Detects redundant content in a provider file relative to AGENTS.md and rewrites it down to a minimal reference (an `@AGENTS.md`-style import where supported, or a text pointer otherwise) plus genuinely provider-specific additions. Self-validates via a bundled deterministic script before finishing. Do not use to write or audit AGENTS.md itself — use agentsmd-author or agentsmd-audit.

Bash Read Edit Write

Gotchas

Not every provider supports cross-file imports. Claude Code does — a CLAUDE.md can consist of nothing but one or more @path lines (e.g. @AGENTS.md), with no other content required. Cursor's .cursor/rules/*.mdc and GitHub Copilot's copilot-instructions.md have no native import mechanism as of current tooling — for those, "thin" means a short text pointer to AGENTS.md plus only what that tool actually needs, not a literal import line. Pass --no-import-syntax to scripts/validate-adapter.sh for these providers.
This skill never creates or edits AGENTS.md itself. If the target repo has no AGENTS.md yet, stop and point the user to agentsmd-author first — there's nothing to adapt to.
Only strip content from the provider file that's genuinely redundant with AGENTS.md. Provider-specific material (IDE settings, tool-only syntax, model-specific instructions) stays — the goal is thin, not empty.
Works standalone or composed-into by agentsmd-author — behave identically either way; don't assume a caller skill exists.

Step 1 — Detect

Look for known provider instruction files in the target repo: CLAUDE.md (repo root, and any deployed copies), .cursor/rules/*.mdc, .github/copilot-instructions.md, and similar tool-specific files. Confirm AGENTS.md exists at the repo root — if not, stop and tell the user to run agentsmd-author first.

Step 2 — Diff and rewrite

Read the provider file and AGENTS.md side by side. Separate the provider file's content into two buckets: lines that restate what AGENTS.md already owns (universal rules, conventions, project overview) versus lines that are genuinely provider-specific (tool syntax, IDE behavior, model-specific instructions). Rewrite the provider file:

Providers with import syntax (Claude Code): replace the redundant bucket with an @AGENTS.md (or correct relative path) import line, keep the provider-specific bucket below it.
Providers without import syntax (Cursor, Copilot, etc.): replace the redundant bucket with a short pointer sentence mentioning AGENTS.md, keep the provider-specific bucket.

Step 3 — Self-validate

Run the bundled check before finishing — this is the skill's own closeout gate; there is no separate paired audit skill for this concern:

bash scripts/validate-adapter.sh [--no-import-syntax] [--max-lines N] <adapter-file> <agents-md-file>

Fix any FAIL and re-run until it exits 0.

Step 4 — Report

State which file was converted, what was removed versus kept, and the validator's final result.

3.6 KiB Raw Blame History