Individual skill
community-import-smoke-test
A portable community plugin for validating OpenDesign plugin import flows.
plugins/community/import-smoke-test/SKILL.md
Source commit e7a18df64d0e5e1161903e93bb5a302229dbeb96
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106,804
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: claude-code
- ai-design Repository topic
- byok Repository topic
- design-systems Repository topic
- claude-design Repository topic
- hermes-agent Repository topic
- agent-skills Repository topic
- desktop-app Repository topic
- figma-alternative Repository topic
- prototyping Repository topic
- ui-generator Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.claude-plugin/plugin.jsonasset · 161 bytesREADME.mddoc · 855 bytesSKILL.mdcore · 844 bytesSKILL.mdcore · 844 bytesassets/import-checklist.mddoc · 317 bytesopen-design.jsonasset · 2,862 bytespreview/index.htmlasset · 2,862 bytes
Read excerpt
# Community Import Smoke Test
Use this plugin when validating that OpenDesign 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.