mcpbeat

Community Import Smoke Test

nexu-io/community-import-smoke-test

A portable community plugin for validating Open Design plugin import flows.

2k tokens
context cost
the whole folder, loaded on every use
6
files
instructions only
0
copies elsewhere
how many repositories repackaged it
83386
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nexu-io/open-design --skill community-import-smoke-test

What comes with it

7 063 bytes besides the instruction
.claude-plugin/plugin.json
README.md
assets/import-checklist.md
open-design.json
preview/index.html

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

1 sections, as written by the author

Community Import Smoke Test

Use this plugin when validating that Open Design can import community plugins

from a local folder, a zip archive, a GitHub subpath, or a marketplace entry.

When this plugin is applied:

  • Identify the import path the user is testing: folder, zip, GitHub, or marketplace.
  • Produce a compact import receipt that includes the plugin name, source kind,

files detected, and any user note.

  • Keep the output intentionally small so install, apply, and provenance states

are easy to inspect in the UI.

Do not require network access, shell commands, external connectors, or secrets.

This plugin exists to exercise install and apply plumbing, not to perform a

production workflow.

How to use it

Copy the folder

Take nexu-io/community-import-smoke-test from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.