- Home
- Skills
- Technical Documentation
- Orviqa Lite: Is your repo ready to promote?
Works with the AI Agents you already use
Orviqa Lite: Is your repo ready to promote?
Before you post your project anywhere, the README decides whether visitors stay.
Free
Orviqa Lite: Is your repo ready to promote?
Example session with this skill installed
Is this repo ready to promote?
- Read your context and instructions
- Compiled the orviqa lite
Illustrative example for a fictional project, acme/tidyjson, a small CLI that formats JSON files. The project, its files and its line numbers are made up to show the shape of the output.
Ready after 2 fixes. Nothing critical is missing, but the quick start installs a package name that differs from the one in pyproject.toml, and the repository has no topics for GitHub search to match.
Step 1: Health check
In good shape. 1 important gap left, then it is down to refinements.
- Missing (IMPORTANT): GitHub topics. Add 5 to 10 topics using terms your audience would search: language, problem domain, ecosystem.
Step 2: README audit
What it is: tidyjson is a Python CLI that rewrites JSON files with stable key order and indentation, and exits non-zero on invalid JSON so it can run in pre-commit.
First impression
The first 20 lines hold the name, a one-line description, two badges and a GIF of the tool reformatting a file. A visitor knows what it does within the first three lines.
[IMPORTANT] INSTALLATION: the install command names a different package
- What is wrong: line 14 reads
pip install tidy-json, butpyproject.tomlline 2 declaresname = "tidyjson".
Why it matters here: the first command a visitor copies installs nothing, or an unrelated package, before they have seen the tool run.
- Fix: change line 14 to
pip install tidyjson.
[OPTIONAL] CALL_TO_ACTION: no next step after the example
What is wrong: the README ends at the usage example on line 41, with no link to the pre-commit hook in .pre-commit-hooks.yaml.
- Fix: add a "Use it in pre-commit" section with the hook id.
Unverified, worth checking
- Windows line endings may be rewritten on save. Settle it by formatting a CRLF file and inspecting it with
od -c.
Step 3: Positioning
- Tagline: Stable key order for JSON, so diffs show real changes
- GitHub About description: keep it. It says what the tool is in the first five words.
- Topics: add these.
json,formatter,cli,python,pre-commit,code-review
Key benefits: exits 1 on invalid JSON, so CI fails early (proof: tests/test_exit.py); ships a pre-commit hook (proof: .pre-commit-hooks.yaml).
5. What I did not claim: no speed claim (no benchmark in the repository), no user numbers.
Summary
- Correct the package name on README line 14.
- Add the six topics above.
- Add a pre-commit section to the README.
I can apply the README fixes if you want. I have not edited anything. To add the topics, run:
gh repo edit acme/tidyjson --add-topic json --add-topic formatter --add-topic cli --add-topic python --add-topic pre-commit --add-topic code-review
Connects securely to your tools. The creator never sees your data.
About this skill
Before you post your project anywhere, the README decides whether visitors stay. Orviqa Lite checks it the way a careful evaluator would.
- Health check: a script checks the README, licence, docs, examples, tests, CI and community files, plus the GitHub About description, topics and releases if the GitHub CLI is signed in. Anything it cannot see is reported as unknown, never as missing.
- README audit: eleven areas, including whether the quick start would run on a clean machine. Every finding quotes the line it is about and says what it costs you.
- Positioning: a tagline, About description and topics. Every benefit points to a file in your repo. If what you have is already good, it says keep it.
It opens with a verdict: Ready, Ready after N fixes, or Not ready yet.
It runs locally with your own agent, needs no API keys, and never edits a file or changes your GitHub repository without asking. The bundled script reads your repository's files and, through the GitHub CLI if installed, that repository's public metadata. Nothing is sent anywhere else.
The last line of every answer links to Orviqa, the full product this skill comes from.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Does not run your install or quick-start commands: the quick start is checked by reading the README and manifests, and anything that needs a run to confirm is listed as unverified. Without a signed-in GitHub CLI, the About description, topics, homepage and releases are reported as unknown.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 19 days ago
- Free with an Agensi account
- Software
Python 3.8+
- Optional
GitHub CLI