LLM Mart Basic
@llm-mart · Joined Jun 2026
Read a CSV file from disk, compute per-column min/mean/max for every numeric column, emit the result as JSON. Stdlib-only Python; no pandas, no numpy. Demonstrates the simplest possible "give me a file path, get back structured analysis" skill — a deliberate baseline for any skil
Summarise a chunk of text down to roughly `length` words using the agent's configured LLM provider. Input shape `{ text: string, length?: number }` on stdin, JSON; output shape `{ summary: string }` on stdout, JSON. Minimal: ~50 lines, no streaming, no retries — a deliberate base
Unified operational manual for AI agents driving the Chrono AI service stack — NyxID (identity, services, orgs, OAuth clients, proxy) AND Ornn (skill lifecycle — search, pull, install, execute, build, upload, share). One skill, two halves, one identity bootstrap, one set of failu
The manual an AI agent loads to operate Ornn — the model-agnostic skill-lifecycle API (an npm-style registry + CLI for agent skills) — via the NyxID CLI (`nyxid proxy request ornn-api …`). Load and follow this skill WHENEVER the user asks to do anything with Ornn skills or skills
Operational manual for AI agents using the Ornn skill-lifecycle API via direct HTTPS with a NyxID bearer token (`curl -H "Authorization: Bearer $TOKEN" …`). Once loaded, the host agent can search / pull / execute / build / upload / share skills end-to-end. Authoritative contract
Use this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: ranked inventory of what exists, column profiles, PII detection, grain and data-quality problems, verified join inference, Mermaid ER diagrams, guarded ad-hoc SQL pro
Use this to keep a dbt project and its semantic layer correct as the warehouse and the business change, including a semantic layer that is native Apache Ossie documents rather than dbt. It detects drift on four axes and proposes the fix: schema drift (source columns and tables ad
Use this to author and change a dbt project or a semantic layer: bootstrap a project in a repo that has none (`transform init`), write or refactor model SQL from staging to marts, add tests and docs in schema.yml, manage dependencies, and define or update the semantic layer, whet
Imported from haoming-luo/agentfem/docs/agents.
Build, review, run, validate, migrate, or extend AgentFEM finite-element projects. Use for AgentFEM studies, meshes, materials, constraints, loads, solution steps, results, campaigns, scientific datasets, surrogate/PINN/neural-operator integration, verification, public API extens
Use when handling Jira issues, sprints, boards, links, fields, worklogs, attachments, or users, or on any Jira intent without a key ("create/find a ticket", "pick a project"). Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when MCP Atlassian tools fail or are unav
Use when writing or formatting Jira descriptions, comments, or any text destined for Jira. Converts Markdown to Jira wiki markup, provides templates (bug reports, feature requests), and validates syntax before submission. Trigger on any Jira content authoring task.
Use when interacting with Jira issues - searching, creating, updating, moving, transitioning, commenting, logging work, downloading attachments, managing sprints, boards, issue links, web links, fields, or users. Auto-triggers on Jira URLs and issue keys (PROJ-123). Also use when
Prove a search, filter or API answer is real before relying on it, and budget web search across a fan-out. Use when querying an unfamiliar API, a filter returns suspiciously clean results, a per-item error may have been swallowed, or briefing research agents.
Open or update an architecture diagram with the selected builtin or custom viewer, preserving a neutral session handoff. Use when asked to inspect architecture interactively or continue an existing diagram session.
Measure whether a test suite is any good, not only that it passes: branch coverage, mutation score, complexity-times-coverage risk, duplication. Use when adding or reviewing tests on a change that matters, a suite passes but a bug still shipped, coverage is high and confidence is
Decide whether to spawn a subagent, and on which model tier and reasoning effort. Use when planning a fan-out, choosing a subagent model, writing a workflow script's opts.model, authoring an agent definition, setting a repo's cost posture, or when a delegation decision is non-obv
Raise the visual quality of something that already renders: build, screenshot, independent scored critique, fix, against rubrics with hard accessibility, design-token, runtime and asset-licensing gates. Use when asked to make a UI, page, HTML doc, dashboard, game scene or 3D asse
Decide where an instruction belongs and write it there, then sync and lint. Use when asked to add, change or remove a rule, skill, instruction, hook, setting or CLAUDE.md line, to "remember" something that should persist beyond this session, or when a correction should apply to f
Verify a third-party library, asset, model, font, dataset or copied snippet is safe to ship under the project's licensing stance, and record it. Use before adding or upgrading any dependency, before downloading any asset, and before a release.
Discovery worked. Ping worked. Every TCP connection timed out, and later the tunnel only worked when someone had a terminal open.
Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.
A surprising share of AI-in-the-terminal failures aren't the AI. They're zsh, and a version of bash from 2006.
A Claude Code plugin turns standalone project configuration into a namespaced, installable extension that teams and communities can update as one unit.
None of the safety came from the model. It came from six boring habits.
Skills package instructions and references. Subagents run work in a separate context and return results. They solve different problems and can be composed deliberately.
Six hours in, one step left, everything green, and the incident that didn't happen
CLAUDE.md carries persistent project context. Skills load reusable procedures when relevant. Separating stable facts from task-specific workflows keeps both easier to maintain.
Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it
An API request routing a model's tool call through an approval gate to a remote MCP server
31 config keys, two audits, and why the first one was wrong in both directions
The official MCP Registry stores standardized server metadata rather than package code. Publishers verify a namespace, describe installation or remote access, and submit immutable versions.
Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.
Remote MCP authorization uses established OAuth standards, but secure integration still requires issuer validation, least-privilege scopes, protected token handling, and server-side enforcement.
"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks
stdio fits local processes and prototypes. Streamable HTTP fits hosted services and shared integrations. The right choice follows where the capability runs and who must reach it.
The most important rule wasn't about what I could change. It was about what I was allowed to display.
Tools perform operations, resources expose readable context, and prompts provide reusable templates. Choosing the correct primitive makes an MCP server easier to understand and govern.
Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.
Build an MCP server in TypeScript with focused tools, validated schemas, local and remote transports, Inspector tests, and production security controls.
/chore
Chore
This is the lane for changes with no behavior to test-drive — prose edits, a version bump on an
/cleanup
Cleanup
Use this after a pull request has merged but your local checkout is still on the topic branch.
/commands
Commands
Prints the public command catalog straight from `COMMANDS.md` — the plugin's own single source
/commit
Commit
This is the single entry point for turning staged work into a commit — nothing in codeArbiter
/conflict
Conflict
The protocol for a rule conflict — not a skill route, an orchestrator-level halt. When two sources
/context-check
Context check
An optional, on-demand drift audit for the bypass case: a merge, a direct push, or a manual edit
/create-context
Create context
This is the populator for a project that already has code to read. Instead of interviewing you about
/debug
Debug
This is where an unexplained defect goes before anyone touches code. The investigation is
/decompose
Decompose
This is the populator for a project that has no code yet to read. Rather than guessing at
/doctor
Doctor
Proves the install is actually enforcing, rather than just present. codeArbiter's worst failure
/feature
Feature
This is the standard entry point for new work with a human in the loop at every step. A short
/fix
Fix
This is the entry point for a defect that already has a known cause, or one you can describe
/init
Init
This is how a repository opts into codeArbiter for the first time. It writes the root-level state
/metrics
Metrics
A bare-numbers governance glance — three metrics, each with a trend arrow against the prior
/override
Override
The sanctioned, logged escape hatch. A routine gate — a lint rule, a style check, a non-security
/pr
Pr
Explicit PR entry and a direct request to open a PR use the same branch-finishing owner.
/preview
Preview
A zero-onboarding, read-only dry-run of the reviewer fleet against whatever is currently
/prune
Prune
This is a Feature Forge preview command — the after-each-turn service ships **off** by default and
/reconcile
Reconcile
Compares architectural records with the scaffold and prior decisions using SMARTS.
/refactor
Refactor
This is the lane for moving or reshaping code without changing what it does — a rename, an extract,
PiG (Pi in Go) is a faithful Go port of upstream Pi, the TypeScript codebase behind the Pi coding agent. It is a parity-bound translation, not a rewrite: upstre…
0 views 0 likesAn AI Agent that lives in your pocket. Local-first and privacy focused.
1 views 0 likesUnofficial skill that teaches coding agents to build with TypeSafe AI's Jev: typed decisions, calibrated confidence, and prior art from 150+ community projects.
5 views 0 likesAdaptive Test-time Learning and Autonomous Specialization
3 views 0 likesPrediction-market trading engine — Wang Transform pricing on 291K+ contracts; paper-traded across Kalshi · Polymarket · Solana DFlow (Jito bundles) · 633 tests
2 views 0 likesKnowledge Management for Humans and Agents
4 views 0 likesOpen-source Claude Cowork / Codex / WorkBuddy alternative — a local-first AI office agent that turns one request into real PPTX, DOCX, XLSX and HTML files. Runs…
4 views 0 likesDeepAgent Code: AI coding agent with persistent memory and control plane
2 views 0 likesAwesome Jev — evidence-graded index of TypeSafe System One: SDKs, MCP tools, agents, apps and open models. 20 languages, rebuilt every 2 hours.
3 views 0 likesCLI for Telegram — agent-friendly, daemon-based, with webhook event push.
3 views 0 likesAI deep-research agent that turns any question into a cited report: plans searches, reads real sources, verifies evidence. Self-hosted, multi-provider, Docker-r…
2 views 0 likes