Teach your skill to critique a reader's first attempt

To teach a skill to critique reader work, give it four things: the submitted attempt, the purpose of the exercise, your criteria for a useful result, and a limit on what it should correct first. Require it to point to evidence in the attempt before recommending a change. Then ask the reader to revise.

That creates a different experience from generating a fresh answer. A reader who has written a project update needs to understand why their update leaves colleagues uncertain. Receiving a beautifully rewritten update might help them meet today's deadline, but it does not, by itself, explain what to notice next time.

For an author, this is a useful place to begin an applied companion to a book. Choose one exercise readers already attempt. Specify what you would notice, what you would preserve, and which correction deserves attention before the others. Your first version can review that one exercise without claiming to coach every situation in the book.

The worked example below is fictional. The submissions and feedback are proposed teaching material, not observed reader behavior or outputs from an executed model test.

Imagine you wrote a practical book about communicating progress on small projects. One exercise asks readers to write an update that helps a colleague decide whether to intervene.

Your method has three requirements:

1. State what has actually changed since the previous update.
2. Separate a confirmed fact from a forecast or unresolved dependency.
3. Name any decision needed, including who needs to make it and when.

You also have a boundary: an update cannot establish a delivery date that the project team has not confirmed. Confident wording does not fix missing evidence.

Those instructions give the skill a basis for reviewing the work. “Make this clearer and more professional” leaves too many decisions unspecified. It might produce a smoother paragraph while retaining the unsupported promise that mattered most.

The review request should therefore include the intended reader and purpose. A private note to yourself and an update asking a project sponsor to resolve a dependency are different tasks. If that context is missing, the skill should ask for it before scoring the attempt against the wrong standard.

Keep the intake small. For this exercise, request the draft, the audience, the decision the update should support, and any facts the reader wants the critique to rely on. Do not demand a complete project history before offering useful feedback.

A critique needs a hierarchy. Otherwise, every departure from your preferred style can appear as a defect.

For the fictional update method, use this order:

The last row is deliberately different. A reader should not be told that their method is wrong because they prefer a conversational opening.

This distinction also tells you what positive feedback means. “Great job” is pleasant but hard to use. “You named the supplier response as the unresolved dependency; keep that detail” identifies something the reader should preserve during revision.

Use your actual book's principles here. If your method rewards exploration before commitment, do not import a generic rubric that treats every open question as a weakness. The purpose of the companion is to help readers apply your approach, including the tradeoffs you deliberately teach.

Here is the fictional reader's draft:

Everything is going well with the exhibition booklet. We made good progress this week and should be ready to print Friday. There are a few small things left with the images. Let me know if you have any questions.

The reader supplies these facts separately:

• The text has been approved.
• Two image files have not arrived from the photographer.
• The printer needs final files by Thursday noon to print Friday.
• The project sponsor can decide to omit the missing images.
• Nobody has asked the sponsor to make that decision yet.

A critique should compare the paragraph with these facts, rather than inventing new project details. Here is an author-written annotation:

This is a diagnostic view for the author. You do not have to show every row to the reader at once. Its purpose is to make the review traceable: each proposed correction connects a visible passage to a stated criterion.

Notice what the annotation does not do. It does not accuse the reader of hiding information. It does not claim the photographer is unreliable. It does not decide that the missing images should be omitted. Those conclusions go beyond the submitted material.

A useful first response could look like this:

Keep: Your update is short and gives the recipient a clear subject: the exhibition booklet.

First revision: Replace the unconditional reassurance with the confirmed progress and the unresolved dependency. The text is approved, but two image files are still missing. Your Friday printing forecast depends on supplying final files by Thursday noon.

Second revision: Ask the sponsor for the decision you need. State the choice about omitting the images, and confirm the latest useful decision time before inserting it.

Revise those two points in your own words. We can review the sentence style afterward.

This proposed response keeps the reader doing the work. It also declines to fabricate the decision deadline. Thursday noon is the printer's file deadline; the sponsor may need to decide earlier to allow time for layout changes.

Limiting priorities is a design choice for this exercise, not a universal rule that feedback must contain exactly two points. A submission with a serious factual problem may need only one correction. A reader explicitly requesting a detailed final review may want a longer list.

There is a recognizable human problem behind that choice. In a discussion about receiving valuable but difficult fiction feedback, u/SofaBaker described feeling overwhelmed:

“now I’m feeling overwhelmed with the amount of work I will have to do in the 2nd and 3rd draft stages.”

That is one writer's account, not evidence that thorough feedback is generally harmful. For your companion, it is a reason to make the next revision legible instead of treating a long inventory of flaws as a complete teaching response.

Sometimes the reader will understand the criticism but still need an example. Allow that option without making a full replacement the default.

In a writing discussion, u/YetAnotherAuthor explained the value of an example:

“Sometimes it is easier to explain what you mean in an example than just explaining it.”

The comment describes their experience with editors offering a rewrite and then giving the writer a chance to change it again. It supports a practical distinction: an example can demonstrate a move while leaving the final revision with the reader.

For the project update, demonstrate only the first move:

The booklet text is approved. Friday printing depends on receiving two missing image files in time to send the final layout by Thursday noon.

Explain what changed: the sentence now distinguishes completed work from a conditional forecast. Do not silently present it as the reader's verified final update. The reader still needs to check the facts and add the decision request.

Your skill instructions can state: offer one short example when the reader asks or when the correction is otherwise unclear; explain the principle it demonstrates; do not add facts; invite the reader to adapt it. That is specific enough to inspect in a trial.

Suppose the fictional reader confirms that the layout needs two hours after the sponsor's decision and returns this revision:

The booklet text is approved. We are waiting for two image files from the photographer. To keep Friday printing, we need the final layout ready by Thursday noon. Please decide by Thursday at 10 a.m. whether to omit those images if the files have not arrived. That leaves two hours to complete the layout.

The follow-up review should acknowledge the changes against the original priorities:

• The completed work and unresolved dependency are now separate.
• The forecast is conditional rather than assured.
• The request names a decision and its timing, using the new information the reader supplied.

It should also check whether the recipient is actually the sponsor. If that was confirmed in the intake, do not ask again. If it was never established, flag the routing question before declaring the exercise complete.

Do not invent another round of stylistic problems just to sustain the conversation. Under this exercise's criteria, a sufficiently clear and accurate update can be finished. Readers need a stopping condition as well as corrective feedback.

Create a short review specification alongside your exercise:

Review the submitted update using the three method requirements. Identify the audience and purpose before judging it. Cite a passage for each substantive correction. Separate missing information from incorrect information. Preserve accurate, useful material. Prioritize no more than two changes in the first response unless another issue must be addressed before the draft can be used. Ask the reader to revise. Offer a limited example when useful, clearly labeling any placeholder. Recheck the revision against the original criteria and stop when those criteria are met.

Then try deliberately different submissions: a strong attempt, a polished attempt with an unsupported promise, a rough attempt with sound reasoning, and an incomplete submission. Save what the skill actually returns. Look for unearned praise, invented facts, excessive rewriting, and critiques that mistake your stylistic preferences for your method.

The guide to measuring agent skill quality can help structure that evaluation. For this reader exercise, the key question is concrete: does the feedback help the reader see and repair the important gap in their own attempt?

Once you have one exercise, its criteria, and a few examples of useful feedback, bring them to Skillfully and choose Book onboarding. That gives the conversation a clear starting point: the reader's work, the judgment you want to preserve, and the next revision your companion should help them make.