인프라·DevOps 스킬

Configure EAS Update to deliver compatible JavaScript, styling, and assets to installed apps without a new native build. Guides publishing to selected channels, testing release behavior, and investigating updates that fail to appear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up remote updates for an Expo app
• Publish JavaScript fixes to preview or staging
• Investigate updates missing from TestFlight or production builds

Create and edit EAS Workflows YAML files to automate Expo app builds and deployment. The skill consults current specifications, checks job dependencies and expressions, and validates configuration through EAS CLI against the linked project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating Expo app builds and deployment
• Creating or editing EAS workflow YAML files
• Checking job dependencies and conditional expressions

Build and submit iOS and Android apps through EAS, an app delivery service. Covers signing, version numbers, store listing information, automated release workflows, and checking submission progress for Expo, React Native, and existing native apps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Distributing an iOS beta through TestFlight
• Preparing an App Store or Google Play submission
• Configuring signing and build version numbers

Prepare a release for review by running quality checks, checking narrow screen layouts, and detecting emoji. Update README version details and draft an accurate changelog from commits, then present verification results and a proposed version for approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run quality checks before a release
• Check layouts at narrow screen widths
• Update README version details and changelog

Prepare and publish codexhost releases through GitHub Actions, including stable and preview versions. Draft release notes, check automated build results, distinguish npm distribution tags from GitHub release status, and verify the published packages and installers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Publishing a stable release
• Publishing a preview without update notifications
• Drafting and reviewing release notes

Connect an agent to Vexa through MCP, a connection interface for agent tools. Find the API key source, choose the hosted or self-hosted URL, and check whether connection failures come from authentication or an unavailable server.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Connect an agent to Vexa for the first time
• Investigate a 401 authentication error
• Configure a self-hosted Vexa connection URL

Prepare AssemblyAI diagnostic evidence for incident triage and support requests. Extract approved metadata such as status changes, timestamps, SDK versions, and error codes, while excluding credentials, signed URLs, audio, transcript text, prompts, and customer content.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing evidence for an AssemblyAI support request
• Investigating status changes and errors without sharing speech content
• Reviewing diagnostic files and setting a deletion date

Review whether an Attio integration is ready for production using code and operational evidence. Check authentication, permissions, retries, webhooks, monitoring, and rollback, then produce a GO or NO-GO decision with blockers and named approvers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review an Attio integration before production launch
• Check webhook signatures and duplicate-event handling
• Document release blockers, accepted risks, and approvers

Plan a staged release for an application that uses Attio’s REST API. The workflow checks configuration and schemas, runs contract tests and a read-only smoke check, verifies a canary write, monitors rollout signals, and prepares rollback evidence.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a staged release of an Attio-backed service
• Checking schemas and configuration before enabling writes
• Verifying a reversible canary write and readback

Build recurring database archival pipelines that move historical records into archive tables or cloud storage. Define retention criteria, verify batches before deleting source records, track archived files, and prepare retrieval procedures for later access.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Move old logs and orders out of primary tables
• Archive records according to retention rules
• Store historical data in cloud storage

Analyze AssemblyAI spending using measured workload usage and dated pricing. Review audio duration, models, features, retries, streaming sessions, and LLM Gateway usage to identify waste and define budgets, anomaly alerts, and spending limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Forecasting budgets from audio duration and model usage
• Investigating unexpected increases in AssemblyAI spending
• Reducing duplicate submissions and abandoned streaming sessions

Deploy AssemblyAI processing workers, temporary streaming token services, and authenticated callback receivers. Configure durable queues, duplicate handling, shutdown behavior, and rollback controls, then check the deployment with synthetic audio before broader use.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy AssemblyAI workers to cloud infrastructure
• Build authenticated receivers for processing callbacks
• Deploy Streaming v3 token services

Add monitoring to Apollo.io integrations by collecting request counts, latency, rate limits, and credit use. It also sets up structured logs with sensitive fields redacted, tracing, and alerts for common API health issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monitor API errors and response times
• Track rate limits and enrichment credits
• Redact personal data from integration logs

Package an AppFolio integration service as a non-root Docker container and deploy it gradually to cloud infrastructure. Keep credentials in a secret manager, check local liveness and provider readiness separately, and retain a rollback target if release checks fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Deploy an AppFolio integration service
• Check service health and AppFolio API readiness
• Roll back a release when readiness checks fail

Check an Apollo.io integration before production by reviewing API key handling, retries, timeouts, logging, personal data redaction, and credit controls. The checklist reports passed and failed checks with a readiness score, helping teams decide whether deployment should proceed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking Apollo credentials before launch
• Reviewing retries, rate limits, and timeouts
• Auditing logging and personal data redaction

Set up separate Apollo.io configurations for development, staging, and production. Define API keys, request limits, feature access, and credit budgets, then add environment-aware clients, Kubernetes secrets, and checks for the active environment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Separate development, staging, and production configurations
• Enable bulk enrichment in staging before production
• Manage API keys with Kubernetes secrets

Review AppFolio integrations before production release, covering credentials, tenant data, duplicate prevention, monitoring, and recovery. Produce a release decision record backed by verified checks, with unresolved controls identified as reasons to block deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess readiness for production release
• Review payment and work-order duplicate prevention
• Verify monitoring and alert routing

Prepare a redacted diagnostic bundle for AppFolio API support investigations. It records endpoint status and latency, rate limit headers, dependency versions, and log file metadata while excluding credentials, response bodies, tenant records, and financial data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing evidence for an AppFolio sync incident
• Checking API connectivity and response times
• Reviewing rate limit and dependency information

Set up GitHub Actions checks for AppFolio integrations, using simulated API responses for pull requests and a restricted sandbox check after main updates. Track request usage and block releases when required checks fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up automated checks for AppFolio integrations
• Test work order mappings with simulated responses
• Verify sandbox API responses after main updates

Package Apple Notes automation written with JXA or osascript as a local macOS service. Choose a launchd agent for scheduled work, or use Automator and Shortcuts for user-triggered tasks, then check permissions, run a scoped smoke test, and retain a rollback path.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run a Notes script on a schedule with launchd
• Trigger Notes automation from Apple Shortcuts
• Check macOS permissions before enabling writes

Set up separate Claude API configurations for development, staging, and production. The skill maps each environment to its own workspace and credentials, applies model and spend limits, and guides isolation checks and a reviewed canary before promotion.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Separating Claude API keys by environment
• Setting model and spend policies per environment
• Checking isolation before production promotion

Analyze Apify spending from Actor run history and tune memory, crawl duration, and proxy traffic. Produce cost comparisons and monthly reports, with an optional budget guard that stops runs once spending exceeds a set limit.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a rise in Apify spending
• Comparing memory settings and execution costs
• Reducing residential proxy traffic

Prepare an Apify Actor, a program running on the platform, for production. Check configuration and builds, then set up scheduled runs, event notifications, health monitoring, rollback, and a spending limit that stops over-budget runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking an Actor before its first production deployment
• Setting up scheduled runs and completion notifications
• Monitoring failures, timeouts, and running costs

Plan capacity and load tests for services using Claude API. Estimate request and token demand, measure latency and costs, and evaluate queues, shared rate limiting, and scaling within the organization's API limits.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Estimating capacity and costs for traffic spikes
• Measuring latency and errors in sandbox load tests
• Coordinating API limits across multiple service instances