Install verification: runtime verified (L5) · tested on dsh 0.2.1-rc.2 · last checked Install verification details →
What it doesAI
Creates spec-compliant DSH skills from the Web UI (Huawei Cloud, generic, REST API) with a 10-point evaluation loop.
- Creates spec-compliant skills directly from the Web UI
- Supports Huawei Cloud, generic and REST API skill types
- Built-in 10-point evaluation loop to validate skills
Capability tags are AI-inferred or rule-extracted from the README (see badge) — vocabulary-limited, not install-verified. AI = inferred; README = literal keyword from the readme.
Installation
dsh plugin --profile web add @cloudplugin/dsh-skill-creatorInstall method: npm · runtime verified (L5)
Verification & Compatibility
Grouped by plugin version: each card lists the dsh versions actually tested against that artifact version and their install verdicts (L5 wins). Untested combinations are omitted — absence means untested, never assumed compatible. L1–L3 are a plugin-level static archive (independent of the dsh version — the same verdict on every dsh row): they sit in each row's level grid next to L4/L5, marked "static", while their evidence is stored once per plugin inside that row's "checks & evidence" instead of being duplicated per version.
External credentials (plugin-level): none detected
○ The author declares no dsh version requirement — install is not blocked by version.
| plugin \ dsh | dsh 0.2.1-rc.2 current | dsh 0.2.1-alpha.4 |
|---|---|---|
| 0.0.4 | ✓ | · |
0.0.4npm✓ 1 runtime-verified2026-10-19
@cloudplugin/dsh-skill-creator
✓dsh 0.2.1-rc.2current2026-10-19L5 · runtime verified
- • Node.js: v24.14.0
- • DSH: 0.2.1-rc.2
- • Plugin artifact: npm · @cloudplugin/dsh-skill-creator@0.0.4
ID: dsh-skill-creator-5@0.0.4@dsh0.2.1-rc.2 · profile: l4-sandbox
Issued: 2026-10-19 · expires: 2026-10-26
View checks & evidence
active in loader tree (150 entries)
L1–L3 are plugin-level static conclusions (baseline, identical across dsh versions): evidence is stored once per plugin.
Only the latest 3 published versions are shown; source-snapshot (commit hash) groups, unstated groups and older versions are omitted — the full archive stays in the data layer (snapshot/unstated groups appear only when a plugin has no published version).
Author badges
Embed the official badges in your README to showcase security & install-test status:
`[](https://www.dsh.so/artifact/dsh-skill-creator-5/)``[](https://www.dsh.so/artifact/dsh-skill-creator-5/)`Security Report
Two automated layers, neither a manual review: a static scan (per-plugin rule checks) and a model-driven dynamic security audit that covers only the subset static-flagged at warn or above and never executes plugin code.
Static low, dynamic high — stricter wins → overall high.
v0.0.4dsh manifest0.0.4npm2026-10-210.0.4same versionclean · gitVet is an AST static scan (npm artifact or git source).
show static findings (8)
- warningchildProcess · code-exec
src/core/creators.mjs:101const clone = spawnSync('git', ['clone', '--depth', '1', '--branch', spec.branch, '--filter=blob:none', '--sparse', spec.repo, staging], - warningchildProcess · code-exec
src/core/creators.mjs:104const co = spawnSync('git', ['-C', staging, 'sparse-checkout', 'set', spec.path], { encoding: 'utf8', timeout: 120000 }); - warningchildProcess · code-exec
src/core/creators.mjs:106const head = spawnSync('git', ['-C', staging, 'rev-parse', 'HEAD'], { encoding: 'utf8', timeout: 30000 }); - warningfsWrite · files
src/core/creators.mjs:149fs.writeFileSync(dest, file.data); - warningfsWrite · files
src/core/creators.mjs:179fs.writeFileSync(stampPath(kind), `${JSON.stringify(stamp, null, 2)}\n`); - warningfsWrite · files
src/core/plugin.mjs:36fs.writeFileSync(marker, `${JSON.stringify({ ...detail, at: new Date().toISOString(), pid: process.pid, cwd: process.cwd() }, null, 2)}\n`); - warningchildProcess · code-exec
src/core/runner.mjs:180result = spawnSync(bash, [script, '-s', skillDir], { - warningfsWrite · files
src/core/runner.mjs:400fs.writeFileSync(tmp, `${JSON.stringify({ version: 1, runs: merged }, null, 1)}\n`);
show 3 audit findings
- highShipped config forces danger-full-access on unattended LLM agents
cordis.patch.yml:49Every install applies this bundle patch, so runs created by POST /run get agents with sandbox=danger-full-access and no approval (runner.mjs spawnAgent sets the preset on the agent session). Those agents execute shell/CLI chosen by an LLM that is steered by a remotely fetched creator SKILL.md and by the request's free-text description; the 'readonly only' evaluation policy is prompt text, not enforcement. Normal use of the panel ('开始创建') therefore yields unsandboxed command execution with the DSH process's privileges and filesystem/network reach, and the plugin writes into <cwd>/skills (defaul
- mediumCreator code is fetched from an unpinned branch head and executed with bash
src/core/runner.mjsThe validator script path is <cache>/<kind>/.../scripts/validate-skill.sh, produced by `git clone --depth 1 --branch spec.branch` (creators.mjs, branches 'master'/'main') with no commit pinning, signature or hash verification; the same unpinned creator tree is also handed to the creation agent with instructions to run its scripts. Any push to those upstream branches, or a compromised mirror/DNS path, becomes shell execution inside the DSH process (and, per the previous finding, full-access LLM execution) on the next evaluation. The no-git fallback apiWalk writes files at path.join(to, file.rel
- lowRun history and mount marker written world-readable to a predictable temp path
src/core/creators.mjsruns.json (steps, spec/description text, target paths, cwd) and mounted.json (cwd, pid) are written under os.tmpdir()/dsh-skill-creator-cache with default mkdir/write modes (typically 0755/0644). On a multi-user host other local users can read pasted requirements and generated skill locations, and can plant a runs.json that the runner rehydrates and displays (React escapes the text, so impact is limited to disclosure/spoofed history).
Ships a default danger-full-access preset for unattended LLM agents and executes creator scripts fetched from unpinned branch heads; routes/validators were not harvestable.
Rule: the dynamic audit can only raise risk, never lower it (raise-only, never an exemption); a wrong raise is withdrawn by human review and the tier falls back to the static verdict. Overall verdict = the stricter of the two layers.
Disclaimer: the static scan and the dynamic security audit are both automated analysis, not a security guarantee. Always review what you install.
Activity
Last commit 2026-10-16 · activity: Active
• Repo created: 2026-10-15
• Stars: ★ 0 · Forks: 0
• Health: Active — committed within last 30 days
Source
Author README
View on GitHub ↗The author's original README from the repository — fetched live, unedited (the English page loads the default README).
