Activity
Stars and mentions · Last 30 days, Oct 20 – Nov 18
Top repositories
jlcoto’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside jlcoto’s account where jlcoto opened or reviewed pull requests in the past 365 days.
Who noticed jlcoto
Everyone who starred or forked jlcoto’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories jlcoto owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
Trusting your data agent Now that we are all rushing to use agentic analytics, something that personally concerns me is whether agents are accurate. For this reason, I built an open source tool called the honest agent. You can hook it to your mcp and run your tests (evals) and check whether your agent is, well, telling you the truth. You can check the project here: thehonestagent.dev and here's the repo jlcoto/the_honest_agent. If you already work with dbt, the setup and workflow will seem very familiar 😉 I'm also writing a series of posts on evals in and why they should be a part of your data strategy if you are using data agents: thehonestagent.dev Your feedback is really appreciated. And if you want to discuss agentic analytics, evals, etc, let's connect! Report on evals from the honest agent