Nixtla on Start AI Tools - Presented by Intent Solutions

CEO Feedback Pivot and the Nixtla Skills Blitz

Sun, 21 Dec 2025 10:00:00 -0600

The fastest way to learn your messaging is wrong is to show it to the person writing the checks.

Lumera Pivots on Terminology

Five commits on Lumera-Emanuel, and the most important one deleted more than it added. The CEO looked at the product description and flagged the WOW terminology — “Wisdom of the World,” a framing I’d been using to describe the agent memory model.

His feedback was direct: it sounded like a marketing tagline, not a technical capability. Worse, it obscured the actual value proposition.

Two Products Bootstrapped from Zero to Release in One Day

Mon, 15 Dec 2025 10:00:00 -0600

December 15th was a bootstrapping day. Two products went from empty directories to tagged releases. Not prototypes. Not “hello world” scaffolds. Actual versioned releases with real functionality.

git-with-intent: 11 Commits Through 7 Phases

git-with-intent is the AI-assisted git workflow tool. On December 15th it went from concept to v0.2.0 across 11 commits.

The phases tell the story:

Phase 1: Core commit analysis engine. Parse git history, extract semantic meaning from diffs.
Phase 2: Intent classification. Map commits to intent categories (feature, fix, refactor, chore).
Phase 3: Workflow templates. Predefined patterns for common git workflows.
Phase 4: CLI scaffolding. Commander.js setup with subcommands for each operation.
Phase 5: Configuration system. User-level and repo-level config with sensible defaults.
Phase 6: Output formatting. Structured output for terminal, JSON, and markdown.
Phase 7: Release prep. Version bump, changelog generation, LICENSE, README.

Each phase was a focused commit or two. No phase depended on a phase that hadn’t been built yet. The ordering was deliberate — you can’t build intent classification without a commit analysis engine, and you can’t build a CLI without knowing what operations you’re exposing.

Gemini PR Reviews and Four Releases in One Day

Sat, 06 Dec 2025 10:00:00 -0600

54 commits. Four releases. And a debugging journey through three different Gemini configurations before PR reviews actually worked.

The Gemini PR Review Pipeline

The goal: automated code review on every PR to the Nixtla repo. An AI reviewer reads the diff, checks for compliance violations, flags potential issues, and posts a structured review comment. The reviewer is Gemini, because the free tier is generous enough for a repo this size.

Global Skill Schema and a Prediction Markets Vertical

Fri, 05 Dec 2025 10:00:00 -0600

106 files. 11,951 lines. The day split into two halves: standardizing how skills get built, then proving the standard works by building a new vertical from it. Standards that exist without implementations are aspirational. Standards that ship with a working example are real.

Global Standard Skill Schema

The 8 skills from Dec 1 followed a structure. But that structure lived in tribal knowledge and copy-paste. Today it became a formal specification.

v1.2.0: Every Skill to 100% Compliance

Thu, 04 Dec 2025 10:00:00 -0600

24 commits. One release. The entire day was compliance remediation. Not the glamorous kind of engineering. The kind that makes everything else work correctly.

The Starting Point

The skills infrastructure built on Dec 1 had the right structure but loose compliance. Each SKILL.md file scored between 38% and 40% against the compliance checker. Missing required fields, incomplete schemas, permissions that didn’t match actual plugin requirements, usage examples that wouldn’t parse.

CEO Quickstart Guide and DeFi Sentinel Exploration

Wed, 03 Dec 2025 10:00:00 -0600

Two very different writing tasks today. One document optimized for a specific person. Six documents exploring a product that might not exist in a month. Four commits total, but the line count tells the real story: 4,798 lines of DeFi exploration and 203 lines of the most carefully edited document in the repo.

CEO Quickstart: 203 Lines for Max

The Nixtla workspace has thorough documentation. Architecture docs, API references, deployment guides, compliance audits. What it didn’t have was a document that answers: “I’m Max. I have 10 minutes. What does this do and how do I show it to someone?”

Skills Infrastructure from Scratch: 8 SKILL.md Files, an Installer, and a Compliance Framework

Mon, 01 Dec 2025 10:00:00 -0600

53 files. 13,445 lines. One goal: give the Nixtla workspace a skills layer that doesn’t exist yet.

What Needed Building

The Nixtla workspace had plugins. It had documentation. It had release discipline. What it didn’t have was a way for external tools to discover and invoke its capabilities through a standardized interface.

Skills are that interface. A SKILL.md file declares what a skill does, what inputs it needs, what outputs it produces, and what permissions it requires. An installer package reads those declarations and wires them into Claude Code. A demo project proves the whole chain works end-to-end.

Nixtla Baseline Lab: Real statsforecast Baselines via MCP Server

Mon, 24 Nov 2025 10:00:00 -0600

Yesterday was plugin scaffolding. Today the Baseline Lab gets real models running real data through a real MCP server.

Phase 2: Plugin Manifest and MCP Config

The Baseline Lab plugin needed two pieces of infrastructure before any forecasting code could run.

Plugin manifest. Standard plugin.json declaring the plugin’s name, version, dependencies, and MCP server configuration. The MCP config tells Claude Code how to start the server, what tools it exposes, and what permissions it needs (filesystem read for data files, network for optional Nixtla cloud API calls).

Nixtla Repo: Zero to v0.2.0 with a Working Search-to-Slack Plugin

Sun, 23 Nov 2025 10:00:00 -0600

New repo. Empty directory. By end of day: v0.2.0 tagged, a working plugin shipping, and a GitHub Pages site live.

Repository Initialization

The Nixtla Claude Code plugins workspace needed proper infrastructure from commit one. Not a README and a prayer – actual CI/CD, documentation filing, and GitHub Actions workflows.

First commit: project scaffolding with GitHub Actions for CI, automated doc filing using the standard 000-docs numbering scheme, and a base configuration for the plugin workspace. GitHub Pages site deployed from the repo’s docs output.