SkillHub ClubShip Full StackFull Stack

article-analysis

Imported from https://github.com/az9713/cerebro.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 20, 2026

Overall rating

C3.1

Composite score

3.1

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install az9713-cerebro-article-analysis

Repository

az9713/cerebro

Skill path: .claude/skills/article-analysis

Imported from https://github.com/az9713/cerebro.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: az9713.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install article-analysis into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/az9713/cerebro before adding article-analysis to shared team environments
Use article-analysis for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: article-analysis
description: 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.
---

# 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:
```markdown
# [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/`