SKILLEMALL.ai
GitHub ↗ RU Sign in

AC jenkins-skills

Manage Jenkins CI from the command line — list jobs, inspect a job, trigger builds (with or without parameters), check build status, stream console logs, and enable/disable jobs. Use this whenever the user wants to run a Jenkins job, check whether a build passed, read build logs, or pause/resume a job.

ClawHub Agent Skills author: weiguang1017 v0.1.0 MIT-0 8 files body ≈ 583 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

Manage Jenkins CI from the command line — list jobs, inspect a job, trigger builds (with or without parameters), check build status, stream console logs, and…

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

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
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
52/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

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

    ✓ No critical or high findings

    Files scanned: 8. 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 52/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. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (jenkins-skills) differs from the folder (jenkins-ci-skill)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 9 steps
    • 100Execution cost. Instruction body is 583 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
    • +2Single-language instructions
    • +3Description length 303: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 9 items
    • +4Has examples (2 code blocks)
    • +3All 1 scripts are documented
    • +1License stated

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

    External checks

    ClawHub: suspicious
    This Jenkins skill is purpose-built and not deceptive, but it can implicitly run or disable CI jobs using Jenkins credentials without a clear confirmation gate.
    LLM: suspicious (high) · 5 Aug 2026