SKILLEMALL.ai

BF gitlab-agent-profile

Maintain the GitLab agent profile page and static contribution performance chart.

ClawHub Agent Skills author: xrow GmbH v1.91.2 MIT-0 5 files body ≈ 1 395 tokens Open the sourceclawhub.ai analyzed 2 d ago

Maintain the GitLab agent profile page and static contribution performance chart.

As a process F 46/100 · Will not run — References files that are not bundled: assets/gitlab-agent-profile.svg, assets/gitlab-agent-profile.webp, assets/gitlab-agent-profile-records.json

ProcedureGitLabAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: assets/gitlab-agent-profile.svg, assets/gitlab-agent-profile.webp, assets/gitlab-agent-profile-records.json
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ClawHub

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: 5. 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: assets/gitlab-agent-profile.svg
  • warning missing-ref reference to a missing file: assets/gitlab-agent-profile.webp
  • warning missing-ref reference to a missing file: assets/gitlab-agent-profile-records.json
  • note edit-residue the text marks something as outdated (lines 59): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: assets/gitlab-agent-profile.svg, assets/gitlab-agent-profile.webp, assets/gitlab-agent-profile-records.json
  • 0Tools and files. 3 referenced file(s) missing: assets/gitlab-agent-profile.svg, assets/gitlab-agent-profile.webp, assets/gitlab-agent-profile-records.json
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 12 mutating operations with no state check
  • 40Consistency. Frontmatter name (gitlab-agent-profile) differs from the folder (xrowgmbh-gitlab-agent-profile)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 29 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Execution cost. Instruction body is 1395 tokens
  • low The response is described with custom markup (3 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 81: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 29 items
  • +4Has examples (1 code blocks)

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

External checks

ClawHub: suspicious
This skill is mostly aligned with its stated GitLab profile purpose, but it should be reviewed because it can run repeatedly on a schedule, collect GitLab activity, and push generated assets.
LLM: suspicious (high) · 11 Sept 2026