skillsync

skillsync

Discover hidden talent in your codebase

373 followers

Skillsync analyzes your codebase to find domain experts, discover unique skills, and capture successful patterns. No surveys needed—just timely insights that help you scale what works across your team.
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
skillsync gallery image
Free Options
Launch Team / Built With
ace.me
ace.me
Your new website, email address & cloud storage
Promoted

What do you think? …

Narayana Aaditya

👋 hey product hunt!

open source powers the internet — but the contributors behind it are still underrated.

most platforms reduce effort to green squares and PR counts.

they miss the deeper signals and unique expertise of the contributors.

we built skillsync to change that.

it reads your real work — pull requests, reviews, comments — and builds a living skill graph.

not just what you did, but how you think, collaborate, and contribute.

with skillsync, you can:

  1. discover hidden talent in your codebase

  2. find the right experts for the right problems

  3. scale unique skills with repeatable playbooks

  4. even build your own agents on top of real team intelligence

we believe engineering is more than just shipping fast —

it’s about judgment, care, empathy, and craft.

skillsync helps make that visible.

try it on your favorite open source repo — or connect your own.

excited to hear what you think :)
https://sklsync.com

nars
co-founder, skillsync

Sam @CRANQ

This really hits cos SkillSync feels like the recognition open source contributors have deserved for years lol - What I like is that it’s not just always about what you build but also it’s how you think & this finally captures that!

Congrats to the team!!

Narayana Aaditya

@cranqnow I swearr! It's like there's so much good work out there to learn from yet it's barely used :)

Nishant Joshi

@cranqnow If not now, will open source developers ever get recognized? Especially with the increasing usage of AI for writing code. To be honest, OSS deserves a lot of credit for how good AI is :)

Sangamesh Kulkarni
🔌 Plugged in

Loved the product !

Narayana Aaditya

@sangamesh_kulkarni Thanks Sangamesh!

Narayana Aaditya

@sangamesh_kulkarni Also special shoutout to you for helping us meet @nachiketh10 :)

Supa Liu

Skillsync offers a thoughtful way to surface hidden expertise and elevate team performance without interrupting the workflow. It’s a smart step toward more adaptive, insight-driven engineering culture.

Narayana Aaditya

@supa_l Thank you! which OSS projects are on your hitlist :)

Egret

Loved it!

Narayana Aaditya

@egret_studio Thank you :)

Nishant Joshi

Thanks @egret_studio !

@egret_studio Thankyou

Neeraj Kumar
💡 Bright idea

This is quite interesting, so this analyzes working styles too? What does that even look like in practice?

Narayana Aaditya

@neeraj_kumar_n Haha that's a great question, this is internally our most debated topic: is it even possible to infer working styles or behavioral inclinations from code? The answer is a yes and a no! While the entire spectrum of competencies / behavioral skills is much much more nuanced and dependent on many factors, there are a few practical cues that can be picked up from code! We currently look at the scope of work, whether it is narrow or broad on one side and whether someone is more execution oriented vs exploration oriented in their approach. To test this, we conducted behavioral interviews with quite a few contributors and we were able to reliably predict their working styles! You can check out the schema for this approach here: https://github.com/gasby-co/skill-schema

Evgenii Zaitsev
💡 Bright idea

This is a really powerful idea! I’m really curious about the AI-driven insights part - could this tool help even in early-stage projects where some contributors may still be learning or adapting?

Narayana Aaditya

@evgenii_zaitsev1 You bring up an interesting point because the number of lines of code each developer would be 'accountable' for is increasing exponentially even if the team size isn't. Things can quickly spiral out of control. Especially if a few team members are still learning, they could be brought up to speed pretty quick if you can create a playbook out of the desired skill levels!

1234
Next
Last