跳到正文
cccskills
免费在 GitHub 公开

specification-system

Define reusable OpenRig agent setups, roles, and workflows in specification files. Review dependencies that prevent use on another host, distinguish specifications from bundles and extensions, and verify both file structure and actual execution.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction.

查看安装方法

适用场景

  • Defining reusable agent roles and workflows
  • Reviewing specifications for use on another host
  • Testing specifications in a clean OpenRig environment
  • Separating specifications, bundles, and extensions

包含的文件(1)

  • SKILL.md4.8 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Specification System

The declarative primitive family for OpenRig intent: rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, and the user spec library that stores and reuses them.

Specs are how humans and agents describe repeatable topology and behavior without re-explaining it in chat. They are also shareable artifacts: a user should be able to publish a spec or spec family so another user can instantiate the same rig shape, role structure, or workflow pattern.

Without a dependable spec primitive, OpenRig depends on manual startup prompts and tribal memory. That blocks repeatability, product demos, rig bundles, and autonomous rig construction.

Use this when

  • Authoring a RigSpec / AgentSpec / workflow spec
  • Designing a startup/context fragment
  • Reasoning about spec-library lifecycle (validation, sharing, upgrade semantics)
  • Auditing a spec for portability (does it run on another host?)
  • Distinguishing spec vs bundle vs extension cleanly

Don't use this when

  • The work is one-off and won't be reused. Manual rig assembly is fine for one-shot work.
  • The intent is to package a topology + workflow as a shareable artifact. That's rig-bundles-and-shareable-artifacts.
  • The intent is to add runtime behavior. That's extension-and-user-workspace.

Failure modes (4)

  1. A spec can instantiate a topology but not the workflow or operating mode needed to use it. Topology is necessary but not sufficient — workflow and operating mode must be declared too.
  2. A shared spec depends on local paths or hidden startup fragments and fails on another host. Specs must be self-describing for portability.
  3. Agents modify specs as one-off files instead of preserving reusable user/library intent. Specs are reusable; treating each instance as one-off destroys the primitive's value.
  4. Validation proves YAML shape but not whether the declared topology can actually run. Structural validation is not enough; runtime realization is the real proof.

Proof standard

Proof should:

  1. Author a spec
  2. Validate it (structural)
  3. Install it (into spec library)
  4. Instantiate it on a clean OpenRig environment
  5. Show both structural validation AND runtime realization

Validation alone is insufficient.

Spec / bundle / extension boundary

ConceptDeclaresExample
SpecTopology / role / workflow shape (declarative intent)rig.yaml, agent.yaml, workflow.yaml
BundleSpec(s) + supporting fragments packaged for shareable instantiationA Velocity Team bundle
ExtensionRuntime behavior added to user workspaceRigX command, custom view

Don't conflate them. The contract should distinguish spec, bundle, and extension cleanly.

Currently shipped surfaces

OpenRig already has:

  • RigSpec / AgentSpec authoring (agent.yaml, rig.yaml formats; see openrig-architect skill)
  • Workflow specs (markdown/YAML files, daemon read-through cache via workflow_specs table; see workflow-runtime skill)
  • Bundle/spec command surface (rig bundle / spec / agent / specs ls/show/preview/add/sync/remove/rename)
  • Spec library (filesystem-backed at packages/daemon/specs/ + ~/.openrig/specs/ per cli-reference.md)

Not yet shipped:

  • Spec library lifecycle (validation, sharing, upgrade) treated as a first-class primitive
  • Cross-host spec sharing
  • Marketplace / public registry

See also

  • openrig-architect skill — RigSpec / AgentSpec authoring discipline
  • workflow-runtime skill — workflow spec authoring + transactional-scribe contract
  • rig-bundles-and-shareable-artifacts skill — bundle is the packaged form of specs
  • extension-and-user-workspace skill — extensions add runtime behavior; specs declare intent
  • openrig/docs/reference/rig-spec.md (product reference doc) — RigSpec format specification
  • openrig/docs/reference/agent-spec.md (product reference doc) — AgentSpec format specification

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.

中文简介正在准备中。当前显示英语简介。

  • Automating form entry and submission
  • Extracting page text and saving screenshots
  • Comparing page appearance before and after changes
mvschwarz/openrig78332026年10月19日 更新

Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.

中文简介正在准备中。当前显示英语简介。

  • Designing an application operated by OpenRig agents
  • Organizing instructions and shared application state
  • Tracing unexpected behavior to its source
mvschwarz/openrig78332026年10月19日 更新

Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.

中文简介正在准备中。当前显示英语简介。

  • Designing procedures for environments with varying conditions
  • Resuming interrupted operations from verified evidence
  • Deciding whether an agent or ordinary code should control a procedure
mvschwarz/openrig78332026年10月19日 更新

Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.

中文简介正在准备中。当前显示英语简介。

  • Create reusable startup context for an agent role
  • Refresh an agent workspace from an existing starter
  • Check a starter’s source history and freshness
mvschwarz/openrig78332026年10月19日 更新

Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.

中文简介正在准备中。当前显示英语简介。

  • Designing startup files for a new agent
  • Reviewing stale guidance used by running agents
  • Separating role information from reusable procedures
mvschwarz/openrig78332026年10月19日 更新

Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.

中文简介正在准备中。当前显示英语简介。

  • Configuring command permissions before launching an agent team
  • Reducing repeated approvals for selected rig commands
  • Adding permission rules within a chosen project scope
mvschwarz/openrig78332026年10月19日 更新

查看 mvschwarz 的全部技能

报告此技能的问题