<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>LLMs on Minko Gechev&#39;s blog</title>
		<link>https://blog.mgechev.com/tags/LLMs/</link>
		<description>Recent content in LLMs on Minko Gechev&#39;s blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 14 Mar 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://blog.mgechev.com/tags/LLMs/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>skillgrade</title>
				<link>https://blog.mgechev.com/2026/03/14/skillgrade/</link>
				<pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2026/03/14/skillgrade/</guid>
				<description>&lt;div style=&#34;padding: 15px; border-radius: 5px; background-color:rgb(241 255 240); border: 1px solid #e9e9e9;&#34;&gt;&#xA;⭐ Find &lt;a href=&#34;https://github.com/mgechev/skillgrade&#34;&gt;Skillgrade on GitHub&lt;/a&gt;&#xA;&lt;/div&gt;&#xA;&lt;h1 id=&#34;skillgrade&#34;&gt;skillgrade&lt;/h1&gt;&#xA;&lt;p&gt;A few weeks ago I wrote about &lt;a href=&#34;https://blog.mgechev.com/2026/02/26/skill-eval/&#34;&gt;Skill Eval&lt;/a&gt;, a framework for testing AI agent skills. The idea resonated — skills are becoming a critical part of how teams work with agents, and without a way to measure whether they work, you&amp;rsquo;re guessing.&lt;/p&gt;&#xA;&lt;p&gt;The problem was that Skill Eval required too much setup. You had to clone a repo, understand a specific directory structure, write TypeScript config, and wire everything together before you could run your first eval. The barrier to entry was high for something that should be simple.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Unit Tests for AI Agent Skills</title>
				<link>https://blog.mgechev.com/2026/02/26/skill-eval/</link>
				<pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2026/02/26/skill-eval/</guid>
				<description>&lt;div style=&#34;padding: 15px; border-radius: 5px; background-color:rgb(241 255 240); border: 1px solid #e9e9e9;&#34;&gt;&#xA;⭐ Find &lt;a href=&#34;https://github.com/mgechev/skill-eval&#34;&gt;Skill Eval on GitHub&lt;/a&gt;&#xA;&lt;/div&gt;&#xA;&lt;h1 id=&#34;unit-tests-for-ai-agent-skills&#34;&gt;Unit Tests for AI Agent Skills&lt;/h1&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been working with AI coding agents daily - Antigravity, Gemini CLI, Claude Code, and others. One pattern I keep seeing is teams building &lt;em&gt;skills&lt;/em&gt; for these agents: procedural instructions that teach the model how to use internal tools, follow specific workflows, or comply with team conventions.&lt;/p&gt;&#xA;&lt;p&gt;The problem? There&amp;rsquo;s no way to know if they actually work. You write a text file, hand it to an agent, and hope for the best. When you tweak the instructions, you have no signal telling you whether that change made things better or worse. You&amp;rsquo;re flying blind.&lt;/p&gt;</description>
			</item>
			<item>
				<title>You Should Care About AI</title>
				<link>https://blog.mgechev.com/2025/11/07/you-should-care-about-ai/</link>
				<pubDate>Fri, 07 Nov 2025 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2025/11/07/you-should-care-about-ai/</guid>
				<description>&lt;p&gt;In conversations with developers lately I&amp;rsquo;ve been noticing a lot of discomfort when bringing AI. Talking to people and doing self-reflection I think there are a couple of reasons for this:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Overinflation&lt;/strong&gt;. AI is certainly over hyped by some. People have business interests in raising money or increasing the valuation of their companies and they tend to exaggerated the capabilities of agents and language models. This makes it feel like we&amp;rsquo;re in yet another hype cycle that will pass, so why waste energy?&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Fear&lt;/strong&gt;. Developers see how AI automates some of the tasks they do. Combining this with the overinflation often leads to fear that software engineers will become obsolete. We already see how new grads are struggling to find jobs.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;overinflation&#34;&gt;Overinflation&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been using AI daily in my work over the past couple of years. I&amp;rsquo;ve been using it for coding, scaffolding documents, understanding stack traces, and so much more. It&amp;rsquo;s certainly not perfect and it is certainly over hyped by some. At the same time, there are thousands of use cases that are real and can improve your productivity.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Generative Development</title>
				<link>https://blog.mgechev.com/2025/10/20/generative-development/</link>
				<pubDate>Mon, 20 Oct 2025 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2025/10/20/generative-development/</guid>
				<description>&lt;p&gt;Historically in my blog I&amp;rsquo;ve been posting 10-20 page deep-dive explorations in &lt;a href=&#34;https://blog.mgechev.com/2017/08/05/typed-lambda-calculus-create-type-checker-transpiler-compiler-javascript/&#34;&gt;type theory&lt;/a&gt;, &lt;a href=&#34;https://blog.mgechev.com/2018/10/20/transfer-learning-tensorflow-js-data-augmentation-mobile-net/&#34;&gt;deep neural networks&lt;/a&gt;, &lt;a href=&#34;https://blog.mgechev.com/2018/03/18/machine-learning-data-driven-bundling-webpack-javascript-markov-chain-angular-react/&#34;&gt;predictive prefetching&lt;/a&gt;, etc. Recently, I&amp;rsquo;ve been thinking of taking a new approach with short snippets based on my current thinking about a particular topic.&lt;/p&gt;&#xA;&lt;p&gt;Today, I&amp;rsquo;ll share high-level takes on developer workflows and how they can impact the tools we use.&lt;/p&gt;&#xA;&lt;h2 id=&#34;llms-enable-velocity&#34;&gt;LLMs enable velocity&lt;/h2&gt;&#xA;&lt;p&gt;We can certainly speed up our developer velocity using GenAI. Lately, I&amp;rsquo;ve been consistently using Gemini CLI and Cursor. Currently, I feel resistance when I have to write a piece of trivial logic, like create a login form or a chat interface from scratch. Agentic tools have enabled me to quickly iterate and test hypothesis. In this phase of the development process I rarely need to look at source code, unless something went terribly wrong. My focus in such early stages of exploration is on the output of whatever I&amp;rsquo;m building. Whether I&amp;rsquo;m developing an agent, web UI, or a compiler, I&amp;rsquo;d create multiple prototypes using agentic tools and entirely focus on the output the prototypes without looking at the implementation. Based on the outputs, I decide which prototype I&amp;rsquo;d like to move forward with.&lt;/p&gt;</description>
			</item>
			<item>
				<title>LLM-first Web Framework</title>
				<link>https://blog.mgechev.com/2025/04/19/llm-first-web-framework/</link>
				<pubDate>Sat, 19 Apr 2025 00:00:00 +0000</pubDate>
				<guid>https://blog.mgechev.com/2025/04/19/llm-first-web-framework/</guid>
				<description>&lt;div style=&#34;padding: 15px; border-radius: 5px; background-color: #fff4da; border: 1px solid #ffe88c;&#34;&gt;&#xA;The opinions stated here are my own, not necessarily those of my employer.&#xA;&lt;/div&gt;&#xA;&lt;p&gt;Over the past few weeks I&amp;rsquo;ve been thinking about how we can make a framework easier for AI. In particular I&amp;rsquo;ve been &lt;em&gt;only&lt;/em&gt; focused on building user interface. When we add a backend, database, and communication protocol across the backend and the frontend, we get another set of problems that could be a good fit for another post and exploration.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
