SKILLEMALL.ai
GitHub ↗ RU Sign in

CC skill-d-create-issues

【issue 落地总控】当组织者确认 issue 草稿后触发。触发方式：(A) 组织者在 Gitea 把 draft_issue.md 改名为 confirmed_issue.md，由 webhook 通知 OpenClaw；(B) 组织者在 OpenClaw 中说"确认 YYYY-MM-DD-HHMM 的 issue"。触发关键词：确认issue、创建issue、落地issue、confirmed_issue、批量建issue。不处理会议创建、会前简报、会后纪要等场景。

ClawHub Agent Skills author: myd2002 v1.0.0 MIT-0 14 files · 1 script body ≈ 1 385 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

GeneratorInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
C
74/100
safety, quality, tests
Safety 60%
84
Quality 40%
59
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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.

Exfiltration 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Exfiltration net-redirectable-api-key scripts/check.py:33
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key scripts/create_issues.py:47
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key scripts/finish.py:52
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • low Dangerous commands cmd-background-process SKILL.md:64
    Starts a background / autostarted process
    nohup python3 scripts/webhook.py > ~/.config/skill-d-create-issues/webhook.log 2>&1 &

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 2, column 149: …bhook 通知 OpenClaw；(B) 组织者在 OpenClaw 中说"确认 YYYY-MM-DD-HHMM 的 issue"。触发关键词：确认iss… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 20 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 64 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1385 tokens

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
  • -36 of 7 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 238: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 64 items
  • +4Has examples (7 code blocks)

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

External checks

ClawHub: suspicious
This skill matches its meeting-to-issue purpose, but needs Review because it can modify Gitea, expose meeting/contact data, and run a public webhook with weak defaults.
LLM: suspicious (high) · VirusTotal: · 29 May 2026