PaperLab Student Readability
When to Use
USE WHEN: improving a PaperLab textbook or course book for student learning,
especially after the scientific content is broadly complete. This skill checks
whether a chapter is easy to enter, easy to follow, and useful for exam and
exercise preparation.
DO NOT USE for: journal-paper conciseness, renderer debugging, or technical
validation of NeqSim calculations. Pair with paperlab-scientific-traceability-audit
for scientific claims and paperlab-book-typesetting-release for final formats.
Reader Model
Assume the primary reader is a student who:
- knows basic petroleum engineering terminology but not every industrial acronym,
- learns best from worked examples and recurring case threads,
- needs to connect equations, figures, and decisions,
- will use the book for exercises, exams, and project work,
- may be reading in English as a second language.
Chapter Checklist
For each chapter, check:
- Learning objectives: 3 to 7 objectives, written as observable actions.
Prefer verbs such as calculate, compare, explain, diagnose, design, and
evaluate. Avoid vague objectives such as "understand processing".
- Prerequisites: identify any concepts that must already be known. If a
prerequisite is not covered earlier, add a short bridge paragraph or a cross-reference.
- Concept sequence: introduce physical intuition before equations, and
equations before computational examples.
- Worked examples: include at least one compact worked example in core
engineering chapters. The example should state inputs, method, result,
interpretation, and common mistakes.
- Figures as teaching objects: each non-cover figure should be followed by
discussion using
figure-discussion.
- Exercises: include a mix of conceptual questions, calculation questions,
and short design-decision questions.
- Summary: close with decision-useful takeaways, not a table of contents in prose.
- Glossary and acronyms: define important first-use terms and keep names
consistent with the book glossary and acronym list.
Readability Rubric
Grade each chapter as ready, minor-revision, or major-revision.
| Area |
Ready Signal |
Revision Signal |
| Objectives |
Objectives map to sections and exercises |
Objectives are broad or missing |
| Flow |
Reader can follow the chapter without lecture context |
Chapter reads like stitched slides |
| Examples |
Examples show inputs, method, result, meaning |
Examples give numbers without interpretation |
| Language |
Sentences are direct and jargon is introduced |
Acronyms and compressed phrases dominate |
| Student Use |
Chapter supports exercises and exam preparation |
Chapter is mainly descriptive |
Output Pattern
Write a short chapter review with:
## Student Readability Review: <chapter>
- Status: ready | minor-revision | major-revision
- Best teaching asset: <figure/example/section>
- Main student friction: <one sentence>
- Required edits:
- <edit 1>
- <edit 2>
- Optional polish:
- <edit 3>
Common Fixes
- Replace long historical background with a short "why this matters" paragraph.
- Move dense slide coverage lists to an appendix or review artifact.
- Add a small numerical example after a new equation.
- Convert a generic summary into three to five engineering takeaways.
- Add a short "common mistake" note after unit-sensitive calculations.
1---2name: paperlab-student-readability-33description: |4 Review and revise PaperLab book chapters so students can learn efficiently.5 Use for learning-objective alignment, prerequisite checks, worked examples,6 summaries, exercises, glossary consistency, and chapter-level pedagogy.7last_verified: "2026-09-12"8metadata:9 source: https://skillmd.com/skills/equinor/paperlab-student-readability-310---1112# PaperLab Student Readability1314## When to Use1516USE WHEN: improving a PaperLab textbook or course book for student learning,17especially after the scientific content is broadly complete. This skill checks18whether a chapter is easy to enter, easy to follow, and useful for exam and19exercise preparation.2021DO NOT USE for: journal-paper conciseness, renderer debugging, or technical22validation of NeqSim calculations. Pair with `paperlab-scientific-traceability-audit`23for scientific claims and `paperlab-book-typesetting-release` for final formats.2425## Reader Model2627Assume the primary reader is a student who:2829- knows basic petroleum engineering terminology but not every industrial acronym,30- learns best from worked examples and recurring case threads,31- needs to connect equations, figures, and decisions,32- will use the book for exercises, exams, and project work,33- may be reading in English as a second language.3435## Chapter Checklist3637For each chapter, check:38391. **Learning objectives**: 3 to 7 objectives, written as observable actions.40 Prefer verbs such as calculate, compare, explain, diagnose, design, and41 evaluate. Avoid vague objectives such as "understand processing".422. **Prerequisites**: identify any concepts that must already be known. If a43 prerequisite is not covered earlier, add a short bridge paragraph or a cross-reference.443. **Concept sequence**: introduce physical intuition before equations, and45 equations before computational examples.464. **Worked examples**: include at least one compact worked example in core47 engineering chapters. The example should state inputs, method, result,48 interpretation, and common mistakes.495. **Figures as teaching objects**: each non-cover figure should be followed by50 discussion using `figure-discussion`.516. **Exercises**: include a mix of conceptual questions, calculation questions,52 and short design-decision questions.537. **Summary**: close with decision-useful takeaways, not a table of contents in prose.548. **Glossary and acronyms**: define important first-use terms and keep names55 consistent with the book glossary and acronym list.5657## Readability Rubric5859Grade each chapter as `ready`, `minor-revision`, or `major-revision`.6061| Area | Ready Signal | Revision Signal |62|------|--------------|-----------------|63| Objectives | Objectives map to sections and exercises | Objectives are broad or missing |64| Flow | Reader can follow the chapter without lecture context | Chapter reads like stitched slides |65| Examples | Examples show inputs, method, result, meaning | Examples give numbers without interpretation |66| Language | Sentences are direct and jargon is introduced | Acronyms and compressed phrases dominate |67| Student Use | Chapter supports exercises and exam preparation | Chapter is mainly descriptive |6869## Output Pattern7071Write a short chapter review with:7273```markdown74## Student Readability Review: <chapter>7576- Status: ready | minor-revision | major-revision77- Best teaching asset: <figure/example/section>78- Main student friction: <one sentence>79- Required edits:80 - <edit 1>81 - <edit 2>82- Optional polish:83 - <edit 3>84```8586## Common Fixes8788- Replace long historical background with a short "why this matters" paragraph.89- Move dense slide coverage lists to an appendix or review artifact.90- Add a small numerical example after a new equation.91- Convert a generic summary into three to five engineering takeaways.92- Add a short "common mistake" note after unit-sensitive calculations.