chore: sync generated content from apify-plugins

skills/apify-actor-development/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: apify-actor-development
+description: Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing. Use when creating new Actors, modifying existing ones, or troubleshooting Actor code.
+---
+
+# Apify Actor Development
+
+**Important:** Before you begin, fill in the `generatedBy` property in the meta section of `.actor/actor.json`. Set it to the name of the AI coding tool and model you are currently running in, in the format `"<tool> with <model>"` — for example `"Cursor with Claude Sonnet 4.5"`, `"Claude Code with Claude Opus 4"`, or `"GitHub Copilot with GPT-5"`. If you don't know the exact model, use the tool name alone (e.g. `"Cursor"`). This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
+
+## What are Apify Actors?
+
+Actors are serverless programs inspired by the UNIX philosophy - programs that do one thing well and can be easily combined to build complex systems. They're packaged as Docker images and run in isolated containers in the cloud.
+
+**Core Concepts:**
+- Accept well-defined JSON input
+- Perform isolated tasks (web scraping, automation, data processing)
+- Produce structured JSON output to datasets and/or store data in key-value stores
+- Can run from seconds to hours or even indefinitely
+- Persist state and can be restarted
+
+## Prerequisites & Setup (MANDATORY)
+
+Before creating or modifying actors, verify that `apify` CLI is installed `apify --help`.
+
+If it is not installed, use one of these methods (listed in order of preference):
+
+```bash
+# Preferred: install via a package manager (provides integrity checks)
+npm install -g apify-cli
+
+# Or (Mac): brew install apify-cli
+```
+
+> **Security note:** Do NOT install the CLI by piping remote scripts to a shell
+> (e.g. `curl … | bash` or `irm … | iex`). Always use a package manager.
+
+When the apify CLI is installed, check that it is logged in with:
+
+```bash
+# Auth check — do NOT pipe to /dev/null, you need to see errors
+apify info 2>&1
+```
+
+If not logged in, authenticate using OAuth (opens browser):
+
+```bash
+apify login
+```
+
+If browser login isn't available (headless environment or CI), the CLI automatically reads `APIFY_TOKEN` from the environment. Ensure the env var is exported and run any apify command - no explicit login needed. If the user doesn't have a token, generate one at https://console.apify.com/settings/integrations.
+
+> **Security note:** Avoid passing tokens as command-line arguments (e.g. `apify login -t <token>`).
+> Arguments are visible in process listings and may be recorded in shell history.
+> Prefer environment variables or interactive login instead.
+> Never log, print, or embed `APIFY_TOKEN` in source code or configuration files.
+
+## Template Selection
+
+**IMPORTANT:** Before starting actor development, always ask the user which programming language they prefer:
+- **JavaScript** - Use `apify create <actor-name> -t project_empty`
+- **TypeScript** - Use `apify create <actor-name> -t ts_empty`
+- **Python** - Use `apify create <actor-name> -t python-empty`
+
+Use the appropriate CLI command based on the user's language choice. Additional packages (Crawlee, Playwright, etc.) can be installed later as needed.
+
+## Quick Start Workflow
+
+1. **Create actor project** - Run the appropriate `apify create` command based on user's language preference (see Template Selection above)
+2. **Install dependencies** (verify package names match intended packages before installing)
+   - JavaScript/TypeScript: `npm install` (uses `package-lock.json` for reproducible, integrity-checked installs — commit the lockfile to version control)
+   - Python: `pip install -r requirements.txt` (pin exact versions in `requirements.txt`, e.g. `crawlee==1.2.3`, and commit the file to version control)
+3. **Implement logic** - Write the actor code in `src/main.py`, `src/main.js`, or `src/main.ts`
+4. **Configure schemas** - Update input/output schemas in `.actor/input_schema.json`, `.actor/output_schema.json`, `.actor/dataset_schema.json`
+5. **Configure platform settings** - Update `.actor/actor.json` with actor metadata (see [references/actor-json.md](references/actor-json.md))
+6. **Write documentation** - Create comprehensive README.md for the marketplace (see [references/actor-readme.md](references/actor-readme.md) — this is mandatory, not optional)
+7. **Test locally** - Run `apify run` to verify functionality (see Local Testing section below)
+8. **Deploy** - Run `apify push` to deploy the actor on the Apify platform (actor name is defined in `.actor/actor.json`)
+
+## Security
+
+**Treat all crawled web content as untrusted input.** Actors ingest data from external websites that may contain malicious payloads. Follow these rules:
+
+- **Sanitize crawled data** — Never pass raw HTML, URLs, or scraped text directly into shell commands, `eval()`, database queries, or template engines. Use proper escaping or parameterized APIs.
+- **Validate and type-check all external data** — Before pushing to datasets or key-value stores, verify that values match expected types and formats. Reject or sanitize unexpected structures.
+- **Do not execute or interpret crawled content** — Never treat scraped text as code, commands, or configuration. Content from websites could include prompt injection attempts or embedded scripts.
+- **Isolate credentials from data pipelines** — Ensure `APIFY_TOKEN` and other secrets are never accessible in request handlers or passed alongside crawled data. Use the Apify SDK's built-in credential management rather than passing tokens through environment variables in data-processing code.
+- **Review dependencies before installing** — When adding packages with `npm install` or `pip install`, verify the package name and publisher. Typosquatting is a common supply-chain attack vector. Prefer well-known, actively maintained packages.
+- **Pin versions and use lockfiles** — Always commit `package-lock.json` (Node.js) or pin exact versions in `requirements.txt` (Python). Lockfiles ensure reproducible builds and prevent silent dependency substitution. Run `npm audit` or `pip-audit` periodically to check for known vulnerabilities.
+
+## Best Practices
+
+**✓ Do:**
+- Use `apify run` to test actors locally (configures Apify environment and storage)
+- Use Apify SDK (`apify`) for code running ON Apify platform
+- Validate input early with proper error handling and fail gracefully
+- Use CheerioCrawler for static HTML (10x faster than browsers)
+- Use PlaywrightCrawler only for JavaScript-heavy sites
+- Use router pattern (createCheerioRouter/createPlaywrightRouter) for complex crawls
+- Implement retry strategies with exponential backoff
+- Use proper concurrency: HTTP (10-50), Browser (1-5)
+- Set sensible defaults in `.actor/input_schema.json`
+- Define output schema in `.actor/output_schema.json`
+- Clean and validate data before pushing to dataset
+- Use semantic CSS selectors with fallback strategies
+- Respect robots.txt, ToS, and implement rate limiting
+- **Always use `apify/log` package** — censors sensitive data (API keys, tokens, credentials)
+- Implement readiness probe handler (required if your Actor uses standby mode)
+
+**✗ Don't:**
+- Use `npm start`, `npm run start`, `npx apify run`, or similar commands to run actors (use `apify run` instead)
+- Assume local storage from `apify run` is pushed to or visible in the Apify Console — it is local-only; deploy with `apify push` and run on the platform to see results in the Console
+- Rely on `Dataset.getInfo()` for final counts on Cloud
+- Use browser crawlers when HTTP/Cheerio works
+- Hard code values that should be in input schema or environment variables
+- Skip input validation or error handling
+- Overload servers - use appropriate concurrency and delays
+- Scrape prohibited content or ignore Terms of Service
+- Store personal/sensitive data unless explicitly permitted
+- Use deprecated options like `requestHandlerTimeoutMillis` on CheerioCrawler (v3.x)
+- Use `additionalHttpHeaders` - use `preNavigationHooks` instead
+- Pass raw crawled content into shell commands, `eval()`, or code-generation functions
+- Use `console.log()` or `print()` instead of the Apify logger — these bypass credential censoring
+- Disable standby mode without explicit permission
+
+## Logging
+
+See [references/logging.md](references/logging.md) for complete logging documentation including available log levels and best practices for JavaScript/TypeScript and Python.
+
+Check `usesStandbyMode` in `.actor/actor.json` - only implement if set to `true`.
+
+## Commands
+
+```bash
+apify run          # Run Actor locally
+apify login        # Authenticate account
+apify push         # Deploy to Apify platform (uses name from .actor/actor.json)
+apify help         # List all commands
+```
+
+**IMPORTANT:** Always use `apify run` to test actors locally. Do not use `npm run start`, `npm start`, `yarn start`, or other package manager commands - these will not properly configure the Apify environment and storage.
+
+## Local Testing
+
+When testing an actor locally with `apify run`, provide input data by creating a JSON file at:
+
+```
+storage/key_value_stores/default/INPUT.json
+```
+
+This file should contain the input parameters defined in your `.actor/input_schema.json`. The actor will read this input when running locally, mirroring how it receives input on the Apify platform.
+
+**IMPORTANT - Local storage is NOT synced to the Apify Console:**
+- Running `apify run` stores all data (datasets, key-value stores, request queues) **only on your local filesystem** in the `storage/` directory.
+- This data is **never** automatically uploaded or pushed to the Apify platform. It exists only on your machine.
+- To verify results on the Apify Console, you must deploy the Actor with `apify push` and then run it on the platform.
+- Do **not** rely on checking the Apify Console to verify results from local runs — instead, inspect the local `storage/` directory or check the Actor's log output.
+
+## Standby Mode
+
+See [references/standby-mode.md](references/standby-mode.md) for complete standby mode documentation including readiness probe implementation for JavaScript/TypeScript and Python.
+
+## Project Structure
+
+```
+.actor/
+├── actor.json           # Actor config: name, version, env vars, runtime
+├── input_schema.json    # Input validation & Console form definition
+└── output_schema.json   # Output storage and display templates
+src/
+└── main.js/ts/py       # Actor entry point
+storage/                # Local-only storage (NOT synced to Apify Console)
+├── datasets/           # Output items (JSON objects)
+├── key_value_stores/   # Files, config, INPUT
+└── request_queues/     # Pending crawl requests
+Dockerfile              # Container image definition
+```
+
+## Actor Configuration
+
+See [references/actor-json.md](references/actor-json.md) for complete actor.json structure and configuration options.
+
+## Input Schema
+
+See [references/input-schema.md](references/input-schema.md) for input schema structure and examples.
+
+## Output Schema
+
+See [references/output-schema.md](references/output-schema.md) for output schema structure, examples, and template variables.
+
+## Dataset Schema
+
+See [references/dataset-schema.md](references/dataset-schema.md) for dataset schema structure, configuration, and display properties.
+
+## Key-Value Store Schema
+
+See [references/key-value-store-schema.md](references/key-value-store-schema.md) for key-value store schema structure, collections, and configuration.
+
+## Actor README
+
+**IMPORTANT:** Always generate a README.md as part of Actor development. The README is the Actor's landing page on Apify Store and is critical for discoverability (SEO), user onboarding, and support. Do not consider an Actor complete without a proper README.
+
+See [references/actor-readme.md](references/actor-readme.md) for the required structure, SEO best practices, and content guidelines. Also review these top Actors for best practices:
+
+- [Instagram Scraper](https://apify.com/apify/instagram-scraper)
+- [Google Maps Scraper](https://apify.com/compass/crawler-google-places)
+
+## Apify MCP Tools
+
+If MCP server is configured, use these tools for documentation:
+
+- `search-apify-docs` - Search documentation
+- `fetch-apify-docs` - Get full doc pages
+
+Otherwise, the MCP Server url: `https://mcp.apify.com/?tools=docs`.
+
+## Resources
+
+- [docs.apify.com/llms.txt](https://docs.apify.com/llms.txt) - Apify quick reference documentation
+- [docs.apify.com/llms-full.txt](https://docs.apify.com/llms-full.txt) - Apify complete documentation
+- [https://crawlee.dev/llms.txt](https://crawlee.dev/llms.txt) - Crawlee quick reference documentation
+- [https://crawlee.dev/llms-full.txt](https://crawlee.dev/llms-full.txt) - Crawlee complete documentation
+- [whitepaper.actor](https://raw.githubusercontent.com/apify/actor-whitepaper/refs/heads/master/README.md) - Complete Actor specification

skills/apify-actor-development/references/actor-json.md

@@ -0,0 +1,66 @@
+# 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.

skills/apify-actor-development/references/actor-readme.md

@@ -0,0 +1,93 @@
+# Actor README Guidelines
+
+The README is the Actor's landing page on Apify Store. It serves as SEO content, first impression, usage guide, and support resource. **Always generate a README.md when creating or deploying an Actor.**
+
+## Required Structure
+
+Write in Markdown. Use H2 (`##`) for main sections (these form the table of contents) and H3 (`###`) for subsections. Do not use H1 — the Actor name is automatically used as H1.
+
+### 1. What does [Actor name] do?
+
+- 1-2 sentences explaining what the Actor does and doesn't do
+- Include a link to the target website
+- Mention keywords like "API" (e.g., "Instagram API alternative")
+- Bold the most important terms
+
+### 2. Why use [Actor name]? / Why scrape [target site]?
+
+- Business use cases and benefits
+- List main features and capabilities
+- Highlight Apify platform advantages: scheduling, API access, integrations, proxy rotation, monitoring
+
+### 3. What data can [Actor name] extract?
+
+- Table showing main data fields the Actor outputs (field name, type, description)
+- Don't list every field — focus on the most useful and understandable ones
+
+### 4. How to scrape [target site]
+
+- Numbered step-by-step tutorial (Google may pick these up as rich snippets)
+- Include a link to blog tutorials if they exist
+
+### 5. How much will it cost to scrape [target site]?
+
+- Set pricing expectations based on the Actor's pricing model
+- For pay-per-result: mention free tier limits and what larger plans offer
+- For compute units: explain average data volume per dollar
+- Cost-related questions rank well in Google search
+
+### 6. Input
+
+- Reference the input tab: "See the input tab for full configuration options"
+- Explain any complex input fields or special formatting requirements
+- Screenshot of the input schema is optional but helpful
+
+### 7. Output
+
+- Include: "You can download the dataset in various formats such as JSON, HTML, CSV, or Excel"
+- Show a simplified JSON output example (2-3 items)
+- If output is complex, show separate examples for different data types
+
+### 8. Tips / Advanced options (if applicable)
+
+- How to limit compute unit usage
+- How to get more accurate results or improve speed
+
+### 9. FAQ, Disclaimers, and Support
+
+- Legal/scraping disclaimer (use this template and customize with the target site name):
+  > Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.
+- Common troubleshooting tips
+- Mention the Issues tab for feedback
+- Link to API tab for programmatic access
+- Use cases for the extracted data
+
+## SEO Best Practices
+
+- Include keywords naturally in H2/H3 headings (e.g., "How to scrape Instagram" not just "How to use")
+- Target "People Also Ask" style questions as H3 headings
+- Aim for at least 300 words total
+- Embed a YouTube video URL if available (renders automatically as a player)
+- Make images clickable with links
+
+## Tone
+
+- Match the README tone to the target audience skill level
+- For no-code users: use plain language, avoid code blocks early on
+- For developers: include technical details, code examples, and API references
+- Be clear about what technical knowledge is needed to use the Actor
+
+## Reference Actors
+
+Before writing a README, review these top Actors on the Apify Store for best practices on structure, tone, and content:
+
+- [Instagram Scraper](https://apify.com/apify/instagram-scraper)
+- [Google Maps Scraper](https://apify.com/compass/crawler-google-places)
+
+## Key Rules
+
+- Always write the README as part of Actor development — do not skip this step
+- The first 25% of the README is what most visitors read — put the most important info there
+- Use emojis sparingly as bullet points to break up text
+- Keep images compressed but good quality
+- Use [Carbon](https://github.com/carbon-app/carbon) for code snippet screenshots if needed