CtrlK
BlogDocsLog inGet started
Tessl Logo

pajamas

GitLab Pajamas Design System expert for building UIs with Pajamas components and patterns. Use when: (1) implementing UI that should follow GitLab's Pajamas design system, (2) selecting or configuring Pajamas/GlComponent components (GlButton, GlAlert, GlModal, etc.), (3) translating Figma designs into Pajamas-compliant code, (4) questions about Pajamas component usage, variants, categories, or accessibility, (5) building GitLab-style interfaces, or (6) the user mentions "Pajamas", "GitLab UI", "Gl components", or "design system" in a GitLab context. Works hand-in-hand with the implement-design skill and Figma MCP tools.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a well-structured, actionable overview that leans on tables and concrete commands rather than padding, and points one level deep to script-generated references. Its main weakness is mild repetition across the token-rule sections, which keeps conciseness just below excellent.

Suggestions

Consolidate the 'CRITICAL RULE: Always Use Design Tokens', 'When encountering absolute values', and 'Token usage priority' sections to remove overlapping guidance and tighten conciseness.

Add a small runnable Vue 2.7 render example (e.g., a GlButton with category/variant props) to make the import snippet fully copy-paste ready and lift actionability.

Add an explicit 'if peer-dependency verification fails, adjust the scaffold and re-verify' feedback loop to the scaffold workflow to match the validation rigor of a score-5 workflow.

DimensionReasoningScore

Conciseness

Largely efficient — tables, imperative directives, and no padding about what a design system is — but the absolute-value rules, the 'When encountering absolute values' steps, and the 'Token usage priority' list overlap slightly and could be tightened. Fits the score-4 anchor (efficient, minor over-explanation to trim); not 5 due to that repetition.

4 / 5

Actionability

Provides concrete executable commands ('npm info @gitlab/ui peerDependencies --json', 'bash scripts/update-refs.sh'), specific token names, a runnable import snippet, and a 5-step Figma lookup chain. Mostly copy-paste ready with minor gaps (no full Vue render example), matching score-4.

4 / 5

Workflow Clarity

Clear sequenced workflows for initialization, scaffolding (check peerDeps → pick scaffold → verify), component lookup, and Figma matching, with an explicit 'Verify after install' checkpoint and a token-resolution feedback loop. Not score-5 because the scaffold flow lacks an explicit fix-and-revalidate loop, but well above score-3.

4 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview pointing one level deep to references via a token-reference table and SSoT reference columns; the referenced paths (component-index.md, design-tokens/token-map.md, tokens.css) are confirmed to be produced by the bundled scripts, and content is appropriately split. Matches the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Description

100%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 is exemplary: it states concrete capabilities, lists natural trigger terms and synonyms, and provides six explicit 'Use when' clauses with GitLab-context scoping. It clearly distinguishes itself from generic UI/design-system skills and notes a complementary skill relationship.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('building UIs with Pajamas components and patterns', 'selecting or configuring Pajamas/GlComponent components (GlButton, GlAlert, GlModal)', 'translating Figma designs into Pajamas-compliant code') with comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers both what ('GitLab Pajamas Design System expert for building UIs with Pajamas components and patterns') and when via six numbered 'Use when' trigger clauses with concrete phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Includes comprehensive natural trigger terms and synonyms — 'Pajamas', 'GitLab UI', 'Gl components', 'design system' — plus concrete component names a user would actually mention, matching the score-5 anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche scoped to 'GitLab's Pajamas design system' 'in a GitLab context', with component-specific triggers that minimize overlap with other design-system skills, matching the score-5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 11 missing, 7 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 34 missing, 19 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
gitlabhq/orbit-knowledge-graph
Reviewed

Table of Contents

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.