重要前提
安装AI Skills的关键前提是:必须科学上网,且开启TUN模式,这一点至关重要,直接决定安装能否顺利完成,在此郑重提醒三遍:科学上网,科学上网,科学上网。查看完整安装教程 →
cloudflare by heyvhuang/ship-faster
npx skills add https://github.com/heyvhuang/ship-faster --skill cloudflare管理 Cloudflare 服务:Workers、KV、R2、D1、Hyperdrive、可观测性、构建和审计日志。
MCP 是可选的。 此技能可与 MCP(自动)、Wrangler CLI 或仪表板配合使用。有关执行选项,请参阅 BACKENDS.md。
| 层级 | 用途 | 范围 | 风险控制 |
|---|---|---|---|
| 诊断 | 只读/查询/故障排除 | 可观测性、构建、审计 | 默认入口,无写入操作 |
| 变更 | 创建/修改/删除资源 | KV、R2、D1、Hyperdrive | 需要确认 + 验证 |
| 超级管理员 | 最高权限 | 全部 + 容器沙箱 | 仅在隔离/测试环境中使用 |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
1. 计划:先读取当前状态(列出/获取)
2. 确认:输出精确的变更(名称/ID/影响),等待用户确认
3. 执行:创建/删除/更新
4. 验证:审计日志 + 可观测性确认没有新错误
| 类别 | 可执行的操作 |
|---|---|
| 可观测性 | 查询 worker 日志/指标,发现字段,探索值 |
| 构建 | 列出构建历史记录,获取构建详情,查看构建日志 |
| 浏览器 | 获取页面 HTML,转换为 markdown,截图 |
| 审计 | 按时间范围拉取变更历史 |
| Workers | 列出 workers,获取详情,查看源代码 |
| 资源 | 操作 |
|---|---|
| KV | 列出,获取,创建 ⚠️,更新 ⚠️,删除 ⚠️ |
| R2 | 列出,获取,创建 ⚠️,删除 ⚠️ |
| D1 | 列出,获取,查询,创建 ⚠️,删除 ⚠️ |
| Hyperdrive | 列出,获取,创建 ⚠️,编辑 ⚠️,删除 ⚠️ |
⚠️ = 需要确认
用于隔离任务的临时容器(约 10 分钟生命周期):
1. 明确症状 → worker 名称 / 时间范围 / 错误类型
2. 查询可观测性以拉取日志/指标
3. 如果与构建相关 → 获取构建日志
4. 如果与页面相关 → 截图以复现
5. 追踪变更 → 拉取审计日志
6. 总结:根本原因 + 证据 + 修复建议
1. 列出账户 → 设置活动账户
2. 列出资源(KV / R2 / D1)
3. 计划变更 → 呈现给用户
4. 确认后执行
5. 验证:审计日志 + 可观测性显示无错误
示例:
✅ 调查完成:worker `api-gateway` 在 18:00-18:30 期间经历了 5xx 激增
根本原因:部署的新代码在处理 /v2/users 时抛出 TypeError
证据:
- 日志:18:02 首次出现 "Cannot read property 'id' of undefined"
- 审计:18:00 用户 dev@example.com 部署了新版本
- 指标:错误率从 0.1% 跃升至 12%
建议:回滚到先前版本,或修复 /v2/users 处理程序
当集成到多步骤工作流时:
runs/<workflow>/active/<run_id>/
├── proposal.md # 症状/目标
├── context.json # 账户/worker/资源/时间范围
├── tasks.md # 检查清单 + 批准门
├── evidence/observability.md
├── evidence/audit.md
├── evidence/screenshots/
├── evidence/change-plan.md # 写入操作首先写在这里
├── evidence/report.md # 结论 + 证据 + 后续步骤
└── logs/events.jsonl # 可选的工具调用摘要
| 情况 | 操作 |
|---|---|
| 账户未设置 | 先运行 accounts_list → set_active_account |
| 资源不存在 | 验证 ID/名称,列出可用资源 |
| 权限不足 | 解释所需权限,检查 API 令牌范围 |
| 可观测性查询范围太广 | 拆分成更小的时间范围 |
每周安装数
47
仓库
GitHub 星标数
327
首次出现
2026年2月10日
安全审计
安装于
claude-code40
opencode38
gemini-cli36
cursor36
github-copilot35
codex35
Manage Cloudflare services: Workers, KV, R2, D1, Hyperdrive, Observability, Builds, and Audit Logs.
MCP is optional. This skill works with MCP (auto), Wrangler CLI, or Dashboard. See BACKENDS.md for execution options.
| Tier | Purpose | Scope | Risk Control |
|---|---|---|---|
| Diagnose | Read-only/query/troubleshoot | Observability, Builds, Audit | Default entry, no writes |
| Change | Create/modify/delete resources | KV, R2, D1, Hyperdrive | Requires confirmation + verification |
| Super Admin | Highest privileges | All + Container Sandbox | Only in isolated/test environments |
1. Plan: Read current state first (list/get)
2. Confirm: Output precise change (name/ID/impact), await user confirmation
3. Execute: create/delete/update
4. Verify: audit logs + observability confirm no new errors
| Category | What You Can Do |
|---|---|
| Observability | Query worker logs/metrics, discover fields, explore values |
| Builds | List build history, get build details, view build logs |
| Browser | Fetch page HTML, convert to markdown, take screenshots |
| Audit | Pull change history by time range |
| Workers | List workers, get details, view source code |
| Resource | Operations |
|---|---|
| KV | List, get, create ⚠️, update ⚠️, delete ⚠️ |
| R2 | List, get, create ⚠️, delete ⚠️ |
| D1 | List, get, query, create ⚠️, delete ⚠️ |
| Hyperdrive | List, get, create ⚠️, edit ⚠️, delete ⚠️ |
⚠️ = Requires confirmation
Temporary container for isolated tasks (~10 min lifecycle):
1. Clarify symptoms → worker name / time range / error type
2. Query observability to pull logs/metrics
3. If build-related → get build logs
4. If page-related → take screenshot to reproduce
5. Trace changes → pull audit logs
6. Summarize: root cause + evidence + fix recommendations
1. List accounts → set active account
2. List resources (KV / R2 / D1)
3. Plan changes → present to user
4. Execute after confirmation
5. Verify: audit logs + observability shows no errors
Example:
✅ Investigation complete: worker `api-gateway` experienced 5xx spike between 18:00-18:30
Root cause: New code deployed threw TypeError when processing /v2/users
Evidence:
- Logs: 18:02 first occurrence of "Cannot read property 'id' of undefined"
- Audit: 18:00 user dev@example.com deployed new version
- Metrics: error_rate jumped from 0.1% to 12%
Recommendation: Roll back to previous version, or fix /v2/users handler
When integrating into multi-step workflows:
runs/<workflow>/active/<run_id>/
├── proposal.md # Symptoms/objectives
├── context.json # Account/worker/resource/time_range
├── tasks.md # Checklist + approval gate
├── evidence/observability.md
├── evidence/audit.md
├── evidence/screenshots/
├── evidence/change-plan.md # Write operations written here first
├── evidence/report.md # Conclusion + evidence + next steps
└── logs/events.jsonl # Optional tool call summary
| Situation | Action |
|---|---|
| Account not set | Run accounts_list → set_active_account first |
| Resource doesn't exist | Verify ID/name, list available resources |
| Insufficient permissions | Explain required permissions, check API token scope |
| Observability query too broad | Split into smaller time ranges |
Weekly Installs
47
Repository
GitHub Stars
327
First Seen
Feb 10, 2026
Security Audits
Gen Agent Trust HubFailSocketPassSnykWarn
Installed on
claude-code40
opencode38
gemini-cli36
cursor36
github-copilot35
codex35
Azure 配额管理指南:服务限制、容量验证与配额增加方法
138,600 周安装