EM

e-m-albright/workbench

Developer tools

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る

1 stars 品質 54 トレンド 22

Core: agent workbench - shared rules, skills, and tooling

概要

The portable intelligence and engineering-guidance layer for my development environment. Workbench is where I version the behavior I want Pi, Claude Code, and Codex to share: agent rules, skills, prompts, safety policy, engineering doctrine, and reusable project-health tools. It turns those canonical sources into each harness's native configuration and verifies the live result. This is a personal, opinionated repository. It optimizes one workflow rather than trying to become a general agent platform. Workbench is the agent-intelligence layer of the capability stack described canonically in STACK.md: dotfiles provisions the host and installs Workbench; private workflow layers may apply both public layers through their CLI contracts. Each layer stands alone - integration is composition and provisioning order, never cross-repository Python imports. Workbench gives me one place to answer four questions: 1.

README

以下は原文 README の抜粋です。原文を見る。

Workbench

The portable intelligence and engineering-guidance layer for my development environment.

Workbench is where I version the behavior I want Pi, Claude Code, and Codex to share: agent rules, skills, prompts, safety policy, engineering doctrine, and reusable project-health tools. It turns those canonical sources into each harness’s native configuration and verifies the live result.

This is a personal, opinionated repository. It optimizes one workflow rather than trying to become a general agent platform.

Position in the Stack

Workbench is the agent-intelligence layer of the capability stack described canonically in STACK.md:

dotfiles   host foundation and machine capabilities
    ↓
workbench  reusable agent intelligence and engineering standards
    ↓
private workflow layers

dotfiles provisions the host and installs Workbench; private workflow layers may apply both public layers through their CLI contracts. Each layer stands alone - integration is composition and provisioning order, never cross-repository Python imports.

What It Does

Workbench gives me one place to answer four questions:

  1. How should my coding agents behave? Shared rules, safety boundaries, reusable skills, and review guidance live under agents/.
  2. How do those instructions reach each harness? workbench sync translates and deploys the canonical sources into Pi, Claude Code, and Codex configuration.
  3. Has live configuration drifted? workbench drift compares the deployed files and installed plugins directly with the repository.
  4. What engineering judgment should carry between projects? The playbook, health kit, and review skills preserve reusable decisions without coupling them to a particular codebase.
                    canonical sources
              agents/   playbook/   health/
                           │
                  workbench sync all
                           │
          ┌───────────────┼───────────────┐
          │               │               │
         Pi          Claude Code         Codex
  rules, settings,   rules, settings,   rules, TOML,
  skills, extensions skills, plugins    skills, plugins
          │               │               │
          └───────────────┼───────────────┘
                          │
                workbench drift all
                    live drift report

The repository is both the source material and the deployment contract. It does not store a snapshot of the machine and compare against that stale observation.

Ownership Boundaries

Concern Owner
Agent rules, skills, prompts, MCP declarations, hooks, and permissions Workbench
Engineering doctrine, stack guidance, review skills, and portable health tooling Workbench
GitHub で README 全文を見る

推奨ツール

別のキーワードを試すか、フィルタを外してください。

インストール

npx skillfish add e-m-albright/workbench
MCP 初心者?mcpskill.org のガイドから始めましょう →