From forge-obsidian
Push a vault skill to its target module for sharing via GitHub. USE WHEN the user wants to publish a drafted skill, finalize a behavioural rule, or move authored content from the vault workspace to a module.
npx claudepluginhub n4m3z/forge-obsidianThis skill uses the workspace's default tool permissions.
Push a skill from the vault workspace to its target module, with a review gate to scrub user-specific content before it lands in the module.
Publishes local skills to claude-code-plugin repo with correct structure, category placement, validation, duplicate checks, and beta/internal support.
Guides contributing custom skills to upstream repository: sync main, create feature branch, edit/create SKILL.md, commit, push to fork, create GitHub PR using gh CLI.
Evolves existing skills by refining content in-place or creating advanced variants. Assesses gaps, applies changes, updates version metadata, syncs registry/cross-references. Use for outdated steps, feedback gaps, complexity upgrades.
Share bugs, ideas, or general feedback.
Push a skill from the vault workspace to its target module, with a review gate to scrub user-specific content before it lands in the module.
Before running the promote script, spawn a skill-reviewer agent (via the Task tool) to analyze the draft skill. The agent MUST:
$FORGE_USER_ROOT/Orchestration/Skills/<SkillName>/SKILL.mdVaults/Personal/...)Show the review findings. For each issue, present the specific edit. The user can:
Apply accepted edits to the draft in Orchestration/Skills/ before promoting.
# Promote a single skill
Modules/forge-obsidian/bin/forge-promote BehavioralSteering
# Promote all skills with source_module: in the workspace
Modules/forge-obsidian/bin/forge-promote
The script:
source_module: from frontmatter to find the target moduleSKILL.yaml sidecar (via promote.yaml allowlist)Orchestration/Skills/Orchestration/Upstream/<SkillName>/ → module skill directoryCanon + sidecar output is mandatory. After promote, the module directory must contain both SKILL.md (Claude-canonical) and SKILL.yaml (Obsidian metadata). A promote without a sidecar is incomplete — the round-trip via /Draft would lose vault metadata.
/Update: Regenerate plugin.json if skill directories changedBinary: Modules/forge-obsidian/bin/forge-promote
Auto-resolves FORGE_USER_ROOT from defaults.yaml/config.yaml.
| User Says | Args | Effect |
|---|---|---|
| "promote BehavioralSteering" | BehavioralSteering | Review + push single skill to its source module |
| "promote all", "promote everything" | (no args) | Review + push all skills with source_module: |
source_module: frontmatter — vault-permanent skills are left untouchedsource_module: is missing (prompts you to ask the user which module)Orchestration/Upstream/ (stays visible in Obsidian, excluded from Linter)