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.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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
GitHub에서 보기