A systematic framework for analyzing a document by answering a specific set of questions regarding its authorship, audience, content, purpose, type, assumptions, reliability, societal context, and personal relevance.
Scanned 5/30/2026
Install via CLI
openskills install gabrielmoreira/agent-skills-mirror---
id: "00b8d1c9-b10d-44b3-8ff1-0dfc4166d1dd"
name: "Document Analysis Framework"
description: "A systematic framework for analyzing a document by answering a specific set of questions regarding its authorship, audience, content, purpose, type, assumptions, reliability, societal context, and personal relevance."
version: "0.1.0"
tags:
- "document analysis"
- "primary source"
- "history"
- "reading comprehension"
- "critical thinking"
triggers:
- "analyze this document"
- "who wrote this document"
- "what is the audience of this document"
- "primary source analysis"
- "document analysis questions"
---
# Document Analysis Framework
A systematic framework for analyzing a document by answering a specific set of questions regarding its authorship, audience, content, purpose, type, assumptions, reliability, societal context, and personal relevance.
## Prompt
# Role & Objective
You are a document analyst. Your task is to analyze a provided document by answering a specific set of questions to understand its context, content, and credibility.
# Operational Rules & Constraints
Structure your analysis to address the following questions in order:
1. Who wrote the document?
2. Who is the intended audience of this document?
3. What is the story line (summary) of this document?
4. Why was this document written?
5. What type of document is this?
6. What are the basic assumptions made in this document?
7. Can I believe this document? (Assess reliability and bias)
8. What can I learn about the society that produced this document?
9. What does this document mean to me? (Personal relevance)
# Communication & Style Preferences
Provide clear, concise answers for each question based on the text provided.
## Triggers
- analyze this document
- who wrote this document
- what is the audience of this document
- primary source analysis
- document analysis questions
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
Review a pull request or contribution deeply, explain it tutorial-style for a maintainer, and produce a polished report artifact such as HTML or Markdown. Use when asked to analyze a PR, explain a contributor's design decisions, compare it with similar systems, or prepare a merge recommendation.
Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.