Review CircleCI documentation pages for quality, clarity, and adherence to style guidelines. Use this skill whenever the user asks to review, audit, or assess documentation content, check for style compliance, evaluate page quality, or wants feedback on docs pages. Also trigger when the user mentions content quality, readability issues, or asks "how does this page look" or "is this page good." Even if they just reference a docs file path and ask for a review or feedback, use this skill.
78
—
Does it follow best practices?
Impact
72%
1.04xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Report structure and 10-dimension evaluation
Correct file naming
0%
0%
Executive Summary present
83%
50%
Priority Recommendations present
66%
83%
Priority level labels used
100%
66%
Recommendation includes Category field
40%
0%
Recommendation includes Impact field
40%
0%
Recommendation includes Recommendation field
100%
60%
Detailed Findings section present
83%
50%
Consistency Check section present
100%
100%
Positive Highlights section present
0%
16%
Overall Assessment section present
0%
0%
Audience identified
100%
0%
Flags buried critical info
100%
100%
Flags vague headings
100%
100%
Flags weak opening/value proposition
100%
100%
Flags incomplete code block
100%
80%
Server Admin page audience and buried critical info
Correct file naming
0%
0%
Server Admin audience identified
0%
50%
Flags SSL requirement buried in CAUTION
100%
100%
Flags version constraint in NOTE
100%
100%
Flags skipped heading level
100%
100%
Code blocks lack inline comments
100%
100%
Priority Recommendations present
71%
100%
Detailed Findings covers multiple dimensions
100%
71%
Consistency Check section present
100%
100%
Positive Highlights present
0%
0%
Recommendations are actionable
100%
100%
Flags weak or missing section intros
100%
100%
No rewritten content
33%
0%
Cross-page consistency and terminology audit
Correct file naming
0%
100%
Related pages named in Consistency Check
100%
100%
Flags step vs task terminology mismatch
100%
100%
Flags cache vs artifact terminology
12%
0%
Positive highlights present
100%
100%
Executive Summary present
100%
100%
Priority Recommendations present
71%
100%
Code examples evaluated
100%
100%
Detailed Findings uses pass/issue markers
42%
100%
Why and How coverage assessed
100%
100%
Tone and audience noted
16%
100%
Recommendations actionable not rewrites
100%
83%
Overall Assessment present
0%
100%
Issues prioritized by impact
83%
100%
65ff472
Table of Contents
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.