Why I built it: With the rise of "Vibe Coding" and AI tools, shipping new products has never been faster. But that also means "abandonware" is piling up. As a user myself, before I pay for a subscription (or even consider buying a micro-SaaS), I constantly ask myself:
"Is there still an active developer behind this?"
"Is this project alive, or was it abandoned 3 months ago?"
I built GitPulse to answer that. It’s a verified signal for users and buyers to see if a project is actively maintained or stable without exposing the source code.
Features I added for fun & utility:
Gamification: "Shipping Streaks" to keep myself motivated.
Social Sharing: To show off progress publicly or prove activity to clients/buyers.
Smart Context: Distinguishing between "High Activity" and "Stable" (so finished projects don't look dead).
Roadmap: I’m currently working on deeper metrics like Build Stability (CI/CD status) and Package Health, so it’s not just about quantity, but quality.
I am currently in the startup and indie hacker bubble. It increasingly feels like everyone on social media is successful. Every new product seems to launch with polished testimonials, impressive numbers, and traction screenshots.
I think the issue is that most of this is very easy to fake now. AI has made it simple to create convincing copy, reviews, and even full case studies. I often find myself wondering what is actually real.
Trusers is my effort to establish at least one solid signal in reality: paying customers. Not screenshots or testimonials, just verified customer counts and how they change over time.
I truly believe that as AI-generated noise grows, trustworthy data will become more important. This is a small, initial step in that direction.
I am happy to answer questions and welcome feedback.
Hey, I am Kevin the founder of SkillPass.
When I changed roles a few months ago I noticed something interesting. My successor onboarded in a fraction of the time it took me, simply because I was still around to explain everything. But during that offboarding I also realised how hard it actually is to pass on knowledge. I kept thinking, “Where do I even start?” and I was constantly afraid of forgetting important details. That is exactly what I wanted SkillPass to fix. A tool that gives people a clear thread to follow and asks the right questions so they do not have to figure everything out on their own.
Hi and thanks for the feedback, this is exactly the kind of “state of play” snapshot we had in mind initially. We also think there’s a lot of potential if key people from different teams each create one of these and make it available across the company.
Regarding the AI: at the moment SkillPass Pro is still using OpenAI, mainly because we’re in very early development and want to iterate quickly. Longer term, the plan is to move toward self-hosting and reduce external dependencies.
According to OpenAI’s API policies, data sent via the API is not used to train their models. The data is only retained for a short period and solely for service operation and abuse monitoring purposes, after which it is deleted. This was an important consideration for us when choosing this setup for the early stage.
Thanks for confirming the AI provider, it would be good if they were listed somewhere on the site (but that's probably a personal preference). I'm a massive fan of local models, for your use case they'd be more than powerful enough to run on consumer hardware if you have some lying around. If you ever have any questions, feel free to drop me a DM, happy to chat about it.
Thank you so much for your thoughtful feedback! I really appreciate it. The AI provider is actually already mentioned in our privacy policy, but I completely understand that it might not be easy to find. We're considering making that information more prominent on the site.
Thanks again for your willingness to chat and for sharing your local setup. It's always fascinating to see how different people tackle this! If you decide to give it a shot in the new year, I would truly value any feedback you'll have after you've had some time to explore it.
When I changed roles a few months ago I noticed something interesting. My successor onboarded in a fraction of the time it took me, simply because I was still around to explain everything. But during that offboarding I also realised how hard it actually is to pass on knowledge. I kept thinking, “Where do I even start?” and I was constantly afraid of forgetting important details.
That is exactly what I wanted SkillPass to fix. A tool that gives people a clear thread to follow and asks the right questions so they do not have to figure everything out on their own.
Hey, I am Kevin.
When I changed roles a few months ago I noticed something interesting. My successor onboarded in a fraction of the time it took me, simply because I was still around to explain everything. But during that offboarding I also realised how hard it actually is to pass on knowledge. I kept thinking, “Where do I even start?” and I was constantly afraid of forgetting important details.
That is exactly what I wanted SkillPass to fix. A tool that gives people a clear thread to follow and asks the right questions so they do not have to figure everything out on their own.
Happy to answer anything about how I built it or why.
When I changed roles a few months ago I noticed something interesting.
My successor onboarded in a fraction of the time it took me, simply because I was still around to explain everything.
But during that offboarding I also realised how hard it actually is to pass on knowledge.
I kept thinking, “Where do I even start?” and I was constantly afraid of forgetting important details.
That is exactly what I wanted SkillPass to fix.
A tool that gives people a clear thread to follow and asks the right questions so they do not have to figure everything out on their own.
Happy to answer anything about how I built it or why.
