plugin-release

Revert Bryllen plugin marketplace and npm references to GitHub after local testing.

2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/madebynoam/bryllen --skill plugin-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-release
Source: https://github.com/madebynoam/bryllen/tree/main/.claude/skills/plugin-release
Command: npx skills add https://github.com/madebynoam/bryllen --skill plugin-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reverts Bryllen's plugin marketplace and npm source from the test environment back to the production GitHub hosting, ensuring teams can share and publish stable builds after local testing.

Core Features & Use Cases

  • Reconfigures the Claude Code plugin marketplace back to GitHub for both plugin and npm sources.
  • Updates consumer project references to ensure consistent dependency versions and source locations.
  • Use Case: After validating changes in a local branch, run this skill to restore supplier references in a consumer project so teams can continue development with GitHub-hosted assets.

Quick Start

Perform a plugin release by applying the reverse marketplace switch to point to GitHub and verify the consumer project's package.json references point to github:madebynoam/bryllen

Frequently Asked Questions about plugin-release

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

FAQPage Schema
How do I revert a plugin marketplace back to GitHub after local testing?

To revert a plugin marketplace back to GitHub, you execute marketplace switch commands to point plugin sources to GitHub and update package.json references. This restores supplier references so teams can continue development with GitHub-hosted assets.

How do I update npm package references in consumer projects to use GitHub?

Updating npm package references to GitHub requires modifying package.json to point to github:madebynoam/bryllen. The skill applies this across consumer projects and verifies installation integrity to ensure consistent dependency versions.

What is the best way to switch Bryllen plugin sources from a test environment to production?

The best way to switch Bryllen plugin sources to production is running a reverse marketplace switch that reconfigures both plugin and npm sources back to GitHub hosting, verifying installation integrity after updating references.

Does reverting marketplace configuration affect npm package versions in consumer projects?

Reverting marketplace configuration updates consumer project references to ensure consistent dependency versions and source locations. It swaps package references back to GitHub while verifying installation integrity across the affected projects.

When do I need to run a plugin release workflow?

You need to run a plugin release workflow after validating changes in a local branch. It restores supplier references in consumer projects, reverting marketplace configuration and npm package references from the test environment back to GitHub.

Why does my package.json still reference the test marketplace after switching back to GitHub?

If package.json still references the test marketplace, the revert process did not update package references correctly. A proper plugin release executes marketplace switch commands and updates package.json to point to github:madebynoam/bryllen.