SKILLEMALL.ai
GitHub ↗ RU Sign in

BC jira-skill-free

(no description)

ClawHub Hermes author: 天轰穿 v1.0.1 MIT-0 2 files body ≈ 1 610 tokens Open the sourceclawhub.ai↗ analyzed 20 h ago

Jira集成助手免费版提供Jira事务的只读浏览能力。支持模糊搜索、事务详情查看、浏览器链接生成与可用流转列表查看.

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

IntegrationJiraPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
51
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 0

✓ No critical or high findings

Files scanned: 2. 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: All mapping items must start at the same column at line 9, column 1: description: "|-. 适用于需要jira skill相关能力的开发场景,包含结构化的工作流程和可复用的模板,帮助用户快速完成任务并保持代码质量.… Jira集成助手免费版提供Jira事务的只读浏览能力. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 254 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "summary_zh"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 8 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 32 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1610 tokens
  • 100Progress reporting. Reports progress
  • low 14 top-level sections: this looks like several domains in one skill

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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 32 items
  • +4Has examples (13 code blocks)
  • +1License stated

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

External checks

ClawHub: clean
This skill is a read-only Jira Cloud helper, but users should understand it relies on their Jira API token and may read ticket data from Jira.
LLM: benign (high) · VirusTotal: · 27 Jul 2026