geistdocs

Expert guidance for Geistdocs, Vercel's documentation template built with Next.js and Fumadocs — MDX authoring, configuration, AI chat, i18n, feedback, deployment. Use when creating documentation sites, configuring geistdocs, writing MDX content, or setting up docs infrastructure.

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

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.

Highly actionable and well-sequenced reference content with excellent executable examples. The main weakness is structure: everything is inlined into one file with no local progressive-disclosure references, and version-sensitive pins are not isolated.

Suggestions

Move the syntax/code-block attribute reference and the per-feature details into separate bundle files (e.g. references/syntax.md, references/features.md) and link to them one level deep from the body to improve progressive disclosure.

Add explicit validation checkpoints to the workflows, e.g. 'Open http://localhost:3000 to confirm the dev server runs' after `pnpm dev` and a post-deploy verification step in the Deployment section.

Isolate time-sensitive pins (Next.js 16, gpt-4.1-mini, the 2025-11-12 lastModified example) into a clearly labeled versions/compatibility note so they do not penalize conciseness and age visibly.

Dimension	Reasoning	Score
Conciseness	The body is lean and reference-style with no concept padding, but scattered version/date-sensitive pins ('Next.js 16', 'openai/gpt-4.1-mini', 'lastModified: 2025-11-12', 'Currently in beta') sit outside any deprecated/old-patterns section, a minor conciseness ding.	4 / 5
Actionability	Copy-paste-ready executable guidance throughout: 'npx @vercel/geistdocs init', 'pnpm dev', a full geistdocs.tsx config block, MDX frontmatter, code-block attribute tables, and the pnpm translate command cover the common cases.	5 / 5
Workflow Clarity	Getting Started and Deployment present clear numbered sequences, but validation checkpoints are implicit (no 'verify dev server at localhost:3000' or post-deploy verify step); this is a setup rather than destructive/batch skill so the cap does not apply.	4 / 5
Progressive Disclosure	The body is a single ~215-line monolithic file with no bundle files present; substantial reference content (syntax tables, full feature catalog, code-block attributes) that could live in separate bundle files is inlined, and the only deeper pointers are external URLs rather than one-level-deep local references.	3 / 5
	Total	16 / 20 Passed

Description

87%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.

A strong description with a clear what/when structure, concrete capability list, and a distinct product niche. Minor gains are available by converting feature nouns into verbs and adding synonym/extension triggers.

Dimension	Reasoning	Score
Specificity	Lists several concrete feature areas — 'MDX authoring, configuration, AI chat, i18n, feedback, deployment' — but these are feature nouns rather than verb-driven actions, leaving minor coverage gaps versus a fully comprehensive action list.	4 / 5
Completeness	Explicitly answers both 'what' (expert guidance for Geistdocs with the listed capabilities) and 'when' ('Use when creating documentation sites, configuring geistdocs, writing MDX content, or setting up docs infrastructure') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The 'Use when' clause supplies natural terms ('creating documentation sites', 'writing MDX content', 'docs infrastructure', 'geistdocs') with good coverage, but omits common synonyms and file extensions that would reach comprehensive.	4 / 5
Distinctiveness Conflict Risk	Names a distinct product (Geistdocs) anchored to Vercel + Fumadocs + Next.js, giving it a clear niche with minimal conflict risk against other documentation skills.	5 / 5
	Total	18 / 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/geistdocs/SKILL.md
Commit: d416fd5

Reviewed: 11 hours 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.