Is this person proficient? Answered six ways, from their own code.
How well you write each language
Idioms used well, such as errors wrapped with %w in Go or dataclasses in Python, and how cleanly you write: security, type safety, clean code, language usage, and complexity. Twelve languages, read with real parsers.
- go
- python
- typescript
- javascript
- rust
- c
- c++
- c#
- java
- kotlin
- swift
- dart
What kinds of systems you build
From the libraries your files import: cloud services, integrations, APIs, messaging, data, auth, infrastructure, AI, mobile. Areas that appear together name the kind of work, such as cloud integration.
design.cloud 71 repos gcp firebase aws
design.integration 51 repos http slack
profile: cloud integration, platformAI work that holds up
Agent-written code compared with your own in each language, and how often either needed a fix within 90 days. Using agents is never a weakness; worse results are.
go ai-assisted [n] / 1k lines
your own [n] / 1k lines
durability: [x]% vs [y]% fixedHabits a team would notice
Larger changes committed with tests, the quality gates your CI runs, and commit messages that explain why.
testing 46 23% of changes
quality gates 64 19 repos
commit messages 55 10% explainedHow you brief agents
With --sessions, from local Claude Code, Codex, and Copilot transcripts: verified changes, first-time-right tasks, and whether you explain goals and limits. Counts only; prompt text never leaves.
verified changes [x]% of tasks
explains the goal [x]% of requests
sets limits [x]% of requestsShow it where people look
Badges for READMEs, a portfolio card for your site, and a public JSON API. Each links back to the evidence, shows its trust tier, and shows only what you published.
See badges and embeds →Check any public repo before you run it
Free, no account. Install hooks, data collection, credential access, obfuscation, and supply-chain risks.