<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Scott Shwarts</title>
    <description>The latest articles on DEV Community by Scott Shwarts (@sshwarts).</description>
    <link>https://dev.to/sshwarts</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4037047%2F4829edc7-c94c-4f26-983d-499794f9d461.jpg</url>
      <title>DEV Community: Scott Shwarts</title>
      <link>https://dev.to/sshwarts</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sshwarts"/>
    <language>en</language>
    <item>
      <title>Skillscript – a scripting language for agent orchestration</title>
      <dc:creator>Scott Shwarts</dc:creator>
      <pubDate>Tue, 21 Jul 2026 20:22:20 +0000</pubDate>
      <link>https://dev.to/sshwarts/skillscript-a-scripting-language-for-agent-orchestration-1jeb</link>
      <guid>https://dev.to/sshwarts/skillscript-a-scripting-language-for-agent-orchestration-1jeb</guid>
      <description>&lt;p&gt;Skillscript is a small language I built to write what I want my local agent to actually do, in a form I can read and version, instead of hoping the model gets it right each time.&lt;/p&gt;

&lt;p&gt;The itch started with something small. I wanted my NanoClaw agent to run my morning brief the same way every day. Check overnight tickets, summarize the deploy pipeline, flag anything urgent. Every session, it would re-figure out how to do this from scratch, drift a little, and cost  tokens for what's basically a fixed procedure. I could put it in a system prompt or an MD skill file, but those are still instructions the model reads and reasons about every time. And I wanted it to run autonomously and then hand it to the model to reason over the data.&lt;/p&gt;

&lt;p&gt;The second thing that pushed me: I wanted to use small local models for the cheap stuff. They're capable, but if you just hand them the wheel, they wander. What I wanted was a way for the frontier model (or me) to write a specific procedure and hand it to the local model to execute not interpret. The skillscript is the program; the model is the runtime.&lt;/p&gt;

&lt;p&gt;Skillscript is that. A skillscript is a text file with named steps, variables, conditions, and calls out to tools (MCP connectors, a local model, and shell commands from an operator allowlist). It's deliberately minimal — no eval, no arbitrary imports, no subprocess, no unbounded loops. Bounded language, limited potential for damage. Everything a skillscript can do is in the file. You read it and know.&lt;/p&gt;

&lt;p&gt;Where it is: pre-1.0 (0.37), MCP-native, self-hosted. Rough edges I know about: first-run setup takes more steps than it should, some of the grammar is still moving, and the local model integration currently assumes Ollama. It works well enough that I use it every day, but I wouldn't necessarily call it production-ready.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Repo: &lt;a href="https://github.com/sshwarts/skillscript" rel="noopener noreferrer"&gt;https://github.com/sshwarts/skillscript&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Site: &lt;a href="https://skillscript.ai" rel="noopener noreferrer"&gt;https://skillscript.ai&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Docs: &lt;a href="https://skillscript.mintlify.app/docs" rel="noopener noreferrer"&gt;https://skillscript.mintlify.app/docs&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;npm: &lt;code&gt;skillscript-runtime&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I'd welcome critique on two things especially: the language design (is it too small? too big? wrong shape?) and the trust model around agent-authored skills. What would you want to see before you trusted this on your own machine?&lt;/p&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>automation</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
