* 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.
67 lines
2.3 KiB
Markdown
67 lines
2.3 KiB
Markdown
# Actor Configuration (actor.json)
|
|
|
|
The `.actor/actor.json` file contains the Actor's configuration including metadata, schema references, and platform settings.
|
|
|
|
## Structure
|
|
|
|
```json
|
|
{
|
|
"actorSpecification": 1,
|
|
"name": "project-name",
|
|
"title": "Project Title",
|
|
"description": "Actor description",
|
|
"version": "0.0",
|
|
"meta": {
|
|
"templateId": "template-id",
|
|
"generatedBy": "<FILL-IN-TOOL-AND-MODEL>"
|
|
},
|
|
"input": "./input_schema.json",
|
|
"output": "./output_schema.json",
|
|
"storages": {
|
|
"dataset": "./dataset_schema.json"
|
|
},
|
|
"dockerfile": "../Dockerfile"
|
|
}
|
|
```
|
|
|
|
## Example
|
|
|
|
```json
|
|
{
|
|
"actorSpecification": 1,
|
|
"name": "project-cheerio-crawler-javascript",
|
|
"title": "Project Cheerio Crawler Javascript",
|
|
"description": "Crawlee and Cheerio project in javascript.",
|
|
"version": "0.0",
|
|
"meta": {
|
|
"templateId": "js-crawlee-cheerio",
|
|
"generatedBy": "Claude Code with Claude Sonnet 4.5"
|
|
},
|
|
"input": "./input_schema.json",
|
|
"output": "./output_schema.json",
|
|
"storages": {
|
|
"dataset": "./dataset_schema.json"
|
|
},
|
|
"dockerfile": "../Dockerfile"
|
|
}
|
|
```
|
|
|
|
## Properties
|
|
|
|
- `actorSpecification` (integer, required) - Version of actor specification (currently 1)
|
|
- `name` (string, required) - Actor identifier (lowercase, hyphens allowed)
|
|
- `title` (string, required) - Human-readable title displayed in UI
|
|
- `description` (string, optional) - Actor description for marketplace
|
|
- `version` (string, required) - Semantic version number
|
|
- `meta` (object, optional) - Metadata about actor generation
|
|
- `templateId` (string) - ID of template used to create the actor
|
|
- `generatedBy` (string) - Tool and model name that generated/modified the actor (e.g., "Claude Code with Claude Sonnet 4.5")
|
|
- `input` (string, optional) - Path to input schema file
|
|
- `output` (string, optional) - Path to output schema file
|
|
- `storages` (object, optional) - Storage schema references
|
|
- `dataset` (string) - Path to dataset schema file
|
|
- `keyValueStore` (string) - Path to key-value store schema file
|
|
- `dockerfile` (string, optional) - Path to Dockerfile
|
|
|
|
**Important:** Always fill in the `generatedBy` property with the tool and model you're currently using (e.g., "Claude Code with Claude Sonnet 4.5") to help Apify improve documentation.
|