Is your open-source repository ready to promote? Ask your coding agent. Orviqa Lite is a free skill that checks what decides whether a visitor stays, and gives you a one-line verdict: Ready, Ready after N fixes, or Not ready yet.
It runs locally with your own agent and model. Nothing is sent to Orviqa, and it never edits a file or changes your GitHub repository without asking.
Install
In Claude Code:
claude plugin marketplace add uoparaji/orviqa-lite
claude plugin install orviqa-lite@orviqa
Then, inside your repository, ask: “Is this repo ready to promote?”
Other agents: the skill uses the open Agent Skills format. Copy skills/orviqa-lite/ from the repository into your agent’s skills folder.
What Lite does
Health check. A fixed checklist run by a script: README, licence, About description, topics, docs, examples, tests, CI, releases, community files.
README audit. Eleven areas, including whether the quick start runs on a clean machine. Every finding quotes the line it is about.
Positioning. A tagline, About description and topics, each benefit tied to the file that proves it. If yours are already good, it says keep them.
What Orviqa adds
Lite stops when the repository is ready. Orviqa starts there.
Where to post. Communities graded good fit, possible or not recommended for this project, each with its own self-promotion rules.
What to write. Drafts for each channel from your releases, with the claims you need to check before posting.
When to do it. A dated 30-day plan that starts with the fixes Lite found, then moves to promotion.
Publishing. One click to GitHub Releases, DEV.to, Hashnode, Mastodon, Bluesky, Reddit, Discord, X and LinkedIn, only after you approve each post.