Your skills, and which ones anything backs up
Paste your resume. This finds every skill it can, groups them, and separates what you describe doing from what merely appears in a list.
Your skills, and which ones anything backs up
Paste your resume. This pulls out every skill it can find, groups them, and separates the ones you describe doing something with from the ones that only appear in a list.
Listed, with nothing behind it
How a skill is found and classified
Two passes. Anything in your skills section is split on its delimiters and taken as listed. Separately, every term in the built-in taxonomy is searched for across the whole resume, so a skill you demonstrate but forgot to list still shows up.
Evidence is located by section. A term in your experience or projects counts; the same term in a comma-separated list does not, because a list can be padded in thirty seconds and an interviewer will go to the experience section to check.
The taxonomy is deliberately small. Anything it does not recognise is reported as unclassified rather than forced into a category, because a wrong category reads as a judgement about the skill.
A long skills list is a weak signal
Everyone knows it can be written in a minute, so everyone discounts it. Twelve skills with nothing behind them is worth less than four that appear in something you describe doing.
The useful test is the one on this page: for each term in your list, can you point at a line elsewhere in the resume where you used it? If not, either add that line or cut the term.
Skills you demonstrate but never listed
The reverse case is common and costs you nothing to fix. If your experience describes running a Postgres estate and your skills line does not say Postgres, a keyword search over the list will miss you.
Where the categories come from
Grouping is a convenience for reading, not an assessment. A skill that lands in "not classified" simply is not in the list this tool carries — it says something about the tool, not about you.