recoup-web-intelligence
Web research, deep research, URL extraction, and entity enrichment via the Recoup research API. Use when structured artist data is unavailable, when you need narrative context from the web, when enriching entities with structured facts, or when extracting content from URLs. Also the graceful degradation fallback when other research skills return empty. Triggers on "web search", "deep research", "extract from URL", "enrich", "what does this page say", or when primary research endpoints return no data.
What this skill does
# Web Intelligence
Web research, deep cited reports, URL extraction, and structured entity
enrichment through the Recoup research API. This is also the **graceful
degradation fallback** when the structured (Songstats-backed) endpoints return
empty.
```bash
export RECOUP_API_KEY="recoup_sk_..."
export RECOUP_API="https://api.recoupable.com/api"
```
## Decision tree
- **"Search the web for [topic]"** → `POST /research/web`
- **"Give me a deep report on [topic]"** → `POST /research/deep`
- **"What does this page say?"** → `POST /research/extract`
- **"Enrich [entity] with structured data"** → `POST /research/enrich`
- **Structured endpoints returned empty** → Graceful Degradation chain
## Web Search
Quick ranked web results (~seconds):
```bash
curl -s -X POST "$RECOUP_API/research/web" \
-H "x-api-key: $RECOUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"emerging indie R&B artists 2026","max_results":10,"country":"US"}'
```
Body: `query` (required), `max_results` (1–20, default 10), `country` (2-letter
ISO, optional). Returns `{ results: [{ title, url, snippet, date, last_updated }],
formatted }` — `formatted` is a ready-to-read markdown digest.
## Deep Research
Comprehensive cited narrative report (~2+ min):
```bash
curl -s -X POST "$RECOUP_API/research/deep" \
-H "x-api-key: $RECOUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"why is [artist] going viral on TikTok in [country]"}'
```
Body: `query` (required) only. Returns `{ content (markdown), citations: [url, ...] }`.
**Note:** This endpoint takes 2+ minutes. Set client timeout to ≥3 min.
## URL Extraction
Extract readable content from specific URLs:
```bash
curl -s -X POST "$RECOUP_API/research/extract" \
-H "x-api-key: $RECOUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{"urls":["https://example.com/article","https://linkedin.com/in/person"],"objective":"key facts, quotes, and data points","full_content":false}'
```
Body: `urls` (required, 1–10), `objective` (optional, ≤3000 chars, guides what
gets extracted — be specific), `full_content` (default `false`; set `true` for
the whole page instead of focused excerpts). Returns
`{ results: [{ url, title, publish_date, excerpts[], full_content }], errors[] }`.
## Entity Enrichment
Extract structured facts about any entity (~60–90s):
```bash
curl -s -X POST "$RECOUP_API/research/enrich" \
-H "x-api-key: $RECOUP_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": "<entity name — artist, label, manager, songwriter, venue>",
"schema": {
"type": "object",
"properties": {
"founded": {"type": "string"},
"ceo": {"type": "string"},
"notable_artists": {"type": "array", "items": {"type": "string"}},
"revenue_estimate": {"type": "string"},
"recent_news": {"type": "array", "items": {"type": "string"}}
}
},
"processor": "core"
}'
```
Body: `input` (required), `schema` (required — **must include `"type":"object"`
at the top level**), `processor` (`base` default = fast / `core` = balanced /
`ultra` = comprehensive). Returns `{ output: { ...your schema... },
citations: [{ url, title, field }] }`.
## Graceful Degradation Chain
When the structured endpoints come up empty (search returns `{ results: [] }`,
or `/profile` and `/metrics` are thin), fall through:
1. **`POST /research/web`** — ranked web results (~seconds)
2. **`POST /research/enrich`** — structured facts (~60–90s)
3. **`POST /research/deep`** — cited narrative (~2+ min)
For very emerging artists, Songstats may not have data. Web + enrich + deep is
the full alternative path.
### When to trigger graceful degradation
- `GET /research?q=...` returns `{ results: [] }`
- `/research/lookup?url=...` returns non-200
- `/research/profile` returns thin data and `/research/metrics` has no `stats`
- Any endpoint returns `501` (`Request failed with status 501` = data source
doesn't support that shape) — treat it like "no data"
## Critical gotchas
- **`/research/enrich` schemas must include `"type":"object"` at the top level.**
Endpoint rejects schemas without it.
- **`enrich` default `processor` is `base`** (fast). Pass `core` for balanced or
`ultra` for comprehensive — these take longer.
- **POST endpoint latency:** `/enrich` 60–90s (`core`/`ultra` longer), `/deep` 2+
min, `/web` and `/extract` are seconds-to-tens. Set client timeouts accordingly.
- **`/research/deep` is expensive** (time and credits). Use `/web` first for quick
answers; reserve `/deep` for when you need cited narrative.
- **`/research/extract` objective field matters.** Vague objectives = vague results.
## References
- **`references/endpoints.md`** — POST endpoint details
- **`references/workflows.md`** — chaining rules, when NOT to chain
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.