Files

Defame1297 3a91126d3f fix(kyberforge): correct field classification and fill provenance gaps in plugin-author and marketplace-author

## Why

The manifest-fields tables in both skills used imprecise labels ("CC-only",
"Copilot-only") that conflated two distinct reasons a field appears in only
one manifest: platform constraint (the other tool does not support the field
at all) versus repo convention (both tools support it, but the scaffold places
it in one manifest by design). This caused agents to treat convention
boundaries as hard platform constraints, producing unnecessary errors when
updating manifests for dual-tool repos.

Provenance was also incomplete: sources.md files were missing entries for
sources that had been consulted and were already contributing to SKILL.md
and manifest-fields.md content, making the evidence chain unverifiable.

## Implementation Notes

Field classification now uses three explicit categories — shared, platform
(one tool does not support the field), and convention (both tools support it;
scaffold places it in one manifest by design). The distinction matters because
convention fields may legitimately appear in the other manifest when there is
a deliberate reason; platform fields may not.

New gotchas added to plugin-author: agent files silently ignore hooks,
mcpServers, and permissionMode frontmatter; claude plugin tag --push requires
a clean working tree; --dry-run preview before tagging; --strict flag on
validate. New gotchas in marketplace-author: metadata object as Copilot CLI
canonical location for top-level fields; strict: false for dual-tool plugins;
sha takes precedence over ref for pinning; --strict flag on validate.

tests/ removed from plugin-author because new-plugin.sh has no branching
logic warranting a bats suite at this stage.

## Impact

Skill prompt changes only — no runtime code affected. Agents using these
skills will now correctly distinguish convention from constraint when deciding
which manifest to update for a given field.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-06-28 11:09:13 +00:00

1.4 KiB

Raw Blame History

plugin-author

Creates, updates, and releases plugin scaffolds for the holocron marketplace.

What it does

Manages both manifests (plugin.json for Copilot CLI and .claude-plugin/plugin.json for Claude Code) in one pass. Three operations: create a new plugin scaffold with placeholder manifests and skeleton dirs; update configuration fields (shared fields updated in both manifests simultaneously); release a version with HITL gate before tagging.

Out of scope: plugin content (skills, agents, hooks, MCP servers inside those dirs) and marketplace.json entries.

Before you start

Have ready: the plugin name (kebab-case) and the repo root path.

Usage

/plugin-author

Manual scaffold (human workflow):

bash scripts/new-plugin.sh <plugin-name> <repo-root>

# Examples:
bash scripts/new-plugin.sh my-tools /root/ai-development
bash scripts/new-plugin.sh data-tools .

Files

File	Purpose
`SKILL.md`	Skill instructions for agents
`scripts/new-plugin.sh`	Scaffolds both manifests and skeleton dirs for a new plugin
`references/manifest-fields.md`	All optional fields for both manifests beyond the scaffolded defaults
`references/sources.md`	Research provenance — sources that informed this skill
`scripts/README.md`	Directory meta-documentation for scripts/
`references/README.md`	Directory meta-documentation for references/

1.4 KiB Raw Blame History