菜单
Use when deploying the ETL application to GCP Cloud Run. Triggers on "deploy", "push to production", "release to cloud", "update cloud run", or "ship the ETL". Handles Docker image builds via Cloud Build and Cloud Run Job updates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Build Slack bots with Bolt for JavaScript on Bun. Use this skill whenever the user wants to add a Slack command, event handler, assistant, modal, interactive component, or any Slack integration. Also triggers on "add a slash command", "Slack notification", "Slack bot", "app_mention", "Assistant API", "Slack event", "weekly digest", "scheduled message", or "reaction handler". Covers both real-time handlers (commands, events, modals) and scheduled/proactive messages.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Run compliance-discovery sources against the configured nonprofit entity and report findings. Use this skill when the user asks "are we compliant?", "check our IRS status", "verify our tax-exempt status", "run a compliance check", "is our 501(c)(3) still active?", or when they want to refresh the compliance picture before a board meeting, audit, or grant application. Phase 3 covers IRS TEOS/BMF, public CA AG Registry Search Tool/detail pages, public CA SOS bizfile checks, public CA FTB Entity Status Letter checks, public CDTFA permit verification, and user-assisted authenticated CA portal checks.
Capture the nonprofit's identifying information for compliance discovery and persist it to Secret Manager (entity IDs) and BigQuery (entity attributes). Use this skill when the user is setting up the compliance toolkit for a new nonprofit, when they say "onboard us", "set up compliance", "register our nonprofit details", "configure the compliance module", or when running `compliance-discover` reports that no entity is configured. Also use when the user wants to update the legal name, EIN, fiscal year end, or mailing address on file.
Summarize the configured nonprofit's stored compliance state without running network discovery. Use this skill when the user asks for current compliance status, the latest stored findings, or whether prior discovery found anything that needs attention.
Bulk data enrichment. Adds web-sourced fields (CEO names, funding, contact info) to lists of companies, people, or products. Use for enriching CSV files or inline data. Supports multi-turn: pass --previous-interaction-id from a prior research or enrichment to carry context forward.
| name | deploying-etl |
| description | Use when deploying the ETL application to GCP Cloud Run. Triggers on "deploy", "push to production", "release to cloud", "update cloud run", or "ship the ETL". Handles Docker image builds via Cloud Build and Cloud Run Job updates. |
Deploy the donations ETL application to Google Cloud Platform using the project's deployment script.
Before deploying, verify:
.env file must exist with PROJECT_ID configured./infra/provision.sh)./scripts/deploy.sh
This will:
.env via dotenvx./scripts/deploy.sh --dry-run
Shows what would happen without making changes. Use this to verify configuration before actual deployment.
After deployment, help the user verify:
# Run the job manually
gcloud run jobs execute donations-etl --region us-central1
# Check job execution status
gcloud run jobs executions list --job donations-etl --region us-central1
# View logs from latest execution
gcloud run jobs executions logs <EXECUTION_ID> --region us-central1
| Error | Solution |
|---|---|
| "Not authenticated with gcloud" | Run gcloud auth login |
| ".env file not found" | Copy .env.example to .env and configure |
| "Cloud Run Job not found" | Run ./infra/provision.sh first |
| "Project not found" | Verify PROJECT_ID in .env matches actual GCP project |
The script reads from .env:
| Variable | Required | Default | Description |
|---|---|---|---|
PROJECT_ID | Yes | - | GCP project ID |
REGION | No | us-central1 | GCP region |
AR_REPO | No | donations-etl | Artifact Registry repository |
IMAGE_NAME | No | etl | Docker image name |
JOB_NAME | No | donations-etl | Cloud Run Job name |