SKILLEMALL.ai
GitHub ↗ RU Sign in

CC od-contribute

One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.

nexu-io/open-design Agent Skills author: nexu-io Apache-2.0 22 files · 11 scripts body ≈ 3 368 tokens Open the sourcegithub.com↗ analyzed 6 d ago

One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders.

As a process C 63/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorGitHubWriting and documentsDesignData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
91/100
safety, quality, tests
Safety 60%
94
Quality 40%
86
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 2

    ✓ No critical or high findings

    Medium and low: 2
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read Write Edit AskUserQuestion TaskCreate TaskUpdate WebFetch
    • low Dangerous commands cmd-pipe-to-shell-known-host install.sh:10
      Pipe-to-shell installer from a well-known host (still executes remote code) (code comment)
      #      curl -sSL https://raw.githubusercontent.com/nexu-io/open-design/main/.claude/skills/od-contribute/install.sh | bash
      comment

    Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 63/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 20When it triggers. No condition that starts the skill
    • 85Steps. 41 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3368 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (6 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +3Description length 409: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 41 items
    • +4Has examples (18 code blocks)
    • +4Reference files are cited in the instructions (1 of 4)
    • +3All 10 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.

    In the sandbox The scripts try to reach the network

    The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

    Grade capped: no higher than C. A skill whose scripts reach outside or for secrets cannot wear an A or a B, however well the text is written.

    Запущено 11 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

    Из них 9 не дошли до работы, и об их поведении мы ничего не узнали.

    install.shзапускает curl; завершился с кодом 1
    scripts/check-prereqs.shне запустился: [od-contrib][error] missing required tools: gh jq
    scripts/config.shничего за пределами своей папки
    scripts/create-issue.shне запустился: [od-contrib][error] --title required
    scripts/create-pr.shне запустился: [od-contrib][error] --workdir required
    scripts/discover-doc-gaps.shне запустился: scripts/discover-doc-gaps.sh: line 14: 1: workdir required
    scripts/discover-i18n-gaps.shне запустился: scripts/discover-i18n-gaps.sh: line 14: 1: workdir required
    scripts/setup-workspace.shне запустился: scripts/setup-workspace.sh: line 16: 1: type required (skill|design-system|i18n|docs)
    scripts/validate-design-system.shне запустился: scripts/validate-design-system.sh: line 15: 1: DESIGN.md path required
    scripts/validate-markdown.shне запустился: [od-contrib][error] usage: validate-markdown.sh <file> [<file> ...] [--reference <orig>]
    scripts/validate-skill-submission.shне запустился: scripts/validate-skill-submission.sh: line 15: 1: skill folder path required

    15 Oct 2026