New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Rig Bundles And Shareable Artifacts

by mvschwarz in mvschwarz/openrig

A skill your agent uses when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension…

Apache-2.0Auto-check passedAgent Workflows

Install Rig Bundles And Shareable Artifacts

skills CLI
$ npx skills add mvschwarz/openrig --skill rig-bundles-and-shareable-artifacts -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig rig-bundles-and-shareable-artifacts --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/core/rig-bundles-and-shareable-artifacts .claude/skills/rig-bundles-and-shareable-artifacts && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rig-bundles-and-shareable-artifacts
GitHub stars
6.6k
Token cost
~1.1k tokens
SKILL.md length
452 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension…

  • Works in 4 steps: A bundle works only on the operator's… → A bundle includes too much local state… → A bundle declares topology but omits… → …
  • Installing a rig bundle (packaged
  • SKILL.md covers Use this when, Don't use this when, The bundle vs extension… and Failure modes (4), plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rig Bundles And Shareable Artifacts is an agent skill from mvschwarz/openrig. Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability. Covers the 4 failure modes that prevent bundles from working anywhere but the operator's machine, and the inspect-before-install discipline.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Installing a rig bundle (packaged
  • Shareable artifact that instantiates an opinionated OpenRig topology + workflow)
  • Reasoning about the bundle vs extension boundary
  • Auditing a bundle for portability

Example prompts

  • “/rig-bundles-and-shareable-artifacts”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. A bundle works only on the operator's machine because paths, providers, or credentials are implicit. Bundles must be self-describing for a…
  2. A bundle includes too much local state and becomes a backup archive instead of a reusable artifact. Bundle is the intended shape, not the…
  3. A bundle declares topology but omits proof expectations or workflow mode. Topology alone doesn't tell users what "working as advertised"…
  4. Users cannot inspect what a bundle will create before installing it. rig bundle inspect must show what will be created without side effects.

What it can do on your machine

Read from SKILL.md and the folder at commit 4b48ca2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rig Bundles And Shareable Artifacts loads about 1.1k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 452 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit 4b48ca2, republished under its Apache-2.0 licence (© mvschwarz). 452 words, ~1,078 tokens.

Download SKILL.mdSave it as .claude/skills/rig-bundles-and-shareable-artifacts/SKILL.md (or your agent's skills folder).
name
rig-bundles-and-shareable-artifacts
description
Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability. Covers the 4 failure modes that prevent bundles from working anywhere but the operator's machine, and the inspect-before-install discipline.
metadata.cli_surfaces_referenced
bundle create, bundle inspect, bundle install

Rig Bundles and Shareable Artifacts

A rig bundle is a packaged, shareable artifact that can instantiate an opinionated OpenRig topology and workflow. It may include:

  • rig specs
  • agent specs
  • workflow specs
  • startup files
  • skills or skill references
  • operating-mode declarations
  • proof expectations
  • supporting fragments

Shareable artifact is broader than bundle: specs, bundles, skills, workflows, and extensions can all be shared. A bundle is the packaged form for "load this topology and way of working."

Use this when

  • Authoring a bundle from a proven lab pattern
  • Installing a bundle (rig bundle install <path>)
  • Inspecting a bundle before install (rig bundle inspect <path>)
  • Reasoning about bundle vs extension boundary (bundle declares topology + workflow; extension adds behavior)
  • Auditing a bundle for portability — does it work on a clean OpenRig environment, or only the author's machine?

Don't use this when

  • The work is a one-off topology you won't reuse. Specs alone are sufficient.
  • The intent is to add runtime behavior (commands, views, dashboards). Use extension-and-user-workspace, not bundles.
  • You want to ship a workflow as a daemon feature. Bundle is the path before daemon promotion.

The bundle vs extension boundary (load-bearing)

ConceptDeclaresExample
BundleRig shape + workflow ("load this topology and way of working")A Velocity Team bundle
ExtensionBehavior added to user workspace/runtimeA custom command, view, or dashboard

Don't confuse them. A bundle is opinionated content; an extension is added behavior. Both can be shareable artifacts, but they're structurally distinct.

Show full SKILL.md (215 more words)Show less

Failure modes (4)

  1. A bundle works only on the operator's machine because paths, providers, or credentials are implicit. Bundles must be self-describing for a clean OpenRig environment.
  2. A bundle includes too much local state and becomes a backup archive instead of a reusable artifact. Bundle is the intended shape, not the current state of one specific install.
  3. A bundle declares topology but omits proof expectations or workflow mode. Topology alone doesn't tell users what "working as advertised" means.
  4. Users cannot inspect what a bundle will create before installing it. rig bundle inspect must show what will be created without side effects.

Proof standard

Proof should:

  1. Install the bundle into a clean OpenRig environment
  2. Instantiate it
  3. Verify the expected seats and workflow mode
  4. Run a small smoke proof that the topology behaves as advertised

Bundle path → product

Bundles are how proven lab patterns become reusable product experiences:

local dogfood pattern
  → bundle (with manifest, parameterization, proof expectations)
  → installed by another user on clean OpenRig
  → opinionated workflow shipped without becoming a daemon feature
  → if dependable, graduate parts into core daemon

This is also how OpenRig can ship opinionated workflows without making every workflow a daemon feature.

See also

  • extension-and-user-workspace skill — sibling primitive for user-owned behavior added to runtime; bundle vs extension boundary
  • specification-system skill — rig specs / agent specs / workflow specs that bundles package
  • agent-starters skill — bundles can include or reference Agent Starters
  • openrig-user skill — rig bundle create / inspect / install CLI surface

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/core/rig-bundles-and-shareable-artifacts of mvschwarz/openrig.

Open the folder on GitHubat commit 4b48ca2

Compare with similar skills

Rig Bundles And Shareable Artifacts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rig Bundles And Shareable Artifacts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rig Bundles And Shareable Artifacts this skillmvschwarz/openrig6.6k—~1.1kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.6k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    6.6k GitHub stars~864 tokensUpdated today
    Auto-check passed

  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    6.6k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Seat Continuity and Handover

    mvschwarz/openrig

    Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    6.6k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Addressable Markdown Loader

    mvschwarz/openrig

    Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    6.6k GitHub stars~341 tokensUpdated today
    Auto-check passed

  • Agent Starters

    mvschwarz/openrig

    Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.

    6.6k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Rig Bundles And Shareable Artifacts

What does Rig Bundles And Shareable Artifacts do?

A skill your agent uses when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension…. Rig Bundles And Shareable Artifacts is an agent skill from mvschwarz/openrig. Use when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension boundary, or auditing a bundle for portability.

When should I use Rig Bundles And Shareable Artifacts?

Rig Bundles And Shareable Artifacts fits situations like: installing a rig bundle (packaged; shareable artifact that instantiates an opinionated OpenRig topology + workflow); reasoning about the bundle vs extension boundary; auditing a bundle for portability.

How do I install Rig Bundles And Shareable Artifacts in Claude Code?

Run `npx skills add mvschwarz/openrig --skill rig-bundles-and-shareable-artifacts -a claude-code`. Or copy the skill folder (skills/_canonical/core/rig-bundles-and-shareable-artifacts in mvschwarz/openrig) into .claude/skills/rig-bundles-and-shareable-artifacts in your project. Claude Code loads it when a task matches its description.

How do I install Rig Bundles And Shareable Artifacts in Codex?

Run `npx skills add mvschwarz/openrig --skill rig-bundles-and-shareable-artifacts -a codex`. Or copy the skill folder (skills/_canonical/core/rig-bundles-and-shareable-artifacts in mvschwarz/openrig) into .agents/skills/rig-bundles-and-shareable-artifacts in your project. Codex loads it when a task matches its description.

Can I use Rig Bundles And Shareable Artifacts in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill rig-bundles-and-shareable-artifacts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rig-bundles-and-shareable-artifacts, .gemini/skills/rig-bundles-and-shareable-artifacts, .github/skills/rig-bundles-and-shareable-artifacts and .opencode/skills/rig-bundles-and-shareable-artifacts in your project.

What does Rig Bundles And Shareable Artifacts need to run?

SKILL.md names no scripts, command-line tools or credentials: Rig Bundles And Shareable Artifacts is instructions for the agent only.

Does Rig Bundles And Shareable Artifacts access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rig Bundles And Shareable Artifacts safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rig Bundles And Shareable Artifacts use?

Rig Bundles And Shareable Artifacts is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rig Bundles And Shareable Artifacts use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rig Bundles And Shareable Artifacts?

Skills that share tags, products or a category with Rig Bundles And Shareable Artifacts: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rig Bundles And Shareable Artifacts?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,551 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 10, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.