space-master

Governs WopalSpace ontology sync, capability assembly, and AGENTS.md and README maintenance workflows.

3|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill space-master-wopal-cn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: space-master
Source: https://github.com/wopal-cn/wopal-space-ontology/tree/main/skills/space-master
Command: npx skills add https://github.com/wopal-cn/wopal-space-ontology --skill space-master-wopal-cn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? WopalSpace spaces need a single authoritative way to keep their capabilities in sync with the central ontology pool, contribute changes upstream as clean PRs, and maintain project governance documents (AGENTS.md, README.md) without losing or duplicating work. ## Core Features & Use Cases - Ontology Maintenance: Manages the central capability pool model (upstream/main → local main → space/<name>), including wopal ontology update, wopal space sync, and fork-mode upstream contribution with topic-based PR splitting and two sync gates. - AGENTS.md Maintenance: Audits existing rules (keep/delete/fix), plans changes with user confirmation, and produces review-language then formal English versions following a strict content boundary specification. - README Maintenance: Creates or updates project-level READMEs with capability awareness, verified commands, and conditional document-set alignment. - Skill Lifecycle: Covers find, download, mandatory security scan, install, evaluate, and remove for Wopal skills. - Use Case: A space has diverged from the central pool with new skills and rule changes. Load this skill to run a dry-run sync analysis, present the full change inventory to the user, circle the contribution scope, and ship each topic as a separate upstream PR. ## Quick Start Ask the agent to check the space and ontology status, preview a space sync, and propose which pending changes should be contributed upstream as PRs.

Frequently Asked Questions about space-master

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

FAQPage Schema
How do I sync a WopalSpace space with the central capability pool?

Run `wopal space sync` as a dry-run first to preview what moves, then `wopal space sync --confirm` to execute. The sync integrates space-unique evolution upward into local main first, then fast-forwards the space downward.

How do I contribute ontology changes upstream as a PR?

Use `wopal ontology contribute` in fork mode only; clone mode blocks contributions. Present the full pending file inventory, let the user confirm scope, split changes into one-topic PRs, and pass comma-separated `--include` globs after a dry-run.

Why does wopal ontology contribute fail in clone mode?

Clone mode points origin directly at the canonical upstream, so upstream PRs are strictly unsupported. Convert the repository to fork mode, where origin is your fork and upstream is the canonical repo, then retry the contribution.

When should AGENTS.md be updated after a project change?

Update AGENTS.md only when a long-lived behavior boundary exists that code, tests, config, and existing docs cannot carry. Audit every existing rule first, classify as keep, delete, or fix, and get user confirmation before writing.

Can I install a Wopal skill without running the security scan?

No. `wopal skills scan` is mandatory before installation; it checks for malicious code, data exfiltration, and invalid triggers. After installing, verify with `ls -la .wopal/skills/<name>/SKILL.md` and `wopal skills list`.