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.
Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.
读取 https://funcoding.ai/skills/mvschwarz/openrig/specification-system/install.md ，按里面的步骤帮我安装这个 Skill。
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.
rig-bundles-and-shareable-artifacts.extension-and-user-workspace.Proof should:
Validation alone is insufficient.
| Concept | Declares | Example |
|---|---|---|
| Spec | Topology / role / workflow shape (declarative intent) | rig.yaml, agent.yaml, workflow.yaml |
| Bundle | Spec(s) + supporting fragments packaged for shareable instantiation | A Velocity Team bundle |
| Extension | Runtime behavior added to user workspace | RigX command, custom view |
Don't conflate them. The contract should distinguish spec, bundle, and extension cleanly.
OpenRig already has:
agent.yaml, rig.yaml formats; see openrig-architect skill)workflow_specs table; see workflow-runtime skill)rig bundle / spec / agent / specs ls/show/preview/add/sync/remove/rename)packages/daemon/specs/ + ~/.openrig/specs/ per cli-reference.md)Not yet shipped:
openrig-architect skill — RigSpec / AgentSpec authoring disciplineworkflow-runtime skill — workflow spec authoring + transactional-scribe contractrig-bundles-and-shareable-artifacts skill — bundle is the packaged form of specsextension-and-user-workspace skill — extensions add runtime behavior; specs declare intentopenrig/docs/reference/rig-spec.md (product reference doc) — RigSpec format specificationopenrig/docs/reference/agent-spec.md (product reference doc) — AgentSpec format specification
anthropics/skills180kApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
AI & agents
anthropics/skills180kA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
AI & agents
anthropics/skills180kanthropics/skills180kGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
AI & agents
anthropics/skills180kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
AI & agents
anthropics/skills180kStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
AI & agents