From 3e499c99305c0ca7c79c596594d9518a66e3a0fe Mon Sep 17 00:00:00 2001 From: Marcel Rebro Date: Wed, 30 Sep 2026 17:16:14 +0300 Subject: [PATCH 1/5] docs: list apify-integration-development in Agent Skills tables The apify-sdk-integration skill was removed from apify/agent-skills and superseded by apify-integration-development, which covers workflow automation apps, AI agent plugins, AI framework packages, and direct application clients (the old SDK integration content is now a reference file inside it). Update every skills table, example prompt, and skill-name mention in the docs to match the upstream repo. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016o2xgfqaGDV9V78sgxRkSe --- sources/_partials/_agent-plugin-limitations.mdx | 2 +- sources/_partials/_apify-plugin-skill-prompts.mdx | 4 ++-- sources/_partials/_apify-plugin-skills.mdx | 2 +- sources/platform/get-started/agent-onboarding.md | 2 +- .../platform/integrations/ai/claude/claude-code-cli.md | 8 ++++---- sources/platform/integrations/ai/cursor.md | 8 ++++---- sources/platform/integrations/ai/kimi-code-cli.md | 8 ++++---- sources/platform/integrations/ai/manus.md | 2 +- sources/platform/integrations/ai/openai/codex-app.md | 8 ++++---- sources/platform/integrations/ai/openai/codex-cli.md | 8 ++++---- sources/platform/integrations/ai/qoder/qoder.md | 2 +- sources/platform/integrations/ai/qoder/qwen.md | 4 ++-- 12 files changed, 29 insertions(+), 29 deletions(-) diff --git a/sources/_partials/_agent-plugin-limitations.mdx b/sources/_partials/_agent-plugin-limitations.mdx index 64512d199a..934578a07e 100644 --- a/sources/_partials/_agent-plugin-limitations.mdx +++ b/sources/_partials/_agent-plugin-limitations.mdx @@ -1,3 +1,3 @@ - Long-running Actors may time out during a single tool call. Reduce the scope or split the work across multiple prompts. - Each Actor run counts toward your Apify plan usage, on top of any usage your AI client bills separately. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. diff --git a/sources/_partials/_apify-plugin-skill-prompts.mdx b/sources/_partials/_apify-plugin-skill-prompts.mdx index e9723adacf..e8703abb26 100644 --- a/sources/_partials/_apify-plugin-skill-prompts.mdx +++ b/sources/_partials/_apify-plugin-skill-prompts.mdx @@ -6,6 +6,6 @@ To run `apify-actor-development`: > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -To run `apify-sdk-integration`: +To run `apify-integration-development`: -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. +> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. diff --git a/sources/_partials/_apify-plugin-skills.mdx b/sources/_partials/_apify-plugin-skills.mdx index 5015eca9cb..ec780c9ccc 100644 --- a/sources/_partials/_apify-plugin-skills.mdx +++ b/sources/_partials/_apify-plugin-skills.mdx @@ -4,4 +4,4 @@ | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | diff --git a/sources/platform/get-started/agent-onboarding.md b/sources/platform/get-started/agent-onboarding.md index 6597f897b6..df3ab16af9 100644 --- a/sources/platform/get-started/agent-onboarding.md +++ b/sources/platform/get-started/agent-onboarding.md @@ -283,7 +283,7 @@ npx skills add apify/agent-skills | `apify-actor-development` | Guided workflow for building and deploying custom Actors | | `apify-actorization` | Converts an existing project into an Apify Actor | | `apify-generate-output-schema` | Auto-generates output schemas from Actor source code | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | For the full list and details, see the [skills registry](https://skills.sh/apify/agent-skills). diff --git a/sources/platform/integrations/ai/claude/claude-code-cli.md b/sources/platform/integrations/ai/claude/claude-code-cli.md index a9a2c6ced9..80657aba25 100644 --- a/sources/platform/integrations/ai/claude/claude-code-cli.md +++ b/sources/platform/integrations/ai/claude/claude-code-cli.md @@ -100,7 +100,7 @@ The agent searches Apify Store, fetches the top Actor's details through `plugin: | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -112,9 +112,9 @@ _Actor development:_ > "Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL." -_SDK integration:_ +_Integration development:_ -> "Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON." +> "Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route." ## Troubleshooting @@ -142,7 +142,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Claude usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/cursor.md b/sources/platform/integrations/ai/cursor.md index 4bce15cfbd..44b80cc477 100644 --- a/sources/platform/integrations/ai/cursor.md +++ b/sources/platform/integrations/ai/cursor.md @@ -88,7 +88,7 @@ The agent searches Apify Store, fetches the top Actor's details through the Apif | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -100,9 +100,9 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_SDK integration:_ +_Integration development:_ -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. +> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. ## Troubleshooting @@ -128,7 +128,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Cursor usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/kimi-code-cli.md b/sources/platform/integrations/ai/kimi-code-cli.md index 9601aa483c..c543a8eed4 100644 --- a/sources/platform/integrations/ai/kimi-code-cli.md +++ b/sources/platform/integrations/ai/kimi-code-cli.md @@ -92,7 +92,7 @@ The router searches Apify Store, fetches the top Actor's details through the Api | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -104,9 +104,9 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_SDK integration:_ +_Integration development:_ -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. +> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. Each skill is also registered as a slash command, so you can start a workflow directly. The canonical form is `/skill:`, and the shorthand works when the name isn't taken by a built-in command: @@ -180,7 +180,7 @@ Install the Apify CLI with `npm install -g apify-cli` before using the `apify-ac - Kimi Code has no custom subagents, so the plugin ships a `using-apify` router skill instead of the `apify` agent used by the [Claude Code CLI plugin](/integrations/claude-code-cli). The five workflow skills are identical. - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Kimi usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/manus.md b/sources/platform/integrations/ai/manus.md index 21c91a03e3..b724c5f347 100644 --- a/sources/platform/integrations/ai/manus.md +++ b/sources/platform/integrations/ai/manus.md @@ -109,7 +109,7 @@ Available skills include: | `apify-actor-development` | Full Actor lifecycle: template selection, development, testing, and deployment | | `apify-actorization` | Converts existing projects into Apify Actors | | `apify-generate-output-schema` | Generates dataset and key-value store schemas from Actor source code | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | ### Import a skill from GitHub diff --git a/sources/platform/integrations/ai/openai/codex-app.md b/sources/platform/integrations/ai/openai/codex-app.md index ba6b571d03..e211830b60 100644 --- a/sources/platform/integrations/ai/openai/codex-app.md +++ b/sources/platform/integrations/ai/openai/codex-app.md @@ -89,7 +89,7 @@ Codex searches Apify Store, fetches the top Actor's details through the `apify` | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -101,9 +101,9 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_SDK integration:_ +_Integration development:_ -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. +> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. ## Troubleshooting @@ -129,7 +129,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Codex usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/openai/codex-cli.md b/sources/platform/integrations/ai/openai/codex-cli.md index 2a73465a47..cf790c7b3e 100644 --- a/sources/platform/integrations/ai/openai/codex-cli.md +++ b/sources/platform/integrations/ai/openai/codex-cli.md @@ -87,7 +87,7 @@ It then summarizes the Actor's inputs, pricing, and output - all without running | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | -| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | +| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -99,9 +99,9 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_SDK integration:_ +_Integration development:_ -> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. +> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. ## Troubleshooting @@ -127,7 +127,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Codex usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/qoder/qoder.md b/sources/platform/integrations/ai/qoder/qoder.md index 2d6e3fbe7d..f397dafea0 100644 --- a/sources/platform/integrations/ai/qoder/qoder.md +++ b/sources/platform/integrations/ai/qoder/qoder.md @@ -205,7 +205,7 @@ If the browser doesn't open automatically, copy the OAuth URL shown by the surfa - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/qoder/qwen.md b/sources/platform/integrations/ai/qoder/qwen.md index c16d9e0f4c..092d9f9036 100644 --- a/sources/platform/integrations/ai/qoder/qwen.md +++ b/sources/platform/integrations/ai/qoder/qwen.md @@ -177,7 +177,7 @@ If the sign-in page doesn't open or the server stays disconnected: - **Qwen Code:** copy the authorization URL from the terminal and open it manually. If sign-in still fails, add an `Authorization: Bearer ` header to the `apify` server in `~/.qwen/settings.json` under `mcpServers` - see the [Client configuration](/integrations/mcp#client-configuration) for the shape. - **QwenWork:** remove the connector and add it again. If OAuth still won't complete, re-add it with an `Authorization` header set to `Bearer `. -Get the token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). Setting `APIFY_TOKEN` in your shell doesn't authenticate the MCP server; it only covers the Apify CLI and `apify-client` used by the Actor development, actorization, and SDK integration skills, so run `apify login` once for those. +Get the token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). Setting `APIFY_TOKEN` in your shell doesn't authenticate the MCP server; it only covers the Apify CLI and `apify-client` used by the Actor development, actorization, and integration development skills, so run `apify login` once for those. ## Limitations @@ -185,7 +185,7 @@ Get the token from [Apify Console > Settings > Integrations](https://console.api - QwenWork doesn't host the bundled `apify` agent, so it has no automatic routing. Add the skills you need and let their trigger conditions apply, or name the task clearly. - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Qwen usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. ## Related integrations From 7b23ee1febd00e2f49f6d30b420e47ddd3739a75 Mon Sep 17 00:00:00 2001 From: Marcel Rebro Date: Wed, 30 Sep 2026 17:23:19 +0300 Subject: [PATCH 2/5] docs: keep the original SDK integration example prompts The apify-integration-development skill covers SDK integration as one of its four categories, so the existing prompt still routes correctly. Only the skill name needed changing, not the prompt itself. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016o2xgfqaGDV9V78sgxRkSe --- sources/_partials/_apify-plugin-skill-prompts.mdx | 2 +- sources/platform/integrations/ai/claude/claude-code-cli.md | 2 +- sources/platform/integrations/ai/cursor.md | 2 +- sources/platform/integrations/ai/kimi-code-cli.md | 2 +- sources/platform/integrations/ai/openai/codex-app.md | 2 +- sources/platform/integrations/ai/openai/codex-cli.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/sources/_partials/_apify-plugin-skill-prompts.mdx b/sources/_partials/_apify-plugin-skill-prompts.mdx index e8703abb26..d12146bb97 100644 --- a/sources/_partials/_apify-plugin-skill-prompts.mdx +++ b/sources/_partials/_apify-plugin-skill-prompts.mdx @@ -8,4 +8,4 @@ To run `apify-actor-development`: To run `apify-integration-development`: -> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. diff --git a/sources/platform/integrations/ai/claude/claude-code-cli.md b/sources/platform/integrations/ai/claude/claude-code-cli.md index 80657aba25..27ec77f5db 100644 --- a/sources/platform/integrations/ai/claude/claude-code-cli.md +++ b/sources/platform/integrations/ai/claude/claude-code-cli.md @@ -114,7 +114,7 @@ _Actor development:_ _Integration development:_ -> "Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route." +> "Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON." ## Troubleshooting diff --git a/sources/platform/integrations/ai/cursor.md b/sources/platform/integrations/ai/cursor.md index 44b80cc477..412698683f 100644 --- a/sources/platform/integrations/ai/cursor.md +++ b/sources/platform/integrations/ai/cursor.md @@ -102,7 +102,7 @@ _Actor development:_ _Integration development:_ -> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. ## Troubleshooting diff --git a/sources/platform/integrations/ai/kimi-code-cli.md b/sources/platform/integrations/ai/kimi-code-cli.md index c543a8eed4..138adc57e3 100644 --- a/sources/platform/integrations/ai/kimi-code-cli.md +++ b/sources/platform/integrations/ai/kimi-code-cli.md @@ -106,7 +106,7 @@ _Actor development:_ _Integration development:_ -> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. Each skill is also registered as a slash command, so you can start a workflow directly. The canonical form is `/skill:`, and the shorthand works when the name isn't taken by a built-in command: diff --git a/sources/platform/integrations/ai/openai/codex-app.md b/sources/platform/integrations/ai/openai/codex-app.md index e211830b60..25d009b9b9 100644 --- a/sources/platform/integrations/ai/openai/codex-app.md +++ b/sources/platform/integrations/ai/openai/codex-app.md @@ -103,7 +103,7 @@ _Actor development:_ _Integration development:_ -> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. ## Troubleshooting diff --git a/sources/platform/integrations/ai/openai/codex-cli.md b/sources/platform/integrations/ai/openai/codex-cli.md index cf790c7b3e..4a8de18326 100644 --- a/sources/platform/integrations/ai/openai/codex-cli.md +++ b/sources/platform/integrations/ai/openai/codex-cli.md @@ -101,7 +101,7 @@ _Actor development:_ _Integration development:_ -> Plan an official Apify integration for our app. It should run an Actor and return dataset items from a Node.js API route. +> Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. ## Troubleshooting From 9340699b63acd5d3eba0bce42d2aed1ebadc778a Mon Sep 17 00:00:00 2001 From: Marcel Rebro Date: Wed, 30 Sep 2026 17:29:07 +0300 Subject: [PATCH 3/5] docs: add apify-integration-development, restore apify-sdk-integration Revert the rename from the previous commits. Adding the new skill was the intended change; removing apify-sdk-integration is a separate question and shouldn't ride along in this PR. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016o2xgfqaGDV9V78sgxRkSe --- sources/_partials/_agent-plugin-limitations.mdx | 2 +- sources/_partials/_apify-plugin-skill-prompts.mdx | 2 +- sources/_partials/_apify-plugin-skills.mdx | 1 + sources/platform/get-started/agent-onboarding.md | 1 + sources/platform/integrations/ai/claude/claude-code-cli.md | 5 +++-- sources/platform/integrations/ai/cursor.md | 5 +++-- sources/platform/integrations/ai/kimi-code-cli.md | 5 +++-- sources/platform/integrations/ai/manus.md | 1 + sources/platform/integrations/ai/openai/codex-app.md | 5 +++-- sources/platform/integrations/ai/openai/codex-cli.md | 5 +++-- sources/platform/integrations/ai/qoder/qoder.md | 2 +- sources/platform/integrations/ai/qoder/qwen.md | 4 ++-- 12 files changed, 23 insertions(+), 15 deletions(-) diff --git a/sources/_partials/_agent-plugin-limitations.mdx b/sources/_partials/_agent-plugin-limitations.mdx index 934578a07e..64512d199a 100644 --- a/sources/_partials/_agent-plugin-limitations.mdx +++ b/sources/_partials/_agent-plugin-limitations.mdx @@ -1,3 +1,3 @@ - Long-running Actors may time out during a single tool call. Reduce the scope or split the work across multiple prompts. - Each Actor run counts toward your Apify plan usage, on top of any usage your AI client bills separately. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. diff --git a/sources/_partials/_apify-plugin-skill-prompts.mdx b/sources/_partials/_apify-plugin-skill-prompts.mdx index d12146bb97..e9723adacf 100644 --- a/sources/_partials/_apify-plugin-skill-prompts.mdx +++ b/sources/_partials/_apify-plugin-skill-prompts.mdx @@ -6,6 +6,6 @@ To run `apify-actor-development`: > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -To run `apify-integration-development`: +To run `apify-sdk-integration`: > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. diff --git a/sources/_partials/_apify-plugin-skills.mdx b/sources/_partials/_apify-plugin-skills.mdx index ec780c9ccc..c79299925f 100644 --- a/sources/_partials/_apify-plugin-skills.mdx +++ b/sources/_partials/_apify-plugin-skills.mdx @@ -4,4 +4,5 @@ | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | diff --git a/sources/platform/get-started/agent-onboarding.md b/sources/platform/get-started/agent-onboarding.md index df3ab16af9..f796c696d7 100644 --- a/sources/platform/get-started/agent-onboarding.md +++ b/sources/platform/get-started/agent-onboarding.md @@ -283,6 +283,7 @@ npx skills add apify/agent-skills | `apify-actor-development` | Guided workflow for building and deploying custom Actors | | `apify-actorization` | Converts an existing project into an Apify Actor | | `apify-generate-output-schema` | Auto-generates output schemas from Actor source code | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | For the full list and details, see the [skills registry](https://skills.sh/apify/agent-skills). diff --git a/sources/platform/integrations/ai/claude/claude-code-cli.md b/sources/platform/integrations/ai/claude/claude-code-cli.md index 27ec77f5db..edabdd0401 100644 --- a/sources/platform/integrations/ai/claude/claude-code-cli.md +++ b/sources/platform/integrations/ai/claude/claude-code-cli.md @@ -100,6 +100,7 @@ The agent searches Apify Store, fetches the top Actor's details through `plugin: | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -112,7 +113,7 @@ _Actor development:_ > "Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL." -_Integration development:_ +_SDK integration:_ > "Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON." @@ -142,7 +143,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Claude usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/cursor.md b/sources/platform/integrations/ai/cursor.md index 412698683f..ffc2514175 100644 --- a/sources/platform/integrations/ai/cursor.md +++ b/sources/platform/integrations/ai/cursor.md @@ -88,6 +88,7 @@ The agent searches Apify Store, fetches the top Actor's details through the Apif | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -100,7 +101,7 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_Integration development:_ +_SDK integration:_ > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. @@ -128,7 +129,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Cursor usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/kimi-code-cli.md b/sources/platform/integrations/ai/kimi-code-cli.md index 138adc57e3..5fc3615999 100644 --- a/sources/platform/integrations/ai/kimi-code-cli.md +++ b/sources/platform/integrations/ai/kimi-code-cli.md @@ -92,6 +92,7 @@ The router searches Apify Store, fetches the top Actor's details through the Api | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -104,7 +105,7 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_Integration development:_ +_SDK integration:_ > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. @@ -180,7 +181,7 @@ Install the Apify CLI with `npm install -g apify-cli` before using the `apify-ac - Kimi Code has no custom subagents, so the plugin ships a `using-apify` router skill instead of the `apify` agent used by the [Claude Code CLI plugin](/integrations/claude-code-cli). The five workflow skills are identical. - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Kimi usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/manus.md b/sources/platform/integrations/ai/manus.md index b724c5f347..a1eba7d5df 100644 --- a/sources/platform/integrations/ai/manus.md +++ b/sources/platform/integrations/ai/manus.md @@ -109,6 +109,7 @@ Available skills include: | `apify-actor-development` | Full Actor lifecycle: template selection, development, testing, and deployment | | `apify-actorization` | Converts existing projects into Apify Actors | | `apify-generate-output-schema` | Generates dataset and key-value store schemas from Actor source code | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | ### Import a skill from GitHub diff --git a/sources/platform/integrations/ai/openai/codex-app.md b/sources/platform/integrations/ai/openai/codex-app.md index 25d009b9b9..de2d903f5e 100644 --- a/sources/platform/integrations/ai/openai/codex-app.md +++ b/sources/platform/integrations/ai/openai/codex-app.md @@ -89,6 +89,7 @@ Codex searches Apify Store, fetches the top Actor's details through the `apify` | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -101,7 +102,7 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_Integration development:_ +_SDK integration:_ > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. @@ -129,7 +130,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Codex usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/openai/codex-cli.md b/sources/platform/integrations/ai/openai/codex-cli.md index 4a8de18326..69fe369c69 100644 --- a/sources/platform/integrations/ai/openai/codex-cli.md +++ b/sources/platform/integrations/ai/openai/codex-cli.md @@ -87,6 +87,7 @@ It then summarizes the Actor's inputs, pricing, and output - all without running | `apify-actor-development` | Full Actor lifecycle - template selection, development, local testing, and deployment with `apify push`. | | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | +| `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | | `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | Example prompts that route to specific skills: @@ -99,7 +100,7 @@ _Actor development:_ > Create an Apify Actor that accepts a `startUrl` and `maxPages` input, crawls the site, and stores each page title and URL. -_Integration development:_ +_SDK integration:_ > Add Apify to this project. The Node.js API route should run an Actor and return dataset items as JSON. @@ -127,7 +128,7 @@ export APIFY_TOKEN= - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Codex usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/qoder/qoder.md b/sources/platform/integrations/ai/qoder/qoder.md index f397dafea0..2d6e3fbe7d 100644 --- a/sources/platform/integrations/ai/qoder/qoder.md +++ b/sources/platform/integrations/ai/qoder/qoder.md @@ -205,7 +205,7 @@ If the browser doesn't open automatically, copy the OAuth URL shown by the surfa - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Qoder usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations diff --git a/sources/platform/integrations/ai/qoder/qwen.md b/sources/platform/integrations/ai/qoder/qwen.md index 092d9f9036..c16d9e0f4c 100644 --- a/sources/platform/integrations/ai/qoder/qwen.md +++ b/sources/platform/integrations/ai/qoder/qwen.md @@ -177,7 +177,7 @@ If the sign-in page doesn't open or the server stays disconnected: - **Qwen Code:** copy the authorization URL from the terminal and open it manually. If sign-in still fails, add an `Authorization: Bearer ` header to the `apify` server in `~/.qwen/settings.json` under `mcpServers` - see the [Client configuration](/integrations/mcp#client-configuration) for the shape. - **QwenWork:** remove the connector and add it again. If OAuth still won't complete, re-add it with an `Authorization` header set to `Bearer `. -Get the token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). Setting `APIFY_TOKEN` in your shell doesn't authenticate the MCP server; it only covers the Apify CLI and `apify-client` used by the Actor development, actorization, and integration development skills, so run `apify login` once for those. +Get the token from [Apify Console > Settings > Integrations](https://console.apify.com/settings/integrations?utm_source=qwen&utm_medium=integrations). Setting `APIFY_TOKEN` in your shell doesn't authenticate the MCP server; it only covers the Apify CLI and `apify-client` used by the Actor development, actorization, and SDK integration skills, so run `apify login` once for those. ## Limitations @@ -185,7 +185,7 @@ Get the token from [Apify Console > Settings > Integrations](https://console.api - QwenWork doesn't host the bundled `apify` agent, so it has no automatic routing. Add the skills you need and let their trigger conditions apply, or name the task clearly. - Long-running Actors may exceed the time a single tool call waits for completion. Reduce the scope or split the work across multiple prompts. - Each Actor run consumes Apify platform usage from your plan in addition to any Qwen usage. See [Billing](/account/billing) for details. -- Skills that edit files in your project (Actor development, actorization, integration development) make local changes - review them before deploying or committing. +- Skills that edit files in your project (Actor development, actorization, SDK integration) make local changes - review them before deploying or committing. ## Related integrations From d017279d9893fd15167935c2c3b369fcf327e4b0 Mon Sep 17 00:00:00 2001 From: Marcel Rebro Date: Wed, 30 Sep 2026 17:31:04 +0300 Subject: [PATCH 4/5] docs: reword the integration development skill description The skill guides you through building an integration, it doesn't build one for you. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016o2xgfqaGDV9V78sgxRkSe --- sources/_partials/_apify-plugin-skills.mdx | 2 +- sources/platform/get-started/agent-onboarding.md | 2 +- sources/platform/integrations/ai/claude/claude-code-cli.md | 2 +- sources/platform/integrations/ai/cursor.md | 2 +- sources/platform/integrations/ai/kimi-code-cli.md | 2 +- sources/platform/integrations/ai/manus.md | 2 +- sources/platform/integrations/ai/openai/codex-app.md | 2 +- sources/platform/integrations/ai/openai/codex-cli.md | 2 +- 8 files changed, 8 insertions(+), 8 deletions(-) diff --git a/sources/_partials/_apify-plugin-skills.mdx b/sources/_partials/_apify-plugin-skills.mdx index c79299925f..1b3b3592e6 100644 --- a/sources/_partials/_apify-plugin-skills.mdx +++ b/sources/_partials/_apify-plugin-skills.mdx @@ -5,4 +5,4 @@ | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | diff --git a/sources/platform/get-started/agent-onboarding.md b/sources/platform/get-started/agent-onboarding.md index f796c696d7..f6a90050b1 100644 --- a/sources/platform/get-started/agent-onboarding.md +++ b/sources/platform/get-started/agent-onboarding.md @@ -284,7 +284,7 @@ npx skills add apify/agent-skills | `apify-actorization` | Converts an existing project into an Apify Actor | | `apify-generate-output-schema` | Auto-generates output schemas from Actor source code | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients | For the full list and details, see the [skills registry](https://skills.sh/apify/agent-skills). diff --git a/sources/platform/integrations/ai/claude/claude-code-cli.md b/sources/platform/integrations/ai/claude/claude-code-cli.md index edabdd0401..c01146bed9 100644 --- a/sources/platform/integrations/ai/claude/claude-code-cli.md +++ b/sources/platform/integrations/ai/claude/claude-code-cli.md @@ -101,7 +101,7 @@ The agent searches Apify Store, fetches the top Actor's details through `plugin: | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/cursor.md b/sources/platform/integrations/ai/cursor.md index ffc2514175..e484b08a93 100644 --- a/sources/platform/integrations/ai/cursor.md +++ b/sources/platform/integrations/ai/cursor.md @@ -89,7 +89,7 @@ The agent searches Apify Store, fetches the top Actor's details through the Apif | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/kimi-code-cli.md b/sources/platform/integrations/ai/kimi-code-cli.md index 5fc3615999..5b40902262 100644 --- a/sources/platform/integrations/ai/kimi-code-cli.md +++ b/sources/platform/integrations/ai/kimi-code-cli.md @@ -93,7 +93,7 @@ The router searches Apify Store, fetches the top Actor's details through the Api | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/manus.md b/sources/platform/integrations/ai/manus.md index a1eba7d5df..7bba828408 100644 --- a/sources/platform/integrations/ai/manus.md +++ b/sources/platform/integrations/ai/manus.md @@ -110,7 +110,7 @@ Available skills include: | `apify-actorization` | Converts existing projects into Apify Actors | | `apify-generate-output-schema` | Generates dataset and key-value store schemas from Actor source code | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients | ### Import a skill from GitHub diff --git a/sources/platform/integrations/ai/openai/codex-app.md b/sources/platform/integrations/ai/openai/codex-app.md index de2d903f5e..6eccdf4d65 100644 --- a/sources/platform/integrations/ai/openai/codex-app.md +++ b/sources/platform/integrations/ai/openai/codex-app.md @@ -90,7 +90,7 @@ Codex searches Apify Store, fetches the top Actor's details through the `apify` | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/openai/codex-cli.md b/sources/platform/integrations/ai/openai/codex-cli.md index 69fe369c69..a1bae0b3a7 100644 --- a/sources/platform/integrations/ai/openai/codex-cli.md +++ b/sources/platform/integrations/ai/openai/codex-cli.md @@ -88,7 +88,7 @@ It then summarizes the Actor's inputs, pricing, and output - all without running | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Builds official Apify integrations - workflow automation apps, AI agent plugins, AI framework packages, and direct application clients. | +| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: From 69ebbf9c2231936c749f950a29cf73e4b8bb813a Mon Sep 17 00:00:00 2001 From: Marcel Rebro Date: Wed, 30 Sep 2026 17:48:03 +0300 Subject: [PATCH 5/5] docs: limit the new skill row to the repo-level skill lists The Bundled skills tables on the plugin pages describe what each editor plugin ships, not the agent-skills repo. Every plugin repo (Cursor, Codex, Claude Code, Kimi Code, GitHub Copilot, Qoder) still bundles the same five skills including apify-sdk-integration, and none bundles apify-integration-development, so the row doesn't belong there. Keep it on agent-onboarding.md and manus.md, which document the repo itself via npx skills add and GitHub skill import. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_016o2xgfqaGDV9V78sgxRkSe --- sources/_partials/_apify-plugin-skills.mdx | 1 - sources/platform/integrations/ai/claude/claude-code-cli.md | 1 - sources/platform/integrations/ai/cursor.md | 1 - sources/platform/integrations/ai/kimi-code-cli.md | 1 - sources/platform/integrations/ai/openai/codex-app.md | 1 - sources/platform/integrations/ai/openai/codex-cli.md | 1 - 6 files changed, 6 deletions(-) diff --git a/sources/_partials/_apify-plugin-skills.mdx b/sources/_partials/_apify-plugin-skills.mdx index 1b3b3592e6..5015eca9cb 100644 --- a/sources/_partials/_apify-plugin-skills.mdx +++ b/sources/_partials/_apify-plugin-skills.mdx @@ -5,4 +5,3 @@ | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | diff --git a/sources/platform/integrations/ai/claude/claude-code-cli.md b/sources/platform/integrations/ai/claude/claude-code-cli.md index c01146bed9..a9a2c6ced9 100644 --- a/sources/platform/integrations/ai/claude/claude-code-cli.md +++ b/sources/platform/integrations/ai/claude/claude-code-cli.md @@ -101,7 +101,6 @@ The agent searches Apify Store, fetches the top Actor's details through `plugin: | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/cursor.md b/sources/platform/integrations/ai/cursor.md index e484b08a93..4bce15cfbd 100644 --- a/sources/platform/integrations/ai/cursor.md +++ b/sources/platform/integrations/ai/cursor.md @@ -89,7 +89,6 @@ The agent searches Apify Store, fetches the top Actor's details through the Apif | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/kimi-code-cli.md b/sources/platform/integrations/ai/kimi-code-cli.md index 5b40902262..9601aa483c 100644 --- a/sources/platform/integrations/ai/kimi-code-cli.md +++ b/sources/platform/integrations/ai/kimi-code-cli.md @@ -93,7 +93,6 @@ The router searches Apify Store, fetches the top Actor's details through the Api | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/openai/codex-app.md b/sources/platform/integrations/ai/openai/codex-app.md index 6eccdf4d65..ba6b571d03 100644 --- a/sources/platform/integrations/ai/openai/codex-app.md +++ b/sources/platform/integrations/ai/openai/codex-app.md @@ -90,7 +90,6 @@ Codex searches Apify Store, fetches the top Actor's details through the `apify` | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: diff --git a/sources/platform/integrations/ai/openai/codex-cli.md b/sources/platform/integrations/ai/openai/codex-cli.md index a1bae0b3a7..2a73465a47 100644 --- a/sources/platform/integrations/ai/openai/codex-cli.md +++ b/sources/platform/integrations/ai/openai/codex-cli.md @@ -88,7 +88,6 @@ It then summarizes the Actor's inputs, pricing, and output - all without running | `apify-actorization` | Converts existing JavaScript, TypeScript, Python, or CLI projects into Apify Actors. | | `apify-generate-output-schema` | Generates dataset and key-value store schemas for existing Actors. | | `apify-sdk-integration` | Integrates Actor execution into applications using the `apify-client` package. | -| `apify-integration-development` | Guides you through building an Apify integration - workflow automation apps, AI agent plugins, AI framework packages, or direct application clients. | Example prompts that route to specific skills: