AI tool comparison
GuppyLM vs Skrun
Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.
Developer Tools
GuppyLM
A 9M-param fish LLM that teaches you how transformers actually work
75%
Panel ship
—
Community
Paid
Entry
GuppyLM is a deliberately tiny language model — 9 million parameters, 6 transformer layers — that roleplays as a fish and can be fully trained in under 5 minutes on a free Google Colab T4 GPU. The entire pipeline from data generation to training loop to inference fits in approximately 130 lines of PyTorch, making it the most compressed end-to-end LLM tutorial available. Unlike educational projects that paper over complexity with abstraction layers, GuppyLM deliberately avoids modern optimizations — no RoPE positional encoding, no grouped-query attention, no SwiGLU activations. You see exactly why each component exists when you remove it. It ships with a 60,000-example synthetic conversation dataset and produces coherent (if goofy) fish-themed responses after training. The project hit the top of Hacker News Show HN with 365 points and 31 comments. Developers praised how the simplicity forces you to confront how training data shapes model behavior directly, with multiple commenters saying it's the clearest path from 'I know Python' to 'I understand why LLMs work.'
Developer Tools
Skrun
Deploy any agent skill as a production REST API in one command
50%
Panel ship
—
Community
Paid
Entry
Skrun is an open-source tool that wraps agentic skills — the discrete, reusable capabilities you build for AI agents (web search, data extraction, file transformation, API calls) — into deployable REST APIs with a single command. The idea is that skills you build for one agent context shouldn't be locked to that agent's runtime. With Skrun, you define a skill once with a standard function signature, and get a hosted endpoint with automatic request validation, retry logic, rate limiting, and an OpenAPI spec generated automatically. The project addresses a real architectural tension in the current AI tools ecosystem: agent skills are written in a dozen different formats (LangChain tools, MCP tools, function call JSON, OpenAI tool specs) and are essentially stranded assets — they only work within their specific orchestration framework. Skrun normalizes this by wrapping any skill definition format and exposing it as a framework-agnostic HTTP endpoint that any agent or pipeline can call. This appeared on Hacker News with a small but thoughtful discussion focused on the "skills as microservices" architectural pattern. Critics noted that adding HTTP round-trips to every tool call introduces latency; proponents argued that the composability and reusability benefits outweigh the cost. The early version focuses on stateless skills; stateful/conversational skill deployment is on the roadmap.
Reviewer scorecard
“130 lines from raw data to inference — I've never seen a more honest on-ramp to transformer internals. The deliberate omission of RoPE and SwiGLU forces you to understand the delta between vanilla and modern architectures. Assign this to every junior ML engineer before they touch Hugging Face.”
“The framework portability angle is the real value prop — I have dozens of custom tools built for Claude that I can't reuse in other contexts without rebuilding them. If Skrun actually normalizes this cleanly across tool formats, that's a genuine pain solver.”
“This is education, not tooling — calling it a 'language model' is generous for something that outputs fish puns. The synthetic training data is simplistic and the architecture is years behind real LLMs. Fine for learning, but don't confuse novelty with utility.”
“Wrapping every agent skill in an HTTP call is a latency antipattern — a skill that takes 50ms locally becomes 120ms+ through a hosted endpoint with cold starts. For skills called hundreds of times per agent run, this adds up fast. I'd want colocation support before using this in production.”
“The best thing about GuppyLM is that it normalizes building your own models from scratch. As AI democratizes, the next generation of builders needs to understand transformers at the implementation level — not just prompt them. This is exactly the kind of artifact that spawns a thousand domain-specific tiny models.”
“Skills-as-services is the right architectural direction as agent ecosystems mature. The future is marketplaces of composable agent capabilities that any orchestrator can call — Skrun is early infrastructure for that world.”
“A fish that learned to talk about water from 60K synthetic conversations is unexpectedly charming. The project has a clear personality and a memorable hook — it's the kind of thing that goes viral in classrooms because students actually want to run it. Clever branding for an educational tool.”
“Too deep in infrastructure for my workflow, but the auto-generated OpenAPI spec is a nice touch for anyone who needs to share custom skills with a team without writing documentation manually.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.