Agent skill
harvest-single
Single page smart extraction - articles, docs, blog posts to clean markdown
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/harvest-single
SKILL.md
Harvest Single Page
Extract and clean content from a single web page. Auto-detects content type (article, documentation, API reference, blog post) and produces clean, structured markdown.
Usage
/harvest <url>
Examples
# Extract a blog post
/harvest https://blog.example.com/best-practices-2024
# Extract API documentation page
/harvest https://docs.stripe.com/api/charges
# Extract a GitHub README
/harvest https://github.com/owner/repo
How It Works
- Fetch URL content via WebFetch or crawl4ai
- Detect content type (article, docs, API ref, blog, wiki)
- Extract main content, strip navigation/ads/footers
- Preserve code blocks, tables, images
- Add metadata header (source, date, word count)
- Save to
.claude/cache/agents/harvest/
Output Format
# [Page Title]
> Source: [URL]
> Extracted: [timestamp]
> Type: [article|docs|api|blog|wiki]
> Words: [count]
[Clean extracted content in markdown]
## Links Found
- [Link text](URL)
Fallback Chain
- crawl4ai Docker (port 11235) - preferred
- WebFetch tool - built-in fallback
- curl + html2text - last resort
When to Use
- Quick grab of a single page's content
- Extracting a specific doc page for reference
- Saving an article for later analysis
- Getting clean markdown from messy HTML
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?