Build and optimize Three.js geometry with built-in primitives, BufferGeometry, BufferAttributes, indexed meshes, custom vertex data, lines and points, and instanced rendering. Use when creating meshes, editing vertices or UVs, generating shapes, reducing draw calls, or diagnosing geometry memory and culling behavior.…
Implement and debug Three.js interaction with Raycaster, pointer and touch coordinate conversion, hover/selection state, camera controls, dragging, keyboard input, and world-to-screen projection. Use when picking objects, adding OrbitControls or PointerLockControls, handling mouse/touch input, or fixing interactive 3D…
Design and debug Three.js lighting with directional, point, spot, hemisphere, and area lights, shadow maps, image-based lighting, environment maps, light helpers, and performance budgets. Use when lighting a 3D scene, configuring shadows, setting up HDR illumination, matching a visual reference, or fixing dark, flat…
Operate Panniantong/Agent-Reach, the MIT-licensed installer, doctor, and routing layer for platform-specific internet research tools. Use when the user names Agent Reach, agent-reach, its channel doctor, optional backend setup, OpenCLI integration, cookie configuration, transcription, or an Agent Reach update or…
Ask which skill or flow fits your situation. A router over the skills in this repo. Use when the user asks which of these engineering skills or flows fits their situation. Triggers on: ask- matt, which skill should I use, what flow fits here.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress- test their thinking, or uses any 'grill' trigger phrases.
Compact the current conversation into a handoff document for another agent to pick up. Use when the user says handoff, is running out of context, or wants a fresh agent to pick the work up. Triggers on: handoff, hand this off, compact this conversation.
Implement a piece of work based on a spec or set of tickets. Use when an agreed spec or ticket set should now be built. Triggers on: implement, build this spec, work these tickets.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills. Use when this repo has not yet been configured for the suite. Triggers on: setup-matt-pocock- skills, configure the issue tracker, set up…
Operate ahujasid/blender-mcp, the MIT-licensed MCP server plus Blender addon that lets an AI client drive Blender for scene inspection, modeling, materials, rendering, asset import, and GLB or FBX export. Route one request to one mode: fit-check the project; preflight the host, addon, and port; install and wire a…
Agent-to-Agent horizontal messaging — Linux Foundation AAIF 2026 standard. Use when multiple agents across systems/vendors need to exchange tasks, results, or capabilities without sharing a runtime.
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
Map agent capabilities to standard benchmarks (SWE-bench, WebArena, OSWorld, GAIA, TauBench) plus custom regression packs. Use when you need defensible numbers on agent quality, not just vibes — before shipping, after every model change, and for vendor comparisons.
Compatibility alias for agent-principles. Use when an existing workflow, install surface, or exact-name request still references agent-development-principles; the substantive collaboration-principles work should route to agent-principles. Triggers on: legacy agent-development-principles, old install docs, exact-name…
Layered agent safety — prompt-injection defense, data exfiltration prevention, tool-misuse blocking via NeMo Guardrails + Lakera / LLM Guard / Llama Guard. Use before any agent reads untrusted input or executes tools with real-world side effects.
Simple, installation-agnostic AI agent lifecycle management using tmux + Python. Manage multiple AI agents without running a server, wiring HTTP APIs, or pulling in heavy dependencies.
Design tiered agent memory — core / recall / archival — with backend selection (mem0, Letta, Zep/Graphiti, LangMem) and temporal vs snapshot tradeoffs. Use when an agent needs persistent context across sessions, personalization, or temporal knowledge graphs.
Instrument LLM agents with traces, metrics, and replay. Use when an agent in production is silently failing, regressing, drifting, or burning tokens. Selects LangSmith / Langfuse / Phoenix, defines node-level spans, attaches evals to traces, and enables session replay.
★not rated 52▲
+4 3d agoA63 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: