geist

Expert guidance for Geist, Vercel's default typography system and font family for precise Next.js interfaces. Use when configuring Geist Sans, Geist Mono, or Geist Pixel, setting up font imports, or applying Vercel typography and aesthetic guidance.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 highly actionable, mostly lean reference with copy-paste code for the common Geist setup paths and strong sectioning. Its main gaps are scattered version/date markers not isolated in a deprecated section, a hand-wavy subset-configuration subsection, and an all-inline structure with no progressive file splitting.

Suggestions

Consolidate version-specific notes (v1.7.0 ligatures, Cyrillic, Pixel's Feb 2026 date) into a dedicated 'Version notes' or 'Changelog' section so time-sensitive details don't dilute the main guidance.

Replace the hand-wavy subset section with an executable next.config.js example showing how to configure additional subsets.

Consider moving the font-weights reference table and detailed Pixel variant descriptions into a separate reference file linked from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and code/table-driven with little over-explanation, but time-sensitive markers ('v1.7.0', 'Feb 6, 2026', 'Coding Ligatures (v1.7.0)') are sprinkled in feature sections rather than a deprecated/old-patterns section, so it lands at anchor 4 instead of 5.	4 / 5
Actionability	Copy-paste-ready, executable guidance throughout: npm install, App Router layout imports, Tailwind config, CSS variables, default type recipes, and SS11 ligature config for VS Code and CSS, covering the common cases comprehensively as in anchor 5.	5 / 5
Workflow Clarity	As a non-destructive configuration reference it has a clear implicit install->import->use sequence and well-organized scenario sections, but it is reference-style rather than an explicit multi-step workflow with checkpoints, fitting anchor 4.	4 / 5
Progressive Disclosure	A single ~200-line document with clear section headers and good organization, but all content is inline with no bundle files or one-level-deep detail references to split into, matching anchor 4 rather than the file-split anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

83%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 strong, third-person, and explicitly pairs a clear 'what' with a concrete 'Use when' trigger clause for a well-scoped niche. It falls just short of top marks on specificity, trigger coverage, and distinctiveness due to the slightly broad 'aesthetic guidance' phrasing and missing natural terms like 'next/font' and the 'geist' package.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('configuring Geist Sans, Geist Mono, or Geist Pixel', 'setting up font imports') but 'applying Vercel typography and aesthetic guidance' is vague and coverage has minor gaps, fitting anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	Explicitly states what ('Expert guidance for Geist, Vercel's default typography system and font family for precise Next.js interfaces') and when ('Use when configuring...'), matching the anchor-5 example of clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural terms (Geist, Geist Sans/Mono/Pixel, font imports, typography, Next.js) but omits common variations users would say such as 'next/font', the 'geist' npm package, and CSS variables, so it sits at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The Geist font family niche is highly specific with distinct triggers, but the broad phrase 'Vercel typography and aesthetic guidance' carries minor overlap risk with a general Vercel design-system skill, fitting anchor 4 over 5.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/vercel/skills/geist/SKILL.md
Commit: d416fd5

Reviewed: 4 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.