Harvest Adaptive (Digest)
Automatically detect content type and produce the most useful summary. A blog post gets key takeaways. A library gets feature evaluation. Documentation gets structure overview. API reference gets endpoint catalog.
Usage
/digest <url>
Examples
# Evaluate a library
/digest https://github.com/owner/cool-library
# Summarize an article
/digest https://blog.example.com/microservices-patterns
# Overview documentation
/digest https://docs.example.com
Content Type Detection
| Type |
Signals |
Output Style |
| Library/Tool |
GitHub repo, npm page, PyPI |
Feature matrix, ecosystem health, recommendation |
| Blog/Article |
Single long-form content |
Key takeaways, relevance assessment |
| Documentation |
Multi-page, navigation structure |
Structure map, coverage assessment, quality |
| API Reference |
Endpoints, methods, params |
Endpoint catalog, auth info, SDK availability |
| Comparison |
Tables, vs, alternatives |
Feature matrix, winner per category |
| Tutorial |
Step-by-step, code blocks |
Prerequisites, steps summary, outcome |
Output Templates
Library Evaluation
# Library: [name]
> Source: [URL] | Stars: [X] | Last commit: [date]
## What It Does
[1-2 sentence description]
## Key Features
- Feature 1
- Feature 2
## Ecosystem Health
| Metric | Value |
|--------|-------|
| GitHub Stars | X |
| Weekly Downloads | X |
| Last Release | date |
| Open Issues | X |
| Contributors | X |
## API Surface
[Key classes/functions/exports]
## Verdict
[Use when... Don't use when... Alternatives: ...]
Article Summary
# Summary: [title]
> Source: [URL] | Author: [name] | Date: [date]
## Key Takeaways
1. [Point 1]
2. [Point 2]
3. [Point 3]
## Relevance
[How this applies to current project/context]
## Action Items
- [What to do based on this]
Rules
- Auto-detect, don't ask user for content type
- Keep summaries under 500 words
- Always include source URL and date
- For libraries: check last commit date, flag if > 6 months
- For articles: check publication date, flag if > 1 year
- Confidence rating on every assessment
1---2name: harvest-adaptive3description: Adaptive content summarization - auto-detect content type and produce relevant summary4---56# Harvest Adaptive (Digest)78Automatically detect content type and produce the most useful summary. A blog post gets key takeaways. A library gets feature evaluation. Documentation gets structure overview. API reference gets endpoint catalog.910## Usage1112```13/digest <url>14```1516## Examples1718```bash19# Evaluate a library20/digest https://github.com/owner/cool-library2122# Summarize an article23/digest https://blog.example.com/microservices-patterns2425# Overview documentation26/digest https://docs.example.com27```2829## Content Type Detection3031| Type | Signals | Output Style |32|------|---------|-------------|33| Library/Tool | GitHub repo, npm page, PyPI | Feature matrix, ecosystem health, recommendation |34| Blog/Article | Single long-form content | Key takeaways, relevance assessment |35| Documentation | Multi-page, navigation structure | Structure map, coverage assessment, quality |36| API Reference | Endpoints, methods, params | Endpoint catalog, auth info, SDK availability |37| Comparison | Tables, vs, alternatives | Feature matrix, winner per category |38| Tutorial | Step-by-step, code blocks | Prerequisites, steps summary, outcome |3940## Output Templates4142### Library Evaluation43```markdown44# Library: [name]45> Source: [URL] | Stars: [X] | Last commit: [date]4647## What It Does48[1-2 sentence description]4950## Key Features51- Feature 152- Feature 25354## Ecosystem Health55| Metric | Value |56|--------|-------|57| GitHub Stars | X |58| Weekly Downloads | X |59| Last Release | date |60| Open Issues | X |61| Contributors | X |6263## API Surface64[Key classes/functions/exports]6566## Verdict67[Use when... Don't use when... Alternatives: ...]68```6970### Article Summary71```markdown72# Summary: [title]73> Source: [URL] | Author: [name] | Date: [date]7475## Key Takeaways761. [Point 1]772. [Point 2]783. [Point 3]7980## Relevance81[How this applies to current project/context]8283## Action Items84- [What to do based on this]85```8687## Rules8889- Auto-detect, don't ask user for content type90- Keep summaries under 500 words91- Always include source URL and date92- For libraries: check last commit date, flag if > 6 months93- For articles: check publication date, flag if > 1 year94- Confidence rating on every assessment
vibeeval