react-pdf

React PDF renderer for json-render. Use when generating PDF documents from JSON specs, working with @json-render/react-pdf, or rendering specs to PDF buffers/streams/files.

Quality

88%

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

92%

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

A tight, highly actionable API reference with executable examples and no wasted tokens. The main gap is progressive disclosure: everything is inline rather than split into one-level-deep reference files.

Suggestions

Move the longer Custom Catalog / full component type definitions into a referenced reference file (e.g. CATALOG.md) and keep SKILL.md as an overview pointing to it.

Consider splitting the Standard Components table into a REFERENCE.md so the top-level skill stays a concise overview.

Dimension	Reasoning	Score
Conciseness	Lean reference with no preamble explaining PDFs or libraries; every section (Quick Start, Render APIs, components table, catalog) earns its place and assumes Claude's competence.	3 / 3
Actionability	Provides fully executable TypeScript with imports for renderToBuffer/renderToStream/renderToFile, defineCatalog, defineRegistry, and createStateStore — copy-paste ready.	3 / 3
Workflow Clarity	A single-purpose render skill with an unambiguous action and a clearly exposed API surface; no destructive/batch operations that would require validation checkpoints.	3 / 3
Progressive Disclosure	Sections are well-organized, but all content lives inline in one ~140-line file with no reference split, so content that could be separated (e.g. full catalog/types) is not.	2 / 3
	Total	11 / 12 Passed

Description

85%

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, specific description with an explicit 'Use when' trigger and a clear niche. The only weakness is trigger-term breadth, which over-relies on the package name and misses common user phrasings.

Suggestions

Add common natural phrasings users would actually say, e.g. 'create PDFs', 'PDFs', or 'build a PDF', alongside the package-specific triggers.

Soften reliance on the technical package name '@json-render/react-pdf' in the trigger clause so the description reads as user-oriented, not implementation-oriented.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'generating PDF documents from JSON specs' and 'rendering specs to PDF buffers/streams/files' — rather than vague language.	3 / 3
Completeness	Explicitly states what it does ('React PDF renderer for json-render') and when to use it via a clear 'Use when...' clause, answering both what and when.	3 / 3
Trigger Term Quality	Has natural terms like 'PDF documents' and 'PDF buffers/streams/files', but leans on the package jargon '@json-render/react-pdf' and omits common user phrasings like 'PDFs' or 'create PDFs'.	2 / 3
Distinctiveness Conflict Risk	Tied to a specific package niche (@json-render/react-pdf) with distinct triggers, making conflicts with other skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/json-render
Path: skills/react-pdf/SKILL.md
Commit: 9d3dfc8

Reviewed: about 13 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.