Paste a GitHub link or describe the role. ViewSkill reads the code developers actually shipped and returns a 0 to 100 score, verified skills and a plain-English verdict in about 30 seconds.
Why technical screening breaks down
Most developer assessment tools start after you already have a candidate: they send a test and wait. The slow, expensive part is earlier, deciding who is worth testing, and that still falls on recruiters reading CVs full of the same keywords.
Engineers end up doing first-round screens they don't have time for, or recruiters pass candidates on with no real signal. Either way, the funnel fills with people who look right on paper and stall at the technical interview.
What the tool does
30-second GitHub check
Paste any GitHub profile. Get a score, verified skills from Familiar to Expert, recent activity and a verdict you can forward to the hiring manager.
Search by plain-English role
Describe the job. ViewSkill searches GitHub for developers who built that stack and ranks them, with the reason for each.
Take-home coding tests
Pick from role-specific templates. Submissions are graded automatically on whether the code works, how clean it is and how well it is built.
Contacts and outreach
Find the public contact a developer published and draft a personal first message that references their real work.
Inside ChatGPT and Claude
Run the same checks from your AI assistant over MCP, so screening fits the tools you already use.
Evidence, always linked
Every claim points back to the repository it came from. Nothing is inferred from job titles.
How ViewSkill compares with other developer assessment tools
| ViewSkill | Test-only platforms | CV keyword search | |
|---|---|---|---|
| Works before the candidate applies | Yes, from public code | No | Yes |
| Evidence you can check | Repos linked per skill | Test result only | Self-declared |
| Needs an engineer to read it | No, plain-English verdict | Sometimes | Yes |
| Candidate effort | None for the first check | Hours of testing | None |
| Coding test when you need it | Yes, graded 0 to 100 | Yes | No |
Screening a developer, step by step
- 01
Paste a link or describe the role
A GitHub URL for a candidate you have, or a sentence for candidates you need to find. - 02
Read the verdict
Score, verified skills and a plain-English summary. Enough to decide whether to move forward. - 03
Test the shortlist
Send a graded take-home test only to the people worth an engineer's time.