community-import-smoke-test
A portable community plugin for validating Open Design plugin import flows.
Profile →npx skills add nexu-io/open-design --skill import-smoke-test --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. Identify the import path the user is testing: folder, zip, GitHub, or marketplace. 2. Produce a compact import receipt that includes the plugin name, source kind, files detected, and any user note. 3. 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.
What does the community-import-smoke-test skill do?
A portable community plugin for validating Open Design plugin import flows.
How do I install it?
Run `npx skills add nexu-io/open-design --skill import-smoke-test --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.