SKILLEMALL.ai
GitHub ↗ RU Sign in

BF mcore-create-issue

Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.

ClawHub Agent Skills author: NVIDIA 1 file body ≈ 1 474 tokens Open the sourceclawhub.ai↗ analyzed 26 h ago

Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.

As a process F 51/100 · Will not run — References files that are not bundled: <job-url>, <pr_url>, <run_url>

GeneratorGitHubData and analyticstype 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
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
F
51/100
Will not run
References files that are not bundled: <job-url>, <pr_url>, <run_url>
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
20
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. The text references files that are not there: add them or drop the references.
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: 1. 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")
  • warning missing-ref reference to a missing file: <job-url>
  • warning missing-ref reference to a missing file: <pr_url>
  • warning missing-ref reference to a missing file: <run_url>
  • warning missing-ref reference to a missing file: <job_url>
  • note frontmatter-key unknown frontmatter key "user_invocable"
  • note frontmatter-key unknown frontmatter key "argument"

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: <job-url>, <pr_url>, <run_url>
  • 0Tools and files. 4 referenced file(s) missing: <job-url>, <pr_url>, <run_url>
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 100Steps. 16 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1474 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (11 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)
  • +3Description length 90: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (11 code blocks)
  • +1License stated

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