A week-by-week record of the technologies you use, and how well you know them.
Drag the chart left or right to explore different time periods.
How it works
Connect Claude, Cursor, Cline, Roo Code or OpenCode to Trekme with MCP (Model Context Protocol). Tell your assistant what you used this week. It updates your record from the chat, so you do not open another tab.
Each week, Trekme can send you a short email with a link to the form. It shows how many weeks in a row you logged, and your rank among all users. At 4, 8, 13, 26 and 52 weeks, you get a milestone.
See which technologies you use now, which you know better each month, and which you stopped using.
You log each week while you work. About two weeks after a week ends, Trekme locks it. Thus you cannot add a skill to last year to match a job ad. In an interview, you can say "62 weeks of Python" and show each week.
Put a short note and your reports on one page. Make it public and add its link to your CV, or print it to PDF.
Your company's skill tracker stays with your company. Your Trekme record stays with you, with every technology from every job. Download any report as PNG or SVG.
For recruiters
A candidate can send a Trekme link with the CV. The link shows each week of their work: the technologies and the level of each one. Here is how to read it.
The link opens a dashboard in your browser. You do not sign up and you do not learn a new tool. It fits into the hiring process that you have now.
"Python, 5 years" on a CV can mean 2015 to 2020. The record shows the last week that the candidate used each technology, and the level in each week.
Eleven technologies in every week? Nobody uses that many in a 40-hour week. A record that is too good gives you your first interview question.
For IT & engineering teams
You pay a lot to build your team's skills. Then you track them in a spreadsheet that is out of date on the day you make it. Trekme shows who uses what, and it updates every week.
Search your team by skill. Set a technology, a minimum level and the last week of use. The best matches are at the top.
A team dashboard puts the team reports and a note on one page.
Pay for a course or a conference. Some months later, see if people still use the skill and know it better. Support your training budget with real numbers.
Find the important skills that only one engineer has, before that person leaves. Then share that knowledge while you can.
Base promotions and reviews on what people did, not on who talks the most.
Got questions?
Keep them. They show your jobs and titles. A skill on LinkedIn has no dates and no level. Trekme adds what they cannot show: how many weeks you used each technology, and at what level.
About two minutes. Select the technologies that you used and set a level for each one.
Not at the moment. Your record starts in the week that you sign up. Your CV still shows the years before that.
No. Most users do not look for a job. They use their record in performance reviews and when they ask for a raise.
We set up your team for you. Then each developer logs their own week, and the team reports update.
An HR matrix or an LMS shows what people signed up for or completed. Trekme shows what your engineers use in their real work, each week.
Developers choose who can see each of their own reports and dashboards: only them, their team, their managers, or everyone. Team reports show only the team members.
Read it together with what you see each day: code reviews, tickets and team meetings. When a record and the work do not agree, start a conversation. Team reports show trends over months, not a test score.