1
Hook diagnosis: Review only the opening story paragraph. Identify the protagonist, immediate goal, obstacle, and stakes you can actually infer. List any sentence that sounds intriguing but leaves the causal situation unclear.
8 AI Query Letter Review Examples
Use these examples to study structure, specificity, tone, and variation. They are demonstrations—not claims about a real person or organization unless the example itself makes that explicit.
Before you copy
What to notice in the examples
A useful AI query-letter review works from an explicit rubric instead of asking for a generic rewrite. It separates diagnosis from revision, identifies what evidence or manuscript context the model cannot know, preserves the author’s voice, and requires manual verification of word count, genre, comparable titles, submission instructions, and other factual metadata.
- Provide the query letter plus only the manuscript context needed for the review.
- State the review criteria: hook clarity, protagonist/goal, conflict/stakes, metadata, bio relevance, and closing.
- Ask for diagnosis before rewritten language.
- Separate subjective craft feedback from factual claims that require verification.
- Revise selectively and compare the new letter with the manuscript and target submission requirements.
2
Structure review: Label each paragraph by job—story hook, metadata, author bio, closing—and flag any paragraph doing two incompatible jobs or repeating information.
3
Voice review: Identify phrases that sound generic or promotional compared with the rest of the letter. Suggest narrower alternatives without changing plot facts.
4
Stakes check: List every stated consequence in the query. Mark whether each consequence appears concrete, implied, or unsupported by the text provided.
5
Metadata review: Extract title, genre, age category, word count, comps, and manuscript status into a checklist so I can verify each item manually.
6
Comp-title safety check: Do not recommend new comps. Instead, explain what claim each comp in my draft appears to make about audience, tone, structure, or market position, and list what I should verify independently.
7
Revision comparison: Compare version A and version B of the hook. Explain which version makes goal, conflict, and stakes easier to understand without evaluating the manuscript itself.
8
Submission-fit review: Using only the submission requirements I paste below, make a checklist of query elements that comply, conflict, or need manual confirmation. Do not infer any unstated agent preference.
Keep the underlying decision or pattern, then replace the subject, evidence, relationship, constraints, and tone with details that belong to your situation. If your final line still works after swapping only one noun, it may be too close to the example.