nexu-io/open-design / plugins/_official/examples/od-plugin-publish-github
od-plugin-publish-github
VerifiedPublish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.3 KB |
| open-design.json | config | 5.0 KB |
SKILL.md
View on GitHub---
name: od-plugin-publish-github
description: Publish a local OpenDesign plugin to a new public GitHub repository using gh CLI.
triggers:
- publish plugin
- github repo
- open source plugin
od:
mode: utility
platform: desktop
scenario: plugin-sharing
---
# Publish Plugin to GitHub
Use this workflow when the active project contains a copied plugin folder and the user wants it published as a new public GitHub repository.
## Workflow
1. Read the active plugin inputs. `plugin_context_path` is the copied plugin folder relative to the project working directory.
2. Inspect `open-design.json`, `SKILL.md`, and any compatibility metadata in the copied folder.
3. Call the local daemon endpoint instead of hand-rolling GitHub commands:
`curl -sS -X POST "$OD_DAEMON_URL/api/projects/$OD_PROJECT_ID/plugins/publish-github" -H 'content-type: application/json' -d '{"path":"<plugin_context_path>"}'`
4. Read the JSON response. If `ok` is true, report the final repository URL and any useful log/validation summary.
5. If the endpoint fails, report its `message`, `code`, and useful log lines. When authentication is missing, tell the user to run `gh auth login --hostname github.com`.
Prefer the manifest `name` as the repository slug. If that repository already exists, choose the next clear slug and mention the rename.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |