What proof of work means on Skilion
How evidence-backed skills, badges and endorsements work, and what they do not promise.
5 min read · Updated 10 October 2026
Claims and evidence are different
On Skilion a skill you list is a claim until you link it to a project that uses it. Skills with project evidence are marked, so a visitor can tell the difference at a glance.
What each badge checks
Email: you control the email address. Google or GitHub linked: you signed in with an account whose email the provider verified. Repository owner: you own the repository linked on a project. Peer endorsed: another member vouched for a skill after working with you. Identity checked: a verifier reviewed an identity document.
No badge says more than that. A GitHub link does not prove you wrote every line in a repository, and an endorsement is an opinion.
Showing work well
Lead with two or three projects. For each one say your role, the contribution type (personal, collaborative or client), the tools and the outcome. Link a demo or repository. Private client work can be listed without links.