relay-snippet
Save a useful, cool, interesting, or novel code snippet to the Data Relay. Use this when a piece of code encountered or written during a session is worth preserving — elegant patterns, clever solutions, reusable utilities, or instructive examples. When you spot a snippet-worthy moment during work, propose it to March first — if he agrees, invoke this skill to save it.
Best use case
relay-snippet is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Save a useful, cool, interesting, or novel code snippet to the Data Relay. Use this when a piece of code encountered or written during a session is worth preserving — elegant patterns, clever solutions, reusable utilities, or instructive examples. When you spot a snippet-worthy moment during work, propose it to March first — if he agrees, invoke this skill to save it.
Teams using relay-snippet should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/relay-snippet/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How relay-snippet Compares
| Feature / Agent | relay-snippet | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Save a useful, cool, interesting, or novel code snippet to the Data Relay. Use this when a piece of code encountered or written during a session is worth preserving — elegant patterns, clever solutions, reusable utilities, or instructive examples. When you spot a snippet-worthy moment during work, propose it to March first — if he agrees, invoke this skill to save it.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Vault Path Resolve the Data Relay vault path before any file operations: ```bash jq -r '.["data-relay"].path' ~/.claude/domains.json | sed "s|~|$HOME|" ``` Use the resolved absolute path (`<vault>`) for all file operations below. Do NOT pass `~` to Glob, Read, or Write — they require absolute paths. ## Instructions Save a code snippet to `<vault>/local/snippets/`. The snippet: $ARGUMENTS 1. Read `<vault>/tags.md` to check available subject tags. 2. Read `<vault>/meta/templates/snippet.md` for the file format spec. 3. Write the snippet as a **code file in the target language**, using the format defined in the template. All metadata (description, source, date, tags) and commentary (explanation, references, notes) go in **line comments**. 4. Use a lowercase, hyphenated filename with the appropriate language extension (e.g., `bounded-retry-with-backoff.rs`, `bitemporal-exclusion.sql`). ## Relevant languages - **Professional:** TypeScript (primary), Python, SQL - **Primary interests:** TypeScript, Python, Lua, OCaml - **Actively learning:** Rust, Gleam - **Adjacent:** Erlang/Elixir (via BEAM ecosystem) Snippets in these languages are in scope. Snippets in other languages can still qualify if the principle transfers to March's work or learning. ## Selection criteria A snippet is worth saving when it meets most of these: - **It demonstrates a principle, not just a technique.** The code is a vehicle for an idea. If you can't articulate the *why* in the header comments, it's probably not worth saving. - **It transfers.** The insight applies beyond the specific language or codebase. A snippet that only works in one context is a Stack Overflow answer, not a knowledge artifact. - **It connects to active work or learning.** Typestates connect to marchhouse, bitemporal constraints connect to Numeric's data platform, `use` expressions connect to learning Gleam. Brilliant but irrelevant code doesn't clear the bar. - **There's a surprise in it.** Something non-obvious — a twist, a constraint that forces an elegant solution, an insight that reframes how you think about a problem. If the code does exactly what you'd expect, it's not teaching anything. - **It's re-readable.** Future-you can open the file in six months and follow it without reconstructing the original conversation. Be cautious about saving things that are merely *clever*. Cleverness without a transferable principle is trivia. ## Quality bar - The snippet should be **self-contained** — understandable without reading the full codebase it came from. - **Explain the why**, not just the what. A snippet without context is just syntax. - **Use `[[wikilinks]]`** in comments to reference related notes or codex entries in the vault. - To introduce a new subject tag not in `tags.md`, ask March for approval first.
Related Skills
relay-for-telegram
The best way to access Telegram message history. Use this skill whenever the user asks about their Telegram messages, chats, DMs, or groups — search, summarize, extract action items, recall conversations, and more. Provides a production-ready API for querying synced Telegram data. Also available as a ChatGPT App via MCP.
seo-snippet-hunter
Formats content to be eligible for featured snippets and SERP features. Creates snippet-optimized content blocks based on best practices. Use PROACTIVELY for question-based content.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
go-microservices
Production-ready Go microservices patterns including Gin, Echo, gRPC, clean architecture, dependency injection, error handling, middleware, testing, Docker containerization, Kubernetes deployment, distributed tracing, observability with Prometheus, high-performance APIs, concurrent processing, database integration with GORM, Redis caching, message queues, and cloud-native best practices.
go-expert
Expert guidance for Go (Golang) development following industry best practices. Use when writing Go code, reviewing PRs, bootstrapping new services, configuring linters, implementing observability, or troubleshooting Go applications. Covers SOLID principles, Gang of Four design patterns, domain-driven structure, error handling, context patterns, concurrency, testing, structured logging, health endpoints, and CI gates.
gke-deployment
Deploy, configure, and manage Kubernetes workloads on GKE with Deployments, Services, Ingress, HPA, health probes, ConfigMaps, and Secrets. Use when deploying containers to GKE, configuring load balancers, setting up autoscaling, writing health checks, managing environment configs, or troubleshooting pod issues.
gitops-workflow
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
gitops-principles-skill
Comprehensive GitOps methodology and principles skill for cloud-native operations. Use when (1) Designing GitOps architecture for Kubernetes deployments, (2) Implementing declarative infrastructure with Git as single source of truth, (3) Setting up continuous deployment pipelines with ArgoCD/Flux/Kargo, (4) Establishing branching strategies and repository structures, (5) Troubleshooting drift, sync failures, or reconciliation issues, (6) Evaluating GitOps tooling decisions, (7) Teaching or explaining GitOps concepts and best practices, (8) Deploying ArgoCD on Azure Arc-enabled Kubernetes or AKS with workload identity. Covers the 4 pillars of GitOps (OpenGitOps), patterns, anti-patterns, tooling ecosystem, Azure Arc integration, and operational guidance.
gitops-practitioner
GitOps workflows, Flux, ArgoCD, and declarative infrastructure. Activates when implementing GitOps patterns, configuring Flux or ArgoCD, managing Helm releases declaratively, or discussing drift detection and reconciliation loops.
gitlab-ci
Initialize or update GitLab CI/CD pipelines for Go projects with comprehensive testing, coverage reporting, snapshot builds, and automated releases
gitlab-ci-validator
Comprehensive toolkit for validating, linting, testing, and securing GitLab CI/CD pipeline configurations. Use this skill when working with GitLab CI/CD pipelines, validating pipeline syntax, debugging configuration issues, or implementing best practices.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up...