You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Adam Kaminski
thimslugga
I am interested in Linux, macOS, Python, Golang, Rust and Networking.
Opinions expressed are my own and may not be the views of my employer.
Production AI Automation Notes #1: Agent Approval Gates — JSON schema, human review, deterministic dispatch, audit logs
Production AI Automation Notes #1: Agent Approval Gates — JSON schema, human review, deterministic dispatch, audit logs
Production AI Automation Notes #1: Agent Approval Gates
Updated 2026-04-28 — JSON schemas, human review, deterministic dispatch, and audit logs for AI agents that touch real systems.
The most common shape of an "AI agent" demo is: model decides → model calls API → side effect happens. That works in a sandbox. It does not work the moment the agent is allowed to send an email to a customer, update a CRM record, or trigger an n8n workflow that hits production.
The pattern that does work is older than agents and is borrowed from financial systems: draft → validate → approve → dispatch → audit. Five steps, five contracts, no exceptions.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
The core idea
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Claude Code Agent Playbook — how to bootstrap autonomous agents with Claude Code
Claude Code Agent Playbook
A distilled guide for bootstrapping autonomous agents on top of Claude Code.
TL;DR: An agent is a directory with a CLAUDE.md that gives Claude a role, a startup/shutdown ritual, and a map of files and skills. The rest is just files.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This document captures learnings about how Agent Skills handle references/, recipes/, and services/ folders, including token budget implications and best practices based on the AgentSkills.io specification and GitHub Copilot implementation behavior.
Progressive Disclosure Model
Agent Skills use a three-tier loading model to efficiently manage LLM context windows: