Receber por email
← Voltar para o catálogo

harvest-adaptive

Adaptive content summarization - auto-detect content type and produce relevant summary

507estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add vibeeval/vibecosystem

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/harvest-adaptive/svg)](https://www.skillteca.com.br/skills/harvest-adaptive)
#ai

Alerta por categoria

Receba novas skills de Escrita e Conteúdo toda segunda

1 email curto, só com as skills novas de Escrita e Conteúdo. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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
Compartilhar X LinkedIn