Portfolio Scorecard
Paste your actual project README. This tool reads it — checks for the sections that matter, flags vague language, and looks for real evidence. No self-grading, no guessing.
Use this after you’ve drafted a README, before you publish it publicly — it checks the same seven-section structure taught in the README Template, and every result comes with specific fixes, not just a score.
What We Found
Want this scored again after you fix it, or a copy of these results?
Why real analysis instead of self-report
Most “portfolio scorecard” tools work by asking you questions about your own work and letting you grade yourself — which mostly just reflects back whatever you already believed. This tool works differently: it reads your actual README text and checks it against the same structure real hiring managers look for, the same way a strict but fair reviewer would.
That means the score isn’t a mood ring. If a section is missing, it’s missing because the text genuinely doesn’t contain it — not because you answered a multiple-choice question about it.
What it actually checks
Three things, each scored separately so you know exactly where to focus:
Section Completeness
Scans for the seven sections a strong README needs — problem, tools, steps, findings, skills, and reflection — and flags which ones are missing or too thin.
Evidence & Specificity
Checks for real numbers, named tools, and screenshot references. “I detected some failed logins” scores lower than “47 failed attempts from one IP in 90 seconds.”
Clarity & Depth
Flags vague filler phrases (“various tools,” “several steps”) and checks the write-up has enough substance to actually be evaluated.
Here’s what that actually looks like in a real README — same project, two different ways of writing the Findings section:
“I detected some failed login attempts and set up an alert for it.”
“Detected 47 failed login attempts from one IP within 90 seconds and triggered a saved Splunk alert.”
Same event, same project — but only one gives a hiring manager something concrete to evaluate. This is exactly the kind of gap the Evidence & Specificity score is built to catch.
Don’t have a project documented yet? Grab the free README Template first, then come back and score what you write.
Frequently asked questions
Does this tool store or share my README text?
No. The analysis runs entirely in your browser — nothing is sent anywhere unless you choose to email yourself a copy of the results.
Is this powered by AI?
No — it’s rule-based text parsing (checking for specific sections, numbers, tool names, and vague phrasing), not an AI model. That means the scoring is consistent and explainable, not a black box.
What if I don’t have a project documented yet?
Use the sample README button above to see how the tool works, then grab the free README Template to write your first one — you can come back and score it once it’s done.
Does this work for non-SOC projects, like GRC or cloud security?
Yes — the scoring checks for structure and evidence, not a specific technology, so it works for any project type as long as it follows the seven-section README format.