AgentSkillsCN

Cloudflare Workers Builds

当用户询问“部署状态”、“构建失败”、“构建日志”、“部署历史”、“工作者部署”、“检查构建”、“部署成功”、“构建错误”、“CI/CD”、“验证部署”时，或需要监控Cloudflare Workers构建和部署时，应使用此技能。

SKILL.md
--- frontmatter
name: Cloudflare Workers Builds
description: This skill should be used when the user asks about "deploy status", "build failed", "build logs", "deployment history", "worker deployment", "check build", "deployment succeeded", "build error", "CI/CD", "verify deployment", or needs to monitor Cloudflare Workers builds and deployments.
version: 1.0.0

Cloudflare Workers Builds

Monitor and analyze Cloudflare Workers builds using the Workers Builds MCP server.

Available Tools

ToolPurpose
workers_builds_set_active_workerSet the Worker ID for subsequent operations
workers_builds_list_buildsList recent builds for the active Worker
workers_builds_get_buildGet details for a specific build (by UUID)
workers_builds_get_build_logsFetch logs for a specific build

Deployment Verification Workflow

After deploying a Worker, verify success:

  1. •

    Set active Worker

    code
    workers_builds_set_active_worker with Worker ID
  2. •

    List recent builds

    code
    workers_builds_list_builds

    Check the latest build status (succeeded/failed)

  3. •

    Get build details (if needed)

    code
    workers_builds_get_build with build UUID

    Review build and deploy commands

  4. •

    Check build logs (for failures or debugging)

    code
    workers_builds_get_build_logs with build UUID

    Analyze errors or warnings

Post-Deployment Checklist

After verifying the build succeeded:

  1. •Check build logs for warnings
  2. •Use observability tools to monitor initial traffic
  3. •Verify expected behavior with test requests

Common Use Cases

ScenarioTools to Use
Check if deployment succeededlist_builds → check status
Debug failed deploymentlist_builds → get_build_logs
Review deployment historylist_builds
Compare build configurationsget_build for multiple UUIDs

Tips

  • •Build UUIDs are returned by list_builds
  • •Failed builds will have error details in logs
  • •Set the active worker once per session
  • •Combine with observability tools to verify runtime behavior