BF gitlab-agent-profile
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
ReferenceGitLabAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: gitlab-agent-profile (ClawHub)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: assets/gitlab-agent-profile.svg - warning
missing-refreference to a missing file: assets/gitlab-agent-profile.webp - warning
missing-refreference to a missing file: assets/gitlab-agent-profile-records.json
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. 9 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. 28 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1034 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 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 6 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.
External checks
ClawHub: suspicious
The skill mostly matches its GitLab profile-maintenance purpose, but it creates review-worthy risk through recurring agent scheduling, GitLab-token use, unpinned runtime package execution, and loosely scoped file writes.
LLM: suspicious (high)