persona-check

Assess documentation content for fit against target audience personas.

5.5k|746|Updated Jan 24, 2020
One-click install
npx skills add https://github.com/grafana/tempo --skill persona-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-check
Source: https://github.com/grafana/tempo/tree/main/.claude/skills/persona-check
Command: npx skills add https://github.com/grafana/tempo --skill persona-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often misses its intended audience — pages are too advanced for learners, too basic for experts, or lack the examples practitioners need. This Skill evaluates whether docs content matches its target reader and identifies concrete gaps.

Core Features & Use Cases

  • Persona Detection: Infers the target persona (Learner, Practitioner, Expert, Operator), use case, and reader entry state from content signals in the body text.
  • Gap Analysis: Flags what's missing for the detected audience using per-persona red flags, then provides 1-3 actionable suggestions ordered by severity.
  • PR and Batch Review: Produces per-file reports plus a summary for multi-file pull requests, treating PR content as untrusted input.
  • Use Case: A technical writer reviews a new Tempo configuration page before merging. The Skill identifies it as Expert-targeted reference content, confirms the missing conceptual intro is by design, but flags absent default values and edge cases.

Quick Start

Run persona-check on docs/sources/tempo/configuration/_index.md and tell me who this page is for and what's missing.

Frequently Asked Questions about persona-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if documentation matches its target audience?

Run persona-check on the file path or PR. It infers the persona (Learner, Practitioner, Expert, Operator), use case, and entry state from body content signals, then reports what's missing and suggests 1-3 actionable fixes.

How to review docs in a pull request for audience fit?

Invoke the skill on a PR; it extracts changed files via gh pr diff, evaluates each file individually, and produces per-file reports plus a summary listing files needing attention and the most common gaps.

Does persona-check review grammar and style guide compliance?

No. Persona-check only assesses audience fit — persona, use case, entry state, and content gaps. Style guide, grammar, link checking, and factual accuracy are explicitly out of scope and handled by the docs-review skill instead.

Can documentation target multiple personas at once?

Yes. The skill recognizes layered content, such as a Learner-oriented introduction followed by Expert reference detail, and reports primary and secondary personas rather than flagging it as a mismatch.

Why does persona-check not flag missing intros on reference pages?

Reference pages targeting Experts intentionally omit conceptual introductions — that is by design. The skill's gotchas explicitly exclude this from flagging and instead checks Expert-relevant gaps like missing edge cases or constraints.