- Home
- Skills
- Technical Documentation
- Repo Taste
Repo Taste
Ship GitHub repos with generated architecture maps, honest READMEs and diagrams that never lie.
$7.99
Works with the AI Agents you already use
Repo Taste
Example session with this skill installed
My repo's README is vague and the architecture diagram is hand-drawn and out of date. Regenerate the diagram from the actual source and rewrite the README so it only claims what's really built, then check it's safe to push.
- Read your context and instructions
- Compiled the repo taste
Example session (illustrative; file names and counts come from your repo).
1. Architecture map from source
I ran the map generator over the repo. It parsed the source files and wrote:
- docs/architecture.svg: modules as boxes, imports as arrows, laid out so nothing overflows its box
- docs/SYMBOLS.md: every public type and function with a link to its exact file and line, so the index can't drift from the code
2. Visual check
I rendered a contact sheet of every SVG in docs/ and looked at it before committing. One label was clipped, so I shortened it and re-rendered.
3. README rewrite
The new structure
- What it is, in one sentence
- What's actually built, as a short list with each item linked to its module in the map
- How to run it, with commands copied from the real scripts
- What I learned the hard way (the gotchas)
- Status and limits, stated plainly
I removed two claims the code doesn't back up.
4. Pre-push check
- No API keys, tokens or .env files staged
- No absolute personal paths such as /Users/<name>/ left in the docs or scripts
- Diagrams regenerated from the current commit
Next steps
- Add the map generator to a pre-commit hook so the diagram updates on every change.
Connects securely to your tools. The creator never sees your data.
About this skill
Repos generated by agents often ship diagrams nobody looked at and READMEs that overclaim. This skill gives your agent a craft standard and the tools to meet it.
A source-derived map generator parses Swift, Python, TypeScript, Go and Rust, then emits an architecture SVG plus a symbol index with real line-anchored links that cannot drift. An SVG design system has primitives that refuse to overflow. A contact-sheet renderer forces a visual check before you commit. The README structure leads with what is actually built and what you learned the hard way. A pre-push checklist catches leaked secrets and personal paths.
Use cases
- Generate an accurate architecture diagram from source
- Rewrite a README so every claim has a number or a diagram
- Produce consistent, proportional SVG charts for a project
- Run a pre-publish check for secrets and personal paths
Requires Python 3. Architecture mapping supports Swift, Python, TS/JS, Go, and Rust. SVG verification requires a headless browser to avoid common OS-level rendering traps.
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 any payment.
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
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires
Permissions
Reads your source to build the map and writes SVG and Markdown files into docs/.