OpenParable
Skip to content

DevOps & Security skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

doca-sta

Use this skill when the user is doing hands-on NVMe-over-Fabrics storage-target work on a BlueField DPU or ConnectX NIC with DOCA STA — standing up a doca_sta DOCA Core context that accelerates the target-side NVMe-oF data path over RDMA, defining doca_sta_subsystem targets (NQN + namespaces) backed by local NVMe-PCI backend disks (doca_sta_be), checking device support via doca_sta_cap_is_supported, sizing the per-connection I/O queues, or debugging DOCA_ERROR_* from a STA call. Trigger even when the user does not say "DOCA STA" — typical implicit phrasings include "my NVMe-oF Connect never completes", "Identify Controller times out over RoCE", "16 I/O queues at depth 1024 — does this BlueField support that", "offload the nvmf target onto the DPU", or "DOCA_ERROR_IO_FAILED on an NVMe read". Refuse and route elsewhere for DOCA install, raw RDMA data movement, raw packet I/O, flow-rule programming, or initiator-side / host NVMe stack work — those belong to other skills.

2.52k repo stars283 repo forks
DevOps & Security

doca-urom-svc

SECURITY: the DOCA UROM Service binary has NO standalone access control (no authz list / `allowed_host` / `allowed_users` / `auth_token`) — access is governed ENTIRELY by DOCA Comch pairing + RDMA permissions, so any host able to establish a Comch pairing can drive remote memory ops; isolate accordingly. Use when operating the DOCA UROM Service container on a BlueField Arm to run remote memory ops (puts, gets, atomics, collectives) that paired hosts enqueue via the host-side `doca-urom` library — pulling the NGC container, choosing UCX-component surface, sizing the enqueue queue, wiring Comch endpoint pairing with `doca-urom`, or pinning host-library + service versions per the DOCA Compatibility Policy. Trigger even without 'DOCA UROM' — e.g. 'UCX collectives slow on host CPU, want BlueField offload', 'enqueue returns NOT_PERMITTED though doca_dev access is fine', 'ops enqueue but completions never fire'. Refuse for host-side app code, MPI/UCX integration, or installing DOCA.

2.52k repo stars283 repo forks
DevOps & Security

agent-module-architecture

处理 BK-CI Agent 构建机侧能力时使用,例如守护进程、心跳、Ask 轮询、任务拉起、升级更新和与 Dispatch/Worker 的协作。当用户要改构建机宿主侧行为而不是 Worker 执行细节时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

artifactory-module-architecture

处理 BK-CI 制品上传下载、制品元数据、BkRepo 或磁盘后端存储、文件任务和清理链路时使用。当用户提到构建产物、制品归档、下载令牌、报告文件、BkRepo 集成或制品清理时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

dispatch-module-architecture

处理 BK-CI 构建调度时使用,例如构建机选择、队列推进、配额控制、第三方构建机调度、Docker/Kubernetes 调度。当用户要改任务分配策略而不是 Agent/Worker 执行细节时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

managing-devops-pipeline

通过 MCP 管理 BK-CI 流水线构建时使用,例如查询构建历史、获取启动参数、查看构建状态和在确认后触发构建。当用户要操作现有流水线而不是修改代码实现时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

microservice-infrastructure

处理 BK-CI 微服务底层基础设施时使用,例如条件配置、事件驱动、服务间通信、国际化与日志规范。当用户要搭多环境配置、异步事件、Feign 调用或统一 i18n/日志时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

permission-model-change-guide

修改 BK-CI IAM RBAC 权限模型时使用,例如新增资源类型、设计操作列表、配置 IAM 资源、补迁移数据和验证回调链路。当用户要变更权限模型而不是普通权限调用时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

pipeline-model-architecture

理解或修改 BK-CI 流水线 Model、Stage、Container、Element 结构时使用。当用户提到流水线模型、Stage/Job/Task 数据结构、模型扩展、模型校验、版本兼容、YAML 与 Model 转换时优先使用。

2.51k repo stars519 repo forks
DevOps & Security

pipeline-template-module

处理 BK-CI 流水线模板的创建、版本管理、实例化、权限控制、PAC 模板和商店集成时使用。当用户提到模板复用、模板版本、批量实例化、模板迁移、商店模板或 PAC 模板时优先使用。

2.51k repo stars519 repo forks
DevOps & Security