Name: gitlab
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

gitlab

Gitlab integration. Manage Projects, Groups, Users, Labels. Use when the user wants to interact with Gitlab data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gitlab/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete CLI commands and a clear connection-state workflow including a polling feedback loop. Its main weaknesses are an unnecessary introductory explanation of GitLab, a broken "Step 2" cross-reference, and a large inline actions table that could live in a separate reference file.

Suggestions

Delete the opening "GitLab is a web-based DevOps platform..." paragraph and the "Use action names and parameters as needed" filler to remove concepts Claude already knows.

Fix the "skip to Step 2" reference by labeling the workflow steps (e.g. Step 1: Connect, Step 2: Discover and run actions) so the cross-reference resolves.

Add a worked example that runs a real action (e.g. create-issue with a concrete --input payload) and consider moving the Popular actions table to a referenced ACTIONS.md to tighten the main file.

Dimension	Reasoning	Score
Conciseness	The opening paragraph "GitLab is a web-based DevOps platform that provides version control, CI/CD, and issue tracking..." explains what GitLab is, which Claude already knows, and "Use action names and parameters as needed" is filler; the rest is mostly efficient, matching the anchor that is mostly efficient but includes some unnecessary explanation.	3 / 5
Actionability	Concrete, copy-paste-ready commands are given for install, login, connection, polling, action search, and proxy, with a populated actions table and flags table; the minor gap is that running actions uses templated placeholders (<actionId>, generic --input) with no fully worked end-to-end example using real values.	4 / 5
Workflow Clarity	There is a clear install→login→connect→poll→search→run sequence with an explicit feedback loop for the connection state machine (CLIENT_ACTION_REQUIRED → user acts → re-poll), but the "skip to Step 2" reference points to an unlabeled step and there is no post-run validation, matching the clear-sequence-with-minor-validation-gaps anchor.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no nested references, but the sizable Popular actions table is inline API-catalog content and no external reference file is provided for deeper API detail, matching the good-structure-with-minor-organization-gaps anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit "Use when" trigger and names the GitLab domain with several entities, but uses a single generic verb and omits the most common user-facing terms (issues, merge requests). It is mostly distinct but has minor overlap risk with similar source-control skills.

Suggestions

Replace the generic "Manage" with distinct concrete verbs (e.g. "Create and update issues, merge requests, projects, and labels") to raise specificity.

Expand the trigger phrase to include the natural terms users actually say, e.g. "Use when the user mentions GitLab issues, merge requests, pipelines, or project management."

Add file/URL-based triggers (e.g. gitlab.com links) to sharpen distinctiveness from generic source-control skills.

Dimension	Reasoning	Score
Specificity	"Manage Projects, Groups, Users, Labels" names the GitLab domain and four concrete entities, but relies on a single generic verb ("Manage") rather than several distinct concrete actions, matching the anchor that lists the domain plus a few actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" ("Manage Projects, Groups, Users, Labels") and an explicit "when" ("Use when the user wants to interact with Gitlab data"), but the trigger phrase is generic rather than enumerating concrete triggers, matching the anchor where both are present but the when could be more specific.	4 / 5
Trigger Term Quality	"Projects, Groups, Users, Labels" and "interact with Gitlab data" provide relevant keywords, but the description omits the most common natural terms users actually say for GitLab (issues, merge requests, pipelines), fitting the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Gitlab integration" names a specific platform giving it a clear niche, but "interact with Gitlab data" is broad and could overlap with a closely related source-control skill (e.g. a GitHub skill), matching the mostly-distinct anchor with minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gitlab/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.