Skip to main content

write-an-annotated-bibliography

Produce consistent source annotations that summarize, evaluate, and explain relevance without copying abstracts. Use when preparing a research project or source review.

Source facts

Repository
protosphinx/sphinxstack
Last source activity
July 29, 2026 at 13:55
Detected SKILL.md language
English
Stars
3
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
write-an-annotated-bibliography
category
school
description
Produce consistent source annotations that summarize, evaluate, and explain relevance without copying abstracts. Use when preparing a research project or source review.
# write-an-annotated-bibliography Each annotation should tell the reader what the source contributes, how it knows, and how cautiously it should be used. ## When to use - Use for course assignments, project scoping, literature reviews, and team research handoffs. - Confirm the required citation style, annotation length, and whether annotations are descriptive, evaluative, or both. ## Procedure 1. Record verified bibliographic metadata from the source or authoritative index. 2. Read beyond the abstract: inspect the argument, evidence, methods, population, period, and limitations. 3. Write a concise summary of the source’s actual purpose and findings in original language. 4. Evaluate directness, methods, credibility, important limitations, and conflicts or corrections. 5. Explain how the source informs the research question, contrasts with another source, or leaves a gap. 6. Use a consistent structure and length across entries. 7. Distinguish the source’s claims from the annotator’s interpretation. 8. Check quotations, page locators, identifiers, capitalization, dates, and citation-style details. 9. Order entries as required and add a short synthesis when the assignment calls for one. ## Failure plan - Do not paste or lightly rewrite abstracts. - If full text was unavailable, say so and limit the evaluation accordingly. - Do not call a source biased merely because it reaches an unwelcome conclusion; identify the evidence. - If citation metadata conflicts, resolve it against the original publication and record the version used. ## Done - Every entry has accurate metadata, faithful summary, evidence-based evaluation, and clear relevance - Annotation structure and citation style are consistent - Access limits and uncertainties are visible
View on GitHub