2f55f046b9
* feat: add 12 official Apify skills for web scraping and data extraction Add the complete Apify agent-skills collection as official vendor skills, bringing the total skill count from 954 to 966. New skills: - apify-actor-development: Develop, debug, and deploy Apify Actors - apify-actorization: Convert existing projects into Apify Actors - apify-audience-analysis: Audience demographics across social platforms - apify-brand-reputation-monitoring: Track reviews, ratings, and sentiment - apify-competitor-intelligence: Analyze competitor strategies and pricing - apify-content-analytics: Track engagement metrics and campaign ROI - apify-ecommerce: E-commerce data scraping for pricing intelligence - apify-influencer-discovery: Find and evaluate influencers - apify-lead-generation: B2B/B2C lead generation from multiple platforms - apify-market-research: Market conditions and geographic opportunities - apify-trend-analysis: Discover emerging trends across platforms - apify-ultimate-scraper: Universal AI-powered web scraper Existing skill fixes: - design-orchestration: Add missing description, fix markdown list spacing - multi-agent-brainstorming: Add missing description, fix markdown list spacing Registry and documentation updates: - Update skill count to 966+ across README.md, README.vi.md - Add Apify to official sources in SOURCES.md and all README variants - Register new skills in catalog.json, skills_index.json, bundles.json, aliases.json - Update CATALOG.md category counts (data-ai: 152, infrastructure: 95) Validation script improvements: - Raise description length limit from 200 to 1024 characters - Add empty description validation check - Apply PEP 8 formatting (line length, spacing, trailing whitespace) * refactor: truncate skill descriptions in SKILL.md files and revert description length validation to 200 characters. * feat: Add `apify-ultimate-scraper` to data-ai and move `apify-lead-generation` from business to general categories.
50 lines
1.9 KiB
Markdown
50 lines
1.9 KiB
Markdown
# Output Schema Reference
|
|
|
|
The Actor output schema builds upon the schemas for the dataset and key-value store. It specifies where an Actor stores its output and defines templates for accessing that output. Apify Console uses these output definitions to display run results.
|
|
|
|
## Structure
|
|
|
|
```json
|
|
{
|
|
"actorOutputSchemaVersion": 1,
|
|
"title": "<OUTPUT-SCHEMA-TITLE>",
|
|
"properties": {
|
|
/* define your outputs here */
|
|
}
|
|
}
|
|
```
|
|
|
|
## Example
|
|
|
|
```json
|
|
{
|
|
"actorOutputSchemaVersion": 1,
|
|
"title": "Output schema of the files scraper",
|
|
"properties": {
|
|
"files": {
|
|
"type": "string",
|
|
"title": "Files",
|
|
"template": "{{links.apiDefaultKeyValueStoreUrl}}/keys"
|
|
},
|
|
"dataset": {
|
|
"type": "string",
|
|
"title": "Dataset",
|
|
"template": "{{links.apiDefaultDatasetUrl}}/items"
|
|
}
|
|
}
|
|
}
|
|
```
|
|
|
|
## Output Schema Template Variables
|
|
|
|
- `links` (object) - Contains quick links to most commonly used URLs
|
|
- `links.publicRunUrl` (string) - Public run url in format `https://console.apify.com/view/runs/:runId`
|
|
- `links.consoleRunUrl` (string) - Console run url in format `https://console.apify.com/actors/runs/:runId`
|
|
- `links.apiRunUrl` (string) - API run url in format `https://api.apify.com/v2/actor-runs/:runId`
|
|
- `links.apiDefaultDatasetUrl` (string) - API url of default dataset in format `https://api.apify.com/v2/datasets/:defaultDatasetId`
|
|
- `links.apiDefaultKeyValueStoreUrl` (string) - API url of default key-value store in format `https://api.apify.com/v2/key-value-stores/:defaultKeyValueStoreId`
|
|
- `links.containerRunUrl` (string) - URL of a webserver running inside the run in format `https://<containerId>.runs.apify.net/`
|
|
- `run` (object) - Contains information about the run same as it is returned from the `GET Run` API endpoint
|
|
- `run.defaultDatasetId` (string) - ID of the default dataset
|
|
- `run.defaultKeyValueStoreId` (string) - ID of the default key-value store
|