article-extractor

70
C

Extract clean article content from URLs (blog posts, articles, tutorials) and save as readable text. Use when user wants to download, extract, or save an article/blog post from a URL without ads, navigation, or clutter.

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install I-Onlabs/claude-code-skills/article-extractor
skilz install I-Onlabs/claude-code-skills/article-extractor --agent opencode
skilz install I-Onlabs/claude-code-skills/article-extractor --agent codex
skilz install I-Onlabs/claude-code-skills/article-extractor --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/I-Onlabs/claude-code-skills
2. Copy the agent skill directory:
cp -r claude-code-skills/article-extractor ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Type
Non-Technical
Meta-Domain
general
Primary Domain
general
Sub-Domain
javascript react code
Market Score
70

Agent Skill Grade

C
Score: 70/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
13/30
Ease of Use
24/25
Writing Style
8/10
Utility
20/20
Modifiers: -7

Areas to Improve

  • Lack of Layered Structure
  • Missing Table of Contents

Recommendations

  • Focus on improving Pda (currently 13/30)
  • Address 1 high-severity issues first
  • Add trigger phrases to description for discoverability

Graded: 2026-01-19

Developer Feedback

I took a look at your article-extractor skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 70/100, solidly in C territory. The skill's built on solid fundamentals—your Utility scores a perfect 20/20, which means this actually solves a real problem with good degrees of freedom. But Progressive Disclosure Architecture is dragging you down at 13/30. Based on Anthropic's best practices for agentic skills, this is really about structure and navigation efficiency.

What's Working Well

  • Utility is chef's kiss — You've nailed the core value prop. The skill addresses a clear need (clean article extraction), handles errors properly, and includes validation steps. That's the hard part.
  • Ease of Use is nearly perfect (24/25) — Your metadata, trigger phrases, and workflow clarity are all there. Developers will find and understand this easily.
  • Examples and templates are solid — You've included actual code patterns and complete workflows, not just theory.

The Big One: Layer Your Content

This is what's holding you back most. Right now you've got a 370-line SKILL.md file with everything crammed in—installation, methods, error handling, examples, all inline. That works at small scale, but it burns through tokens fast and makes navigation painful.

Here's the fix: Break it into a proper reference structure:

  • Keep SKILL.md as a ~80-100 line overview: metadata, quick description, 1-2 usage examples, and links to detailed docs
  • Move detailed installation to references/installation.md
  • Move each method (Puppeteer, Cheerio, Playwright, etc.) to its own file: references/method-puppeteer.md, etc.
  • Move error handling and edge cases to references/troubleshooting.md

This...

Report Security Issue

Found a security vulnerability in this agent skill?