Ted Naleid tednaleid

AX: Context documents as Interface (Page) Copy

When building Agentic systems, giving your Agent an MCP server full of tools is only half the battle. Tools act as the functional buttons and form inputs of your application. But an interface made entirely of empty input fields and naked buttons without text labels is impossible to navigate.

To bridge the gap between having a capability and knowing how to apply it, we use Context Markdown Documents (SKILLs) within the Agent's Harness. In Agent Experience (AX), these markdown documents act like our interface page copy, tooltips, and onboarding manuals.

Note

While Anthropic’s open-source SKILLs framework is the most popular structure for this pattern, the underlying concepts are universal. They map directly to Google Labs' DESIGN.md specification for UI coding agents, as well as ecosystem standards like .cursorrules or AGENTS.md files used to ground cod

AI Fundamentals: Intro to Agent Experience (AX)

As we transition from building traditional software integrations to engineering Agentic AI Systems, the way we design technical interfaces must fundamentally change while still remaining intuitive and familiar to us.

We need to start thinking of our AI Agents as digital team members. Collaborators who communicate entirely through text and possess the unique ability to "say" JSON payloads to take real-world actions in their environment.

Historically, our core focus as developers has been to craft a great User Experience (UX)-designing visual workflows, APIs, and frontends to reduce cognitive friction for human eyes and fingers. Today, we must shift our focus to Agent Experience (AX): building systems that make it effortless for GenAI Agents to reason accurately and do the right thing.

What is Agent Experience (AX)?

Delete unused or obsolete files when your changes make them irrelevant (refactors, feature removals, etc.), and revert files only when the change is yours or explicitly requested. If a git operation leaves you unsure about other agents' in-flight work, stop and coordinate instead of deleting.
Before attempting to delete a file to resolve a local type/lint failure, stop and ask the user. Other agents are often editing adjacent files; deleting their work to silence an error is never acceptable without explicit approval.
NEVER edit .env or any environment variable files—only the user may change them.
Coordinate with other agents before removing their in-progress edits—don't revert or delete work you didn't author unless everyone agrees.
Moving/renaming and restoring files is allowed.
ABSOLUTELY NEVER run destructive git operations (e.g., git reset --hard, rm, git checkout/git restore to an older commit) unless the user gives an explicit, written instruction in this conversation. Treat t

Does this remind anyone else of the Emo Philips Northern Conservative Baptist Great Lakes Region Council of 1912 joke?

Format	Base64 Encoded	Java Client Compatible	Kcat Compatible	Benthos Compatible	YAML Config Compatible
JKS File	❌	✅	❌	❌	✅
PKCS12 File	❌	✅	❌	❌	✅
PKCS8 PEM String	✅	✅	✅	❌	❌
PKCS8 PEM Unencrypted File	✅	❌	✅	✅	✅
PKCS1 Encrypted PEM File	✅	❌	✅	✅	✅
PKCS8 Encrypted PEM File (MD5 DES-CBC)	✅	✅	✅	❌	✅

Falsehoods programmers believe about time

This is a compiled list of falsehoods programmers tend to believe about working with time.

Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.

Falsehoods

There are always 24 hours in a day.
February is always 28 days long.
Any 24-hour period will always begin and end in the same day (or week, or month).

	#!/usr/bin/awk -f

	# This program is a copy of guff, a plot device. https://github.com/silentbicycle/guff
	# My copy here is written in awk instead of C, has no compelling benefit.
	# Public domain. @thingskatedid

	# Run as awk -v x=xyz ... or env variables for stuff?
	# Assumptions: the data is evenly spaced along the x-axis

	# TODO: moving average

	/************************************************
	Retrieve a JWT from Auth0 for Postman

	2020-05-15 : @mamund @greatwebapis

	NOTES:
	1) create API definition in Auth0 with
	"client_credential" (machine-to-machine)
	2) pull the following from Auth0 API config:
	- domain

	package main

	import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"

	#include <stdio.h>
	#include <stdlib.h>
	#include <stdint.h>
	#ifdef _MSC_VER
	#include <intrin.h> /* for rdtscp and clflush */
	#pragma optimize("gt",on)
	#else
	#include <x86intrin.h> /* for rdtscp and clflush */
	#endif

	import com.googlecode.utterlyidle.*
	import com.googlecode.utterlyidle.servlet.ApplicationServlet
	import javax.servlet.http.HttpServlet
	import javax.servlet.http.HttpServletRequest
	import javax.servlet.http.HttpServletResponse

	class Application(bindings: List<Binding>): HttpHandler {
	val matcher = BindingMatcher(bindings = bindings)

	override fun handle(request: Request): Response {