new-plugin-layer

Generate a private Layer 3 Claude Code plugin container image and publish it to GHCR.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/sun2admin/builder-project --skill new-plugin-layer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-plugin-layer
Source: https://github.com/sun2admin/builder-project/tree/main/layer3-ai-plugins/.claude/skills/new-plugin-layer
Command: npx skills add https://github.com/sun2admin/builder-project --skill new-plugin-layer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates building a private Layer 3 Claude Code plugin container image.

Core Features & Use Cases

  • Scaffold and publish a Layer 3 plugin container image on GHCR from a selected set of plugins
  • Automatically generate repository scaffolding (GitHub repo, Dockerfile, manifest.json) and a GitHub Actions workflow
  • Enable reuse by updating central references (references/standards.json and references/plugin-lists.json) for future builds

Quick Start

Use the new-plugin-layer skill to generate and publish a private GHCR image for your selected plugins.

Frequently Asked Questions about new-plugin-layer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate building a private Claude plugin container image from multiple sources?

You can automate building a private Claude plugin container image by selecting plugins from multiple sources, detecting duplicates, generating a Dockerfile, and publishing the image to GHCR via GitHub Actions.

What is included in the repository scaffolding for a Claude plugin layer?

Repository scaffolding for a Claude plugin layer includes the GitHub repo structure, a Dockerfile, manifest.json, and a GitHub Actions workflow configured for private GHCR publishing.

Do I need curl and jq to generate a Dockerfile and GitHub Actions workflow for my plugins?

Yes, curl and jq are required dependencies because the skill relies on them to process plugin lists, detect duplicates, and generate the Dockerfile and GitHub Actions workflow.

How does the GHCR publishing workflow handle duplicate plugins from different sources?

The workflow handles duplicate plugins by detecting them during the selection phase before generating the Dockerfile, ensuring the final container image contains a clean, de-duplicated plugin set.

Can I update central references for future plugin builds using this automation?

Yes, you can update central references for future builds because the skill automatically updates references/standards.json and references/plugin-lists.json with the new plugin set during the scaffolding process.

Is Dev Container supported when publishing a Claude plugin layer to GHCR?

Dev Container configurations are supported by generating the necessary container image definitions, allowing the published GHCR image to function as a dev container for Claude Code plugins.