The clean-resume output was moderately usable: the basics were correct, but certifications and GPA were missing and the responsibilities/skills sections still showed formatting artifacts.
What was measured
Output quality
Is the parsed result clean, complete, and usable overall?
decisive for this rankingtransformation
The whole point is usable structured extraction; clean, complete, usable output is the core measure of success. (3 of 3 judges)
What was given, what came back
Test input: Clean single-column resume — Rugved Nichite · pdf · group: resume-parsing
Input — what we sent
Clean single-column resume — Rugved Nichite
A professionally structured single-column resume for Rugved Nichite, used as the baseline input for parser accuracy across standard resume fields.
Why this input is hard
- · baseline field extraction
- · contact info accuracy
- · work experience parsing
- · education and CGPA extraction
- · skills and certifications extraction
Output — unretouched
Also checked on this input — same tool, 4 other criteria
Accuracy✓ WorkedThe core extracted values were correct on the clean resume, including Rugved Nichite, rugved.nchite@email.com, 9876500000, Vasind, the work histories, the education details, and the 2.9-year total experience figure.Field coverage✓ WorkedOn the clean resume, the parser returned the six core fields expected for resume coverage: name, email, phone, work experience, education, and skills.Noise in output✗ FailedThe skills field collapsed into one unspaced concatenated string, so the output was not machine-readable as separate skill items.Noise in output✗ FailedThe parser preserved raw bullet/number formatting in responsibilities, leaking duplicated bullet characters into the extracted text.
Provenance
- Observation
- 466848f3-01a1-45a4-9d9a-7392fad7c254
- Evidence run
- cbbef4db-964c-49fa-a57f-a2977822bdfc
- Study
- Parse resumes into structured data using an API
- Research task
- 86b9jm30n
- Tested at
- not recorded
- Source
- first-party
- Evidence state
- verified
- Proof shown
- input + output shown
- Cost / latency
- not captured
- Repeat run
- not captured
- Tester
- not captured
The last three rows are honest blanks, not placeholders — our capture has no field for them yet.
Query this
get_evidence({
tool: "skima-ai",
scenario: "resume-parsing"
})MCP · mcp.aidemos.com/api/mcp
Free with attribution.
Same input, same check — 7 other tools
measured on Output quality
Airparser◐ MixedProduces readable, structured JSON, but the overall parse quality is reduced by a wrong email address and a truncated job title.Extracta.ai✓ WorkedReturns a clean, minimal JSON payload with the core resume sections extracted and no extra metadata noise.Hireability◐ MixedThe clean-resume output was broadly usable, but overall quality was weakened by a split name and flattened skill structure, so the result was not fully clean.HrFlow◐ MixedOverall output is usable, but the clean-resume parse still shows normalization and classification issues.LlamaParse✓ WorkedThe clean-resume output was structurally rich: skills were grouped into categorized arrays, certifications were separate objects with name/issuer/year, and work responsibilities were split into individual array items.OpenResume◐ MixedOn a clean single-column resume, the output is mostly usable but still partial because the Name field is blank and Phone/Location are missing.Parseur◐ MixedCGPA was embedded inside the education string rather than extracted as a dedicated field.
This evidence is published in
Real inputs and real outputs, no retouching · every cell queryable via API & MCP · aidemos.com