本文へ移動
cccskills
無料GitHub で公開

apify-install-auth

Install and configure Apify SDK, CLI, and API client authentication. Use when setting up a new Apify project, configuring API tokens, or initializing apify-client / Apify SDK in your codebase. Trigger with "install apify", "setup apify", "apify auth", "configure apify token".

インストール方法を見る

含まれるファイル(3)

  • SKILL.md5.0 KB
  • references/authentication.md2.0 KB
  • references/examples.md1.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Apify Install & Auth

Overview

Set up the Apify ecosystem: the apify-client JS library (for calling Actors remotely), the apify SDK (for building Actors), the Apify CLI (for deploying), and Crawlee (for crawling). Each package serves a different purpose — install only what the task needs, then wire up a single API token.

Package Map

PackagenpmPurpose
apify-clientnpm i apify-clientCall Actors, manage datasets/KV stores from external apps
apifynpm i apifyBuild Actors (includes Actor.init(), Actor.pushData())
crawleenpm i crawleeCrawler framework (Cheerio, Playwright, Puppeteer crawlers)
apify-clinpm i -g apify-cliCLI for apify login, apify run, apify push

Prerequisites

  • Node.js 18+ (required by SDK v3+)
  • Apify account at https://console.apify.com
  • API token from Settings > Integrations in Apify Console

Instructions

Step 1: Install Packages

# For CALLING existing Actors from your app:
npm install apify-client

# For BUILDING your own Actors:
npm install apify crawlee

# For CLI deployment:
npm install -g apify-cli

Step 2: Configure Authentication

Pick one. Read any existing .env first so you do not clobber it, then Write the token in.

# Option A: Environment variable (recommended for apps)
export APIFY_TOKEN="apify_api_YOUR_TOKEN_HERE"

# Option B: .env file (add .env to .gitignore)
echo 'APIFY_TOKEN=apify_api_YOUR_TOKEN_HERE' >> .env

# Option C: CLI login (for interactive development)
apify login
# Paste your token when prompted

The APIFY_TOKEN env var is auto-detected by both apify-client and the apify SDK. For every place a token can be supplied (constructor option, header, precedence) plus the full platform env-var list, see authentication reference.

Step 3: Verify Connection

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });

// List your Actors to confirm auth works
const { items } = await client.actors().list();
console.log(`Authenticated. You have ${items.length} Actors.`);

Step 4: Verify CLI (if installed)

apify login --token YOUR_TOKEN
apify info  # Shows your account info

Output

A working, authenticated Apify setup:

  • The needed packages installed in node_modules (verify with npm ls apify-client).
  • APIFY_TOKEN available to the process — via a Write to .env, an exported shell var, or apify login credentials in ~/.apify/auth.json.
  • The Step 3 snippet printing Authenticated. You have N Actors. — proof the token reaches the API.
  • apify info showing your account (only when the CLI was installed in Step 1).

If the verify snippet throws instead of printing the count, jump to Error Handling below.

Error Handling

ErrorCauseSolution
401 UnauthorizedInvalid or expired tokenRegenerate token in Console > Settings > Integrations
Cannot find module 'apify-client'Package not installednpm install apify-client
APIFY_TOKEN is not setMissing env varExport APIFY_TOKEN or pass token to constructor
apify: command not foundCLI not installed globallynpm install -g apify-cli

Examples

The essential singleton-client skeleton:

// src/apify/client.ts
import { ApifyClient } from 'apify-client';
import 'dotenv/config';

let client: ApifyClient | null = null;

export function getClient(): ApifyClient {
  if (!client) {
    if (!process.env.APIFY_TOKEN) {
      throw new Error('APIFY_TOKEN environment variable is required');
    }
    client = new ApifyClient({ token: process.env.APIFY_TOKEN });
  }
  return client;
}

For the full worked set — the .env.example template, the verify snippet, and CLI verification — see worked examples.

Resources

Next Steps

With the client authenticated, proceed to apify-hello-world to make your first Actor call and push results to a dataset. If you are building your own Actor instead of calling one, the apify SDK and Crawlee installed above are your starting point — deploy with apify push.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with "test the Abridge integration".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

Triage Abridge recording, note-review, Epic handoff, and access failures from observed evidence without inventing vendor error codes. Use when an Abridge clinical workflow is degraded. Trigger with "diagnose this Abridge issue".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with "map the Abridge note workflow".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with "verify the Abridge Epic handoff".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

Evaluate Abridge adoption, workflow value, and avoidable operational friction without inventing prices or vendor billing meters. Use when reviewing an Abridge rollout or renewal. Trigger with "analyze Abridge value".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

Produce a PHI-minimized Abridge support bundle with provenance, redaction, and protected escalation boundaries. Use when support needs reproducible evidence for an Abridge issue. Trigger with "build an Abridge debug bundle".

日本語の概要は準備中です。原文の説明を表示しています。

jeremylongshore/tons-of-skills-marketplace2,8322026年10月13日 更新

jeremylongshore のスキルをすべて見る

このスキルの問題を報告する