article-analysis

az9713's avatarfrom az9713

Analyze blog posts and web articles by fetching content from URLs. Use when the user mentions blog post, article, Substack, Medium, web page, newsletter, or provides a URL to analyze.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 27, 2025
[Summarization]

When & Why to Use This Skill

This Claude skill automates the extraction and in-depth analysis of web-based content, including blog posts, newsletters, and articles from platforms like Substack and Medium. It streamlines information consumption by fetching live URL data to generate structured reports with summaries, key insights, and automated activity logging, making it an essential tool for digital knowledge management.

Use Cases

  • Rapidly summarizing long-form industry newsletters and Substack posts to extract core insights without manual reading.
  • Generating structured research reports from technical blog posts or Medium articles for professional documentation.
  • Building an organized archive of web content with automated date-stamped logging and sanitized file naming for easy retrieval.
  • Converting online articles into concise, actionable summaries to stay updated on market trends and news efficiently.
namearticle-analysis
descriptionAnalyze blog posts and web articles by fetching content from URLs. Use when the user mentions blog post, article, Substack, Medium, web page, newsletter, or provides a URL to analyze.

Web Article Analysis

Analyze blog posts, newsletters, and web articles to generate structured reports with summaries, key points, and insights.

When to Use

Activate this skill when the user:

  • Mentions "blog", "article", "post", "Substack", "Medium", "newsletter"
  • Provides a URL they want analyzed
  • Asks to summarize or analyze a web page
  • Wants to extract insights from online content

Instructions

  1. Get the URL - Ask the user for the URL if not provided
  2. Fetch the webpage content using WebFetch
  3. If fetch fails:
    • Inform user: "Could not fetch content from [url]"
    • Suggest: "Try copying the content manually to inbox/ and use /analyze"
    • Stop here
  4. Read the analysis prompt from prompts/article.md
  5. Extract the article title from the page content
  6. Generate analysis following the prompt structure exactly
  7. Save the report to reports/articles/YYYY-MM-DD_sanitized-title.md where:
    • YYYY-MM-DD is today's date
    • sanitized-title is the title in lowercase, spaces replaced with hyphens, special chars removed
  8. Update the activity log at logs/YYYY-MM-DD.md:
    • Create file if it doesn't exist
    • Add entry under "## Articles Read" section
    • Format: - [Title](../reports/articles/filename.md) - HH:MM
  9. Confirm to user what was saved and where

Report Format

Include this header in the report:

# [Article Title]

**Source**: [URL]
**Date**: YYYY-MM-DD
**Type**: Article

---

[Analysis content following prompts/article.md structure]

---

## My Notes

[Empty space for user notes]

Error Handling

  • If URL is invalid: Ask user for correct URL
  • If WebFetch fails: Suggest manual copy to inbox/
  • If prompts/article.md missing: Use prompts/default.md or basic structure

Related

  • Slash command equivalent: /read <url>
  • Prompt file: prompts/article.md
  • Output location: reports/articles/