cnb-plugin-market

Searches the CNB plugin marketplace and generates .cnb.yml pipeline configuration snippets.

3|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill cnb-plugin-market-wopal-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cnb-plugin-market
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/cnb-plugin-market
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill cnb-plugin-market-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing CNB CI/CD pipeline steps by hand means reinventing notification, lint, build, and deploy logic that already exists as packaged plugins. This Skill searches the CNB plugin marketplace for a matching plugin, reads its README documentation, and produces a correct .cnb.yml configuration fragment with the right image and settings parameters. ## Core Features & Use Cases - Intent-based plugin search: Fetches the marketplace plugins.json catalog and matches user needs (notifications, code quality, build/release, deployment, security scanning) against plugin tags and descriptions, returning ranked Top 3-5 recommendations. - Document-driven config generation: Reads the plugin README to extract the settings parameter table and usage examples, then generates YAML with correct image names, lowercase settings keys, and $VAR secret references. - Validation and integration: Merges generated snippets into an existing .cnb.yml and validates the result with the cnb-pipeline validator before delivery. - Use Case: A user says "notify my WeCom group when the build fails." The Skill finds the wecom-message plugin, reads its docs, and outputs a failStages step using tencentcom/wecom-message with webhook: $WECOM_WEBHOOK imported from a secret repository. ## Quick Start Ask the assistant to find a CNB plugin for sending DingTalk notifications and generate the corresponding .cnb.yml pipeline step.

Frequently Asked Questions about cnb-plugin-market

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

FAQPage Schema
How do I find a CNB plugin for sending build notifications?

Describe your notification need, such as WeCom, Feishu, DingTalk, or a generic webhook, and the Skill searches the marketplace plugins.json catalog by tags and descriptions. It returns ranked matches, then reads the chosen plugin's README to generate the .cnb.yml step with correct image and settings.

How do I configure CNB plugin settings in .cnb.yml?

Add an `image` field with the plugin's Docker image name and a `settings` map using the lowercase parameter names from the plugin's README. Reference sensitive values with `$VAR` syntax, where VAR is declared in a secret repository file imported at the pipeline level.

Can I use the CNB plugin marketplace in a private deployment?

Yes. Provide the URL of your private marketplace's plugins.json data source, or paste the file contents directly. The data must follow the same schema with id, name, description, tags, readme, images, and source fields, and the search and matching workflow stays identical.

What happens if no CNB plugin matches my requirement?

The Skill reports that no match was found and suggests alternatives: use any suitable Docker Hub image directly as a pipeline step, write your own plugin following the official create-plugin documentation, or contribute a new plugin to the marketplace.

Why must secrets be referenced with $VAR in CNB plugin settings?

Environment variables declared via env or imports are not passed into the plugin execution environment automatically. Only parameters declared in settings are forwarded, so sensitive values must live in a secret repository file and be referenced as $VAR inside settings.