LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when the user asks which phx-* command fits a task (review, plan,
Initialize plugin in a project — install Iron Laws, auto-activation rules,
Walk through the Elixir/Phoenix plugin commands, workflow, and features
Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures,
Use this skill for a specific cloud workflow. Mention provider, trigger phrases, expected inputs, and when not to use it.
Plan who does each step of a task in this repo, on which model, at which effort: Haiku or Sonnet subagents for search, recon, and log-reading; code edits on Opus 5.5; start at medium effort and escalate on evidence (high, then xhigh, then Fable 5.1 for one stuck task); the orches
The ordered finish-line runner for any change in this repo — generators, then the asset-integrity refresh last on its own, then the full gate suite, then commit and push; use before declaring any change finished or whenever the stop hook reports uncommitted or untracked changes.
Re-verify and extend catalog/model-registry.json — the fail-closed model-name and reasoning-effort matrix scripts/model-policy.mjs validates against — via delegated Context7-backed research, orchestrator-owned registry edits, and the full validation chain; use when a policy check
The repeatable loop for watching a pull request until it is merged or closed, pairing webhook subscription with a scheduled self check-in so CI results, new pushes, and merge-conflict transitions are never missed; use when asked to watch, babysit, or autofix a PR, or right after
Route accounting questions to the narrowest specialist in the catalog. Use when you do not already know the specialist needed. Not for direct accounting answers; Maestro classifies, dispatches, and synthesizes only. Dispatches single agent for focused tasks, parallel team (max 3)
Multi-jurisdiction business combinations reference framework covering acquisition accounting, purchase price allocation, goodwill, and post-combination integration under ASC 805 and IFRS 3.
Multi-jurisdiction financial close cycle reference framework covering month-end, quarter-end, and year-end close. Provides regulatory filing deadlines by jurisdiction (SEC, EU TD, UK DTR, TSE/FSA, CSRC, SEBI, ASX, HKEX), record-to-report process steps, reconciliation standards, i
Multi-jurisdiction consolidation scope and intercompany elimination reference framework covering ASC 810 / IFRS 10 control models, VIE (Variable Interest Entity) primary beneficiary analysis, NCI measurement, equity method accounting (ASC 323 / IAS 28), intercompany eliminations
Multi-jurisdiction equity-based compensation reference framework covering stock options, RSUs, ESPPs, and performance awards under ASC 718 and IFRS 2.
Multi-jurisdiction fixed assets, depreciation, and impairment reference framework covering PP&E, intangibles, right-of-use assets, and goodwill under US GAAP and IFRS.
Multi-jurisdiction reference framework for foreign currency translation and remeasurement covering functional currency determination, ASC 830 / IAS 21 method selection, CTA in OCI, highly inflationary economy treatment, net investment hedge interactions, and multi-GAAP comparison
Multi-jurisdiction hedge accounting reference framework covering ASC 815 (US GAAP) and IFRS 9 hedge designation, effectiveness testing, OCI mechanics, IFRS 9 rebalancing, cost-of-hedging approach, discontinuation rules, embedded derivatives, and local GAAP treatments (German HGB
Multi-jurisdiction indirect tax and e-invoicing reference framework covering VAT/GST compliance and mandatory electronic invoicing mandates across EU, Brazil, India, Mexico, China, UK, and Australia.
Multi-jurisdiction lease accounting reference framework covering ASC 842 (US GAAP) and IFRS 16, with additional coverage of UK FRS 102 (2024 periodic review amendments effective 1 Jan 2026), German HGB, JGAAP (ASBJ Statement No. 34, effective FY beginning on/after 1 Apr 2027), CA
Multi-jurisdiction payroll accounting reference framework covering compensation expense recognition, employee benefits, pension/post-retirement obligations, and payroll tax compliance.
Fourteen posts of being wrong in production, compressed to checkboxes
Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds
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.
/sync-automation-setup
Sync automation setup
Setup automated synchronization workflows
/sync-conflict-resolver
Sync conflict resolver
Resolve synchronization conflicts automatically
/sync-issues-to-linear
Sync issues to linear
Sync GitHub issues to Linear workspace
/sync-linear-to-issues
Sync linear to issues
Sync Linear tasks to GitHub issues
/sync-pr-to-task
Sync pr to task
Link pull requests to Linear tasks
/sync-status
Sync status
Monitor GitHub-Linear sync health status
/sync
Sync
Synchronize task status with git commits, ensuring consistency between version control and task tracking.
/system-behavior-simulator
System behavior simulator
Simulate system performance under various loads with capacity planning, bottleneck identification, and optimization strategies.
/task-from-pr
Task from pr
Create Linear tasks from pull requests
/tdd
Tdd
Test-driven development workflow with Red-Green-Refactor process and branch management
/team-workload-balancer
Team workload balancer
Balance team workload distribution
/test-changelog-automation
Test changelog automation
Automate changelog testing workflow
/test-coverage
Test coverage
Analyze and report test coverage
/testing_plan_integration
Testing plan integration
I need you to create an integration testing plan for $ARGUMENTS
/timeline-compressor
Timeline compressor
Accelerate scenario testing with rapid iteration cycles, confidence intervals, and compressed decision timelines.
/todo
Todo
Manage project todos in a todos.md file with add, complete, remove, and list operations
/troubleshooting-guide
Troubleshooting guide
Generate troubleshooting documentation
/ultra-think
Ultra think
Deep analysis and problem solving mode
/unity-project-setup
Unity project setup
Sets up a professional Unity project with industry-standard structure and configurations
/update-branch-name
Update branch name
Update current git branch name based on analysis of changes made
AI coding platform for teams
20 views 0 likesAI Multi-Agent Framework in .NET
14 views 0 likesProduction-ready code examples for Telnyx AI Communications Infrastructure — Voice AI, SMS, SIP, and IoT APIs
12 views 0 likesUltraGameStudio - AI coding agent for game development: engine workflows, gameplay code, and asset generation.
12 views 0 likes🦞 ResearchClawBench: Evaluating AI Agents for Automated Research from Re-Discovery to New-Discovery
12 views 0 likesThe context-aware model router that learns & adapts to your long-horizon coding agent workflows. Lightweight & extensible, works with any harnesses, any models,…
20 views 0 likesOpen-source sandboxes where coding agents build and deploy. Spin up isolated environments where Claude Code, Cursor, and other agents code and deploy software.
24 views 0 likesNative desktop UI for Claude Code with orchestration, streaming, background agents, and multi-provider support. Built with Tauri + React.
22 views 0 likesOpenCode mobile client via Telegram: run and monitor AI coding tasks from your phone while everything runs locally on your machine. Scheduled tasks support.
17 views 0 likesTerminal session manager for AI coding agents. One TUI for Claude, Gemini, OpenCode, Codex, and more.
23 views 0 likesExposes internet search tools for use by LLM-backed Assist in Home Assistant
15 views 0 likesTemplates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
8 views 0 likesVersus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…
14 views 0 likesBrowser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.
6 views 0 likesAgentic-friendly CLI generator for APIs: turn Swagger, OpenAPI, and google.api.http protos into single-binary CLIs with catalogs and generated Skills.
10 views 0 likesOpen-source agent platform for Global × China enterprises — wire every system through one agent core. Self-hosted, any LLM.
7 views 0 likesOfficial python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.
11 views 0 likesAn agent small enough to run anywhere. A minimal agentic runtime in C — ~380 lines, 54KB binary, ~2MB RAM. A skill file + an LLM + a shell loop, no framework.
10 views 0 likesAgentiLoop Agent! An Autonomous Agentic Agent for Mac, and exclusive Apple only harnesss. Suppprtd automation, scripting, coding, build anything and more. Power…
10 views 0 likes微信公众号 AI 运营助手 | 选题、写稿、审稿、排版、配图、发布全流程 Skill,支持 OpenClaw / Claude Code / Cursor / Codex
17 views 0 likes