SKILLEMALL.ai
GitHub ↗ RU Sign in

CC snowsand-jira

Interact with Jira Cloud via REST API. Use for searching issues (JQL), viewing issue details, creating/updating issues, adding comments, transitioning status, querying sprints/boards, and logging work. Triggers on Jira issue operations, sprint queries, JQL searches, worklog tracking, or any Atlassian Jira Cloud task.

ClawHub Agent Skills author: snowsand-enterprises v1.0.0 MIT-0 4 files body ≈ 1 091 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationJiraOperations 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
C
72/100
safety, quality, tests
Safety 60%
60
Quality 40%
91
Run on models
none yet
Process rating
C
64/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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

    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 · 8

    ✓ No critical or high findings

    Medium and low: 8
    • medium Exfiltration net-credential-use references/fields.md:28
      Credential used in a network call (verify the destination is the intended service)
      curl -s -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \
    • medium Exfiltration net-credential-use references/fields.md:37
      Credential used in a network call (verify the destination is the intended service)
      curl -s -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \
    • medium Exfiltration net-credential-use references/fields.md:119
      Credential used in a network call (verify the destination is the intended service)
      curl -X POST -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \
    • medium Exfiltration net-credential-use references/fields.md:135
      Credential used in a network call (verify the destination is the intended service)
      curl -X POST -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \
    • medium Exfiltration net-redirectable-api-key scripts/jira.py:22
      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-credential-use SKILL.md:21
      Credential used in a network call (verify the destination is the intended service)
      curl -s -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" "$JIRA_BASE_URL/rest/api/3/myself" | jq .
    • medium Exfiltration net-credential-use SKILL.md:161
      Credential used in a network call (verify the destination is the intended service)
      curl -s -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \
    • medium Exfiltration net-credential-use SKILL.md:165
      Credential used in a network call (verify the destination is the intended service)
      curl -s -X POST -u "$JIRA_USER_EMAIL:$JIRA_API_TOKEN" \

    Files scanned: 4. 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 64/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 3 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1091 tokens
    • 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)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 318: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 9 items
    • +4Has examples (8 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +3All 1 scripts are documented

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

    External checks

    ClawHub: suspicious
    This appears to be a legitimate Jira Cloud helper, but it can make live changes to Jira data with broad routing and limited safety boundaries.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026