workspace-governor

Classify proposed artifacts into core, workspace, or ignored local state.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup --skill workspace-governor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-governor
Source: https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup/tree/main/skills/workspace-governor
Command: npx skills add https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup --skill workspace-governor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Govern changes to the JM Labs Claude Desktop workspace ecosystem. Use whenever a task touches bootstrap, refresh, sync, export, local overlays, repo-local skills or agents, workspaces/tasks, generated tasklog.md, task intake flows, or when you need to decide whether an artifact belongs in the core, the workspace instance, or ignored local state.

Core Features & Use Cases

  • Classify every proposed artifact into exactly one destination: core, workspace, or ignored local state.
  • Enforce a clear change workflow: propose, validate, and route artifacts with governance rules that prevent cross-boundary leakage.
  • Reference-guided decision making: align with references/placement-rules.md to ensure portable vs instance-specific content.
  • Auditable outputs: produce consistent decisions suitable for downstream export, sync, and logging.

Quick Start

Describe the artifact you want to place and the governor will classify it as core, workspace, or ignored local state.

Frequently Asked Questions about workspace-governor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify workspace artifacts to prevent cross-boundary leakage during sync?

Workspace governance classifies every proposed artifact into exactly one destination: core, workspace, or ignored local state. This prevents cross-boundary leakage by enforcing clear ownership boundaries and validation steps during sync and export tasks.

What is the best way to govern bootstrap and export tasks for Claude Desktop workspaces?

Governing bootstrap and export tasks requires classifying artifacts like policies, contracts, and runtime components into core, workspace, or ignored local state. This ensures portable versus instance-specific content aligns with placement rules for auditable outputs.

How do I decide if a policy or contract belongs in the core or the workspace instance?

To decide if a policy or contract belongs in the core or workspace instance, apply reference-guided decision making using placement-rules.md. This classifies portable content as core and instance-specific content as workspace, ensuring proper artifact routing.

Does workspace governance support artifact classification for local overlays and repo-local skills?

Yes, workspace governance supports artifact classification for local overlays and repo-local skills. It evaluates these artifacts during tasks touching intake flows or tasklogs, routing them as core, workspace, or ignored local state based on ownership boundaries.

Why do my workspace changes leak across boundaries during refresh tasks?

Workspace changes leak across boundaries during refresh tasks when artifacts lack proper classification into core, workspace, or ignored local state. Applying governance rules validates ownership boundaries and routes artifacts correctly to prevent this issue.

Can I use workspace governance to produce auditable outputs for downstream export and logging?

Yes, you can use workspace governance to produce auditable outputs for downstream export and logging. It generates consistent artifact classification decisions suitable for tracking changes across bootstrap, refresh, sync, and export workflows.