Sahil Lavingia, the founder and CEO of Gumroad, has turned his personal skills inventory into an open-source project on GitHub — and in doing so, has sparked a quiet but meaningful conversation about transparency, self-assessment, and what it means to grow in public.
The repository, simply called “skills” and hosted under Lavingia’s GitHub handle, is exactly what it sounds like: a structured, version-controlled list of the skills he possesses, wants to develop, and is actively working on. It’s a README file. Nothing more. But the implications are far more interesting than the format suggests.
At first glance, the project reads like a personal tracker. Lavingia catalogs competencies across categories — writing, design, engineering, management, among others — and rates himself with a candid, sometimes blunt honesty that most executives would never risk in a public forum. There’s no corporate veneer here. No polished LinkedIn summary designed to impress recruiters. Instead, it’s a living document that admits gaps, acknowledges weaknesses, and invites the world to watch as those gaps either close or persist.
That’s the part that matters.
Lavingia has long been a proponent of building in public. Gumroad, the creator economy platform he founded in 2011, has itself been an exercise in radical transparency — the company has published its financials openly, discussed layoffs candidly, and operated with a level of openness that most venture-backed startups would consider reckless. The skills repository is an extension of that same instinct, applied not to a company but to a person.
The concept isn’t entirely new. Developers have long maintained public dotfiles and configuration repositories. Engineers share their learning paths on GitHub. But a CEO doing it — a founder with a public profile and real stakes — that’s different. It carries risk. Investors, partners, and employees can all see what the person running the company believes he’s bad at.
And yet, that vulnerability appears to be the point.
The repository’s structure is deliberately simple. Markdown. No fancy tooling, no web app, no gamification. Just text organized into sections that reflect how Lavingia thinks about personal development. Skills are grouped loosely, and each one carries a self-assigned proficiency level. Some are marked as areas of active focus. Others sit dormant, acknowledged but not prioritized. The commit history — visible to anyone — shows when entries were added, modified, or removed. It’s a changelog for a human being.
This approach resonates with a broader movement in tech culture that values learning over credentialing. The traditional résumé is a static artifact, a snapshot frozen in time and designed to present the best possible version of a candidate. Lavingia’s skills repo is the opposite. Dynamic. Honest. Sometimes unflattering. It treats professional development as an iterative process — not unlike software itself.
The open-source community has responded with predictable curiosity. Forks of the repository exist, with other developers and professionals creating their own versions. Some have added more structure. Others have stripped it down further. A few have turned it into a template, encouraging friends and colleagues to do the same. The project has become, in a small way, a format — a genre of self-documentation that didn’t exist before.
So why does this matter beyond the personal branding of one Silicon Valley founder?
Because it challenges a deeply held assumption in professional culture: that admitting what you don’t know is a liability. In most corporate environments, competence is performed. Managers project confidence. Executives speak in certainties. The incentive structure rewards appearing capable, not being transparent about capability gaps. Lavingia’s repository flips that dynamic. It says: here’s what I’m working with, here’s where I’m weak, and here’s what I’m doing about it.
The timing is relevant. The tech industry is in the middle of a significant reckoning with how it evaluates talent. The rise of AI tools has made certain technical skills less scarce while elevating others — critical thinking, taste, communication, the ability to manage ambiguity. Traditional skill taxonomies are breaking down. A public, evolving skills document may actually be a more useful signal of a person’s trajectory than a degree or a job title.
Lavingia himself has written extensively about the future of work, the creator economy, and the value of small teams. His 2020 book, The Minimalist Entrepreneur, argued for building businesses that are profitable, sustainable, and human-scaled. The skills repository fits neatly into that philosophy. It’s minimal. It’s sustainable — requiring only occasional updates. And it’s human in a way that most professional self-presentation is not.
There are limitations, of course. Self-assessment is inherently subjective. Lavingia’s ratings of his own abilities are just that — his own ratings. There’s no external validation built into the system, no peer review, no 360-degree feedback mechanism. A cynic might argue that the whole exercise is performative humility, a carefully curated display of vulnerability designed to generate goodwill and social media engagement. That criticism isn’t entirely without merit. But it also misses the larger point: even if the motivation is partly strategic, the format itself is genuinely useful.
Consider the alternative. Most professionals have no structured way to track their own development over time. They rely on annual performance reviews — if they get them at all — or vague personal goals that fade by February. A version-controlled skills document, even a private one, would give anyone a clearer picture of where they’ve been and where they’re headed. Making it public just adds accountability.
The repository also raises interesting questions about what counts as a “skill” in the first place. Lavingia includes items that traditional HR frameworks would never categorize as competencies — things like taste, judgment, and the ability to say no. These are soft, squishy, hard-to-measure qualities. But they’re often the ones that determine whether a founder succeeds or fails. By including them alongside more conventional entries like “Python” or “financial modeling,” Lavingia is implicitly arguing that the distinction between hard and soft skills is less meaningful than we pretend.
GitHub, as a platform, adds an unexpected layer of meaning to the project. Version control — the core technology underlying Git — was designed to track changes to code over time. Applying it to personal development creates a metaphor that’s almost too perfect: every commit is a small act of self-revision, every diff a record of growth or course correction. The medium is the message, as Marshall McLuhan might have said. And the message here is that people, like software, are never finished.
Other founders and public figures have experimented with similar ideas. Some maintain public “now” pages — a concept popularized by Derek Sivers — that describe what they’re currently focused on. Others publish annual reviews or quarterly goals. But few have used a developer tool like GitHub to do it, and fewer still have framed the exercise as open-source, explicitly inviting others to fork and adapt the format for themselves.
The project has no license file, no contributing guidelines, no issue tracker full of feature requests. It’s not trying to be a product. It’s trying to be an example. And in that simplicity lies its power.
Whether Lavingia’s skills repository becomes a widely adopted practice or remains a niche curiosity is beside the point. What it demonstrates — that transparency about one’s own capabilities can be a strength rather than a weakness, that professional growth can be tracked with the same tools we use to build software, and that vulnerability and leadership are not mutually exclusive — is worth paying attention to. Especially now, when the definition of what makes someone valuable in the workplace is shifting faster than most people can keep up with.
The repo sits there on GitHub, public and unadorned. Forty-odd lines of Markdown. No pitch deck. No manifesto. Just a person saying: this is where I am. Fork it if you want.
WebProNews is an iEntry Publication