What people actually say about Tessl
77 mentions across 4 sources · 55% positive · researched Oct 10, 2026
Hacker News, YouTube, Product Hunt, Lemmy
What users praise
- • Evals run agents on real tasks with and without context, producing before/after evidence — the feature users call out most.
- • Skills-registry-and-package-manager framing resonates: versioning, rollback, and installs feel like npm for agent skills.
- • Works across Claude Code, Cursor, Codex, Antigravity, Copilot, and Gemini, so it fits real teams, not a single vendor.
What frustrates them
- • HN reaction has cooled: the spec-driven-development wave that included Tessl feels past its hype peak.
- • Several prominent HN threads are founder-authored, which makes independent validation of benchmark claims difficult.
- • Aimed at org-scale problems — solo devs and small teams get little value from governance/observability.
This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Tessl review.
What comes up again and again about Tessl
Recurring themes across everything we collected, with where each one showed up.
Skills are the new code, and Tessl is the package manager for them
praised · seen on Product Hunt, Lemmy, Hacker News
Evals are the killer feature — teams want before/after evidence, not vibes
praised · seen on Product Hunt, Lemmy
Spec-driven-development hype has cooled; Tessl is grouped with Kiro and Spec-Kit
criticised · seen on Hacker News
Founder credibility (ex-Snyk) carries weight with security and platform buyers
praised · seen on Product Hunt, Hacker News
Governance, RBAC, and Snyk-backed security scoring anchor the enterprise story
praised · seen on Product Hunt, Hacker News
Tooling in the broader agent ecosystem burns too many tokens on mid-sized projects
mixed · seen on Hacker News
How hard is Tessl to learn?
Users describe it as advanced · typically A few hours to get going
Where people get stuck
- • Meaningful value requires connecting SCM accounts and mapping repos across workspaces
- • Setting up RBAC, install/publish policies, and mandated org-standard skills takes configuration
- • Understanding the credit consumption model for evals and agent runs requires trial and error
- • Six-component surface area (registry, governance, evals, observability, context/findings, Tessl agent) needs onboarding
Who Tessl actually suits
Works well for
- • Platform engineering teams managing skills across multiple coding agents
- • Security leaders who need RBAC, audit logs, and Snyk-backed scanning on agent context
- • Organizations with 20+ developers where skill sprawl and stale versions cause real drift
- • Engineering leaders rolling out org-standard skills across Claude Code, Cursor, and Copilot
Not the right fit for
- • Solo developers and small teams — free tier and pricing assume org scale
- • Hobbyists experimenting with skills who don't need governance or evals
- • Teams running fully custom, non-supported agent frameworks outside the listed integrations
- • Anyone looking for a coding agent itself — Tessl governs agents, it isn't one
What people are discussing right now
Discussion volume is medium and trending stable
- Package-manager framing for agent skills
- Evals and before/after evidence for skills
- Credibility of founder Guy Podjarny (ex-Snyk)
- Whether spec-driven development was a fad
- Governance and security scanning of agent context
- Benchmark claims about decision models vs LLM-as-a-judge
What people really think about Tessl
A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.
What's inside your Tessl report
Everything you need to decide — distilled from real, current user opinion.
Live mentions
The actual posts, reviews & complaints about Tessl — with links and dates.
Honest verdict
A straight answer on whether it lives up to the hype — and who it’s really for.
Praise & gripes
What users genuinely love and the frustrations that keep coming up.
Real quotes
Representative voices from real users, not marketing copy.
Recurring themes
The patterns across hundreds of opinions, surfaced at a glance.
Red flags
Hidden costs and dealbreakers people only discover after signing up.
How it works
Sign up free
Create an account in seconds — get 5 free scans, no card.
We sweep the web
Live social media, forums, reviews & video opinions — in ~30–60s.
Get your report
An honest, downloadable verdict with the real mentions behind it.
Ready to see the real verdict on Tessl?
Your scan is ready in under a minute · $1.
Top alternatives to Tessl
Researching options? Explore the closest alternatives.
Endor Labs
Agentic application security that governs AI coding agents and verifies reachable vulnerabilities before code ships
Poolside AI
Poolside builds open-weight agentic coding models — Laguna XS 2.1 (33B) and Laguna S 2.1 (118B) — for code that stays inside your security
Zhipu GLM
Zhipu GLM is a full-stack large-model platform built on open GLM weights, with MaaS APIs, ZCode and shipped computer-use agents.
Future AGI
Agent evaluation platform that simulates voice and chat agents, traces production, and scores hallucinations before your customers hit them
Imbue
Imbue builds inspectable coding-agent tools: mngr for parallel agent runs, Latchkey for HTTP permissions, and Studio as a personal AI OS.
Pipedream
Pipedream is the integration layer for AI agents: managed auth and 10,000+ tools across 3,000+ APIs.
Check sentiment on these too
Run a live scan on the alternatives before you decide.
Tessl — questions buyers ask
What do people complain about most with Tessl?
The complaints that recur most often are HN reaction has cooled: the spec-driven-development wave that included Tessl feels past its hype peak, several prominent HN threads are founder-authored, which makes independent validation of benchmark claims difficult and aimed at org-scale problems — solo devs and small teams get little value from governance/observability. Drawn from 77 mentions across 4 sources.
What do users like about Tessl?
Users consistently praise evals run agents on real tasks with and without context, producing before/after evidence — the feature users call out most, skills-registry-and-package-manager framing resonates: versioning, rollback, and installs feel like npm for agent skills and works across Claude Code, Cursor, Codex, Antigravity, Copilot, and Gemini, so it fits real teams, not a single vendor.
Is Tessl hard to learn?
Users describe it as advanced; most people are up and running in a few hours; the usual sticking points are meaningful value requires connecting SCM accounts and mapping repos across workspaces and setting up RBAC, install/publish policies, and mandated org-standard skills takes configuration.
Who should not use Tessl?
Based on what users report, it is a poor fit for solo developers and small teams — free tier and pricing assume org scale, hobbyists experimenting with skills who don't need governance or evals and teams running fully custom, non-supported agent frameworks outside the listed integrations.
What are people saying about Tessl right now?
Discussion volume is medium and trending stable. Current topics: package-manager framing for agent skills, evals and before/after evidence for skills and credibility of founder Guy Podjarny (ex-Snyk).
How current is this report?
Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.
Can I download it?
Yes — download the full report as a polished, shareable PDF.