SKILLEMALL.ai
GitHub ↗ RU Sign in

BD jira-issue-analyzer

Jira 问题分析编排器。负责获取 issue 与附件、委托日志分析 subagent，并产出最终 Markdown 报告到本地目录。适用于用户要求生成 Jira 问题分析文档的场景。

ClawHub Agent Skills author: Dimos v1.0.0 MIT-0 11 files body ≈ 358 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerJiraOperations and projectstype 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
B
81/100
safety, quality, tests
Safety 60%
92
Quality 40%
65
Run on models
none yet
Process rating
D
48/100
Unfinished process
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 jira/config.py:14
    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 Exfiltration read-dotenv jira/main.py:214
    Reads a .env file (quoted — discussed, not commanded)
    print("Copy .env.example to .env and fill in your token.")
    quoted
  • low Exfiltration read-dotenv jira/README.md:15
    Reads a .env file
    cp .env.example .env
  • low Exfiltration read-dotenv SKILL.md:17
    Reads a .env file (quoted — discussed, not commanded)
    - `cp .env.example .env`
    quoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/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
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 358 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +3Description length 92: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (3 code blocks)

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

External checks

ClawHub: suspicious
This Jira analysis skill is broadly understandable and purpose-aligned, but its attachment handling can write files outside the intended folder if a Jira attachment has an unsafe name.
LLM: suspicious (high) · VirusTotal: · 29 May 2026