portfolio-audit
Skill0 starsChanged 3 days agoMITView on GitHub
Audits the user's public GitHub repositories against a 10/10 quality bar when they ask to "audit my portfolio", "score my repos", "check repo quality", "which repos need improvement", or want a fix-plan for missing README/LICENSE/CI/tests. Use this skill whenever the user wants to evaluate or raise the quality of their public repos.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- imMamdouhaboammar/portfolio-interviewtheir own version, first seen Sep 24, 2026
- nolte/claude-sharedtheir own version, first seen Aug 28, 2026
- trac3r00/agent-skillstheir own version, first seen Aug 26, 2026
- ssurmic/claude-investment-skillstheir own version, first seen Jun 11, 2026
- atifmanzoorali/portfolio-audit-skilltheir own version, first seen Jun 4, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- imMamdouhaboammar/portfolio-interview★ 2same name
- ssurmic/claude-investment-skills★ 1same name
- atifmanzoorali/portfolio-audit-skill★ 0same name
- nolte/claude-shared★ 0same name
- trac3r00/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- ai-infra-helperSkill
- humanizerSkill
- job-applicationSkill
- job-huntSkill
- pr-draftSkill
- resumeSkill
- social-mediaSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Identify repos to audit: Ask the user (or accept as input) for either:
- Distinctive: line 36
Do not push or commit anything without explicit user confirmation.
- Very specific: line 37
When auditing remote GitHub repos, prefer gh CLI.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Portfolio Quality Audit
When to Use
- User asks to audit, score, or quality-check their public repos.
- User wants a fix-plan for missing README, LICENSE, CI, tests, examples, etc.
- User is preparing repos for a job hunt and wants them at 10/10 quality.
How to Use
- Identify repos to audit. Ask the user (or accept as input) for either:
- A list of local repo paths (e.g.
e:\CodingWorkplace\sglang-fork), OR - Their GitHub username (fetch the public repo list via
gh repo list <user> --public --limit 100).
- A list of local repo paths (e.g.
- For each repo, run
scripts/audit-repo.sh <path>to gather signals, then score against the criteria inreferences/quality-bar.md. - Score each repo 0–10 with a per-criterion breakdown. The criteria are:
- README quality (exists, has install/run/usage, has examples or screenshots)
- LICENSE present
- CI present (
.github/workflows/) - Tests present (
tests/,test/,*_test.py,*.test.js, etc.) - Examples directory
- CONTRIBUTING.md
- CODE_OF_CONDUCT.md
- .gitignore appropriate for the language
- Repo description + topics set on GitHub
- Releases / tags (for libraries)
- Output a prioritized fix-plan as markdown: rank repos by lowest score, list specific missing items per repo, mark each as
[easy]/[medium]/[hard]. - Offer to auto-fix easy items (add LICENSE, scaffold README, add .gitignore) — only after explicit user confirmation. Use the templates in
templates/readme-scaffold.md. - Save a snapshot to
references/portfolio-snapshot.mdwith date, scores, and fix-plan so progress is trackable over time.
Rules
- Do not push or commit anything without explicit user confirmation.
- When auditing remote GitHub repos, prefer
ghCLI. If unavailable, ask the user to clone locally first.
References
references/quality-bar.md— the 10/10 criteria (authoritative).templates/readme-scaffold.md— README template for auto-fixes.scripts/audit-repo.sh— repo signal gatherer.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

