메뉴
Use when a project needs Apify-powered web, social, SERP, marketplace, or competitor research with credential, compliance, and dataset controls.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CleanExpo/skills-library --skill apify-research-connector명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Dispatch the eight operational roles against a task, each grounded in the vault before it reads any code, with a live view of what is running. Use for work that wants several independent lenses at once — map, plan, build, verify, review, security, CI, release — rather than one agent doing everything.
Thin wrapper around the Pi-CEO Hour-1 provisioner. Given a client slug + email, invokes `swarm/inbox/provisioner.py` to spin up the full Linear project + Supabase portal_content + ContextBot Telegram intake bot + welcome email + Phill ping. Use when the user says "onboard {client}", "spin up portal for", "new client setup", or right after `stripe-milestone-invoice` confirms a deposit cleared.
PM-Core — the first autonomous execution agent. Claims the highest-priority agent-ready ticket from the Unite-Group Linear board, clones the repo, implements the fix on a feature branch, runs CI, and opens a PR. Model: claude-sonnet-5 (senior agent tier). Trigger: /pm-core [ticket-id] or autonomous via Hermes cron.
SKILL.md 표시 중
| name | apify-research-connector |
| description | Use when a project needs Apify-powered web, social, SERP, marketplace, or competitor research with credential, compliance, and dataset controls. |
Use Apify as a credential-gated data adapter for research, not as a bypass for platform rules. Keep credentials in ignored env stores and keep outputs provenance-rich.
Operate only from the current project folder. Read local docs, .env.example,
package scripts, existing Apify modules, and Brain-1 wiki pages. If project
identity or credential ownership is unclear, stop with a blocked report.
Check presence without printing values:
git check-ignore -v .env.local .env 2>/dev/null || true
awk -F= '/^APIFY_(API_TOKEN|API_KEY)=/{print $1"=present"}' .env.local 2>/dev/null || true
vercel env ls --scope unite-group 2>/dev/null | awk '/APIFY|apify/{print $1, $2, $3, $4, $5}'
Preferred variable is APIFY_API_TOKEN. Treat APIFY_API_KEY as legacy or
project-specific until verified. Never echo, log, screenshot, commit, or paste
token values.
Refresh current Apify docs before adding or changing integration behavior:
https://docs.apify.com/apihttps://docs.apify.com/academy/api/run-actor-and-retrieve-data-via-apihttps://docs.apify.com/api/client/jshttps://docs.apify.com/api/v2/default-datasethttps://apify.com/apimode: official_actor, custom_actor, licensed_vendor,
manual_review, or blocked..call() or sync endpoints; for longer
runs, use async run plus polling or webhooks.OUTPUT.Low-cost auth check:
node -e "const fs=require('fs'); const key='APIFY_'+'API_TOKEN'; const s=fs.readFileSync('.env.local','utf8'); const m=s.match(new RegExp('^'+key+'=(.*)$','m')); process.exit(m?0:2)"
Live API identity check without printing token:
TOKEN=$(node -e "const fs=require('fs'); const key='APIFY_'+'API_TOKEN'; const s=fs.readFileSync('.env.local','utf8'); const m=s.match(new RegExp('^'+key+'=(.*)$','m')); if(!m) process.exit(2); let v=m[1].trim().replace(/^['\\\"]|['\\\"]$/g,''); process.stdout.write(v)")
curl -fsS -H "Authorization: Bearer $TOKEN" https://api.apify.com/v2/users/me \
| jq '{username: .data.username, idPresent: (.data.id != null)}'
Do not run paid actors until the expected cost and approval gate are explicit.
Return: