跳到正文
cccskills
免费在 GitHub 公开

apify-install-auth

Set up the Apify tools needed for a project: the client for calling Actors, the SDK for building them, Crawlee for crawling, or the CLI for deployment. Configure an API token and verify that the connection works.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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".

实测评分 未实测

查看安装方法

适用场景

  • Starting a new Apify project
  • Choosing packages to call or build Actors
  • Configuring an Apify API token
  • Checking client or CLI authentication

包含的文件(3)

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

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

中文简介正在准备中。当前显示英语简介。

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

中文简介正在准备中。当前显示英语简介。

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

中文简介正在准备中。当前显示英语简介。

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

中文简介正在准备中。当前显示英语简介。

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

中文简介正在准备中。当前显示英语简介。

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

中文简介正在准备中。当前显示英语简介。

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace28672026年10月23日 更新

查看 jeremylongshore 的全部技能

报告此技能的问题