worker-module-architecture
Architectural guidance for modifying BK-CI Worker execution flows, including task handling and plugin management.
Install
mkdir -p .claude/skills/worker-module-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2191" && unzip -o skill.zip -d .claude/skills/worker-module-architecture && rm skill.zipInstalls to .claude/skills/worker-module-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
处理 BK-CI Worker 执行器时使用，例如任务领取与执行、插件运行、日志上报、环境变量传递和制品归档。当用户要改 Worker 执行链路而不是插件定义或调度策略时优先使用。Key capabilities
- →Modify Worker startup and execution processes
- →Handle task claiming, task factory, and task executor logic
- →Troubleshoot plugin download, execution, and callback issues within the Worker
- →Adjust log reporting, environment variables, archiving, and API calls
- →Optimize Worker lifecycle or execution stability
How it works
This skill provides architectural guidance for developers to understand and modify the BK-CI Worker's internal mechanisms for task execution, plugin management, and data reporting.
Inputs & outputs
When to use worker-module-architecture
- →Optimize Worker execution flow
- →Debug plugin download issues
- →Modify log reporting mechanisms
- →Handle environment variable passing
About this skill
Worker 模块架构
适用场景
- 修改 Worker 启动和执行流程
- 处理任务领取、任务工厂、任务执行器
- 排查插件在 Worker 内部的下载、执行和回传问题
- 修改日志上报、环境变量、归档和 API 调用
- 优化 Worker 生命周期或执行稳定性
不适用场景
- 只是开发插件本体或改
task.json - 只是修改 Agent 守护、心跳和升级逻辑
- 只是修改 Dispatch 的调度、配额或队列策略
- 只是修改流水线模型定义
快速指导
- 这个 skill 关注的是“任务到了构建机以后，Worker 如何真正执行”。
- Worker 是执行器，不是调度器，也不是插件定义中心。
- 先按问题类型进入对应参考文档：
- 生命周期与执行主链路：
reference/1-runtime-flow.md - 插件执行、日志与制品：
reference/2-task-plugin-log-artifact.md - 环境变量、API 与排查：
reference/3-env-api-debug.md
- 生命周期与执行主链路：
- 如果现象是“插件定义不对”，切到
pipeline-plugin-development。 - 如果现象是“根本没被派到这台机器执行”，切到
dispatch-module-architecture或agent-module-architecture。
高信号规则
- Worker 的主职责是执行，不负责资源调度决策
- 任务执行、日志、变量、归档是同一条运行链上的不同环节
- 插件问题和 Worker 问题经常混淆，先判断契约层还是执行层
- 执行链路改动要优先考虑幂等、失败恢复和日志可诊断性
关键陷阱
- 把调度问题误判成 Worker 问题
- 只改执行逻辑，不同步看变量、日志和结果回传
- 输出变量和日志混用，导致调试与契约边界不清
- 在任务工厂或执行器里堆过多分支，后续难扩展
延伸阅读
- 生命周期与执行主链路：
reference/1-runtime-flow.md - 插件执行、日志与制品：
reference/2-task-plugin-log-artifact.md - 环境变量、API 与排查：
reference/3-env-api-debug.md - 如果你在开发插件：再看
pipeline-plugin-development - 如果你在改 Agent 守护或升级：再看
agent-module-architecture - 如果你在改调度：再看
dispatch-module-architecture
When not to use it
- →Developing only the plugin itself or modifying `task.json`
- →Modifying only Agent daemon, heartbeat, and upgrade logic
- →Modifying only Dispatch scheduling, quotas, or queue strategies
Limitations
- →Does not cover plugin definition or `task.json` modifications
- →Does not cover Agent daemon, heartbeat, or upgrade logic
- →Does not cover Dispatch scheduling, quotas, or queue strategies
How it compares
This skill focuses on the internal execution flow of the Worker after a task is received, distinct from defining plugins or managing scheduling policies.
Compared to similar skills
worker-module-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| worker-module-architecture (this skill) | 3 | 3mo | No flags | Advanced |
| monorepo-architect | 3 | 4mo | No flags | Advanced |
| 00-bkci-global-architecture | 1 | 3mo | No flags | Advanced |
| turborepo | 61 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by TencentBlueKing
View all by TencentBlueKing →You might also like
monorepo-architect
sickn33
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,
00-bkci-global-architecture
TencentBlueKing
BK-CI 全局架构指南，以流水线为核心的模块协作全景图，涵盖完整执行流程、模块依赖关系、数据流向、核心概念。当用户需要理解系统架构、进行跨模块开发、了解模块间协作或规划架构设计时优先阅读。
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
ml-pipeline-workflow
wshobson
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
nx-workspace-patterns
wshobson
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.