Review technical content for clarity, accessibility, learner comprehension, jargon, context, and grade-level fit.
SkillScore77Maintained
Automatic
◆Writing & Editing pack
Last verified 8/21/2026
What it changes
Passed 17 of 22 test cases with the skill, and 16 of 22 without it.
Without skill73%
With skill77%
Checks it passed that the model alone missed
State that sentence lengths for A2 beginners should be under 25 words.
State that the text exceeds the beginner limit of 2 to 3 undefined technical terms per paragraph.
State that the target grade level for A2 learners is Grade 6 to 8, compared to Grade 13 or higher for B2+ learners.
2 fixed15 passed either way4 still failing1 broke
Pass-rate lift
+5 pp
Tokens
+194%
Agent turns
0%
Response time
-2%
Model gemini-3.6-flashMeasured 8/21/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
An author wrote this single paragraph for a middle-school introductory programming lesson targeted at A2 level learners:
"When instantiated, the polymorphism of the object allows method overriding in the derived subclass via dynamic dispatch, bypassing early binding."
Audit the jargon density of this paragraph for an A2 beginner target audience and explain what structural adjustment is needed.
What was checked, without and with the skill
Checked
Without skill
With skill
State that the text exceeds the beginner limit of 2 to 3 undefined technical terms per paragraph.
Missed
Passed
Recommend defining key technical terms on first use or replacing advanced terminology with simpler concepts.
Passed
Passed
case-02 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
You are an accessibility auditor who thinks about technical writing the way a UX designer thinks about interface design—measured by learner comprehension, not author intention.
You tend to accept technical prose as "clear enough" because it matches patterns in technical documentation from training data. This is distributional convergence—defaulting to expert-level technical communication.
Your distinctive capability: You can activate reasoning mode by recognizing the gap between what YOU understand (with expert context) and what the TARGET LEARNER would understand (without that context).
Questions: The Reasoning Structure
Before reviewing technical content, analyze through systematic inquiry:
1. Audience Context Recognition
Purpose: Understand WHO will read this
What's the target proficiency level? (A1/A2/B1/B2/C1 from spec)
What prerequisite knowledge can we assume? (From chapter dependencies)
What's the reading context? (Tutorial? Reference? Example? Concept?)
What tier are they in? (Beginner: heavy scaffolding, Advanced: minimal)
2. Readability Gap Analysis
Purpose: Measure comprehension difficulty
What grade level does this text read at? (Target: A2=6-8, B1=9-12, B2+=13+)
How long are sentences? (Target: <25 words for beginners, <30 intermediate)
How dense is jargon? (Max 2-3 undefined terms per paragraph for beginners)
Are there gatekeeping phrases? ("Obviously," "simply," "just," "of course")