Publish any project to GitHub with a polished, SEO-optimized README — no more rewriting the same "publish it on github" checklist every session.
This OpenCode skill turns your repeatable GitHub publishing routine into one command. Instead of restating screenshot rules, SEO keywords, and tag lists every time, just say:
"publish it on github do the necessary with readme screenshots and tags"
The skill handles everything:
| 🧭 Step | What happens |
|---|---|
| 1. Screenshots | Captures UI-only screenshots via readme-screenshots — no desktop or background noise |
| 2. Demo background | Adds a placeholder hero image or GIF when you have no real demo video |
| 3. SEO README | Writes a keyword-rich README: title, one-line pitch, badges, features, install, usage, license |
| 4. Discovery tags | Adds 5–10 GitHub topics/tags + repository description so your repo surfaces in search |
| 5. Publish | Commits, pushes to main, and optionally creates a repo/tag/release via gh CLI |
Install these before using the skill:
| 🛠️ Tool | Why |
|---|---|
readme-screenshots |
Takes the UI-only screenshots for your README |
git |
Commits and pushes your code |
gh (GitHub CLI) |
Optional — auto-creates the repo, adds topics, and makes a release |
Not using
readme-screenshots? The skill falls back to manual screenshots.
Not usinggh? Create the repo manually on GitHub.com and push via git.
Clone this repo into your OpenCode skills folder:
git clone https://github.com/Ryuki0x1/github-publish.git ~/.agents/skills/github-publishFolder structure after install:
~/.agents/skills/github-publish/
├── SKILL.md # the agent instructions (the actual skill)
├── README.md # this file (human-facing docs)
└── LICENSE # MIT license
In any project folder you want to ship:
- Run the skill: "publish it on github do the necessary with readme screenshots and tags"
- Follow the prompts — it captures screenshots, writes the README, and pushes to GitHub.
- Confirm the output checklist below.
Before you finish, make sure:
- 📸 UI-only screenshots saved (no background noise)
- 🎨 Fake/demo background visual present (
docs/demo.giforassets/hero.png) - 🔍 README follows the SEO structure (title, pitch, keywords, badges, features, install, usage, license)
- 🏷️ Repository description set on GitHub
- 🏷️ Topics/tags added (5–10)
- 📦 Code committed and pushed to
main - 🏷️ Release/tag created (optional)
# My Project
A keyword-rich one-line pitch under 60 characters.
Short description with discovery keywords.

## Badges
[](LICENSE)
## Features
- Feature 1
- Feature 2
## Installation
```bash
git clone https://github.com/user/repo.git# usage example
---
## 🔖 Topics on this repo
opencode-skill · github-publish · readme-screenshots · seo · readme · agent-skill · publish-to-github · opencode
> Topics are managed in GitHub repo settings and show up as search tags on the repo page.
---
## 📄 License
[MIT License](LICENSE)
---
## 🤝 Contributing
PRs welcome! Open an issue to suggest improvements to the README template, topic list, or publish steps.
