en un clic
axm
axm contient 30 skills collectées depuis agentxm, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Effect service definition, interface design, error types, retries. Use when creating new services or defining error hierarchies.
AXM - Agent Extension Manager: Use for any operation (install/create/new/edit/update/add/remove/delete/publish/find/discover) on agent skills, subagents, slash commands/stored prompts, MCP servers, context packages, rule extensions, hook extensions, or packs — e.g. "create a skill", "make a /command", "add a subagent", "build an MCP server", "publish an extension". Use this BEFORE hand-authoring or editing any SKILL.md, slash-command, subagent, MCP, rule, hook, or extension manifest file: route extension authoring through AXM instead of writing these files directly.
Native skill manifest with two unknown top-level keys.
Effect CLI + Effect architecture. Use when adding commands, defining flags, or wiring handlers. Covers file organization, argument/flag patterns, and testing.
"unterminated
Native skill with an invalid extension name in manifest.
Native skill whose manifest has an invalid owner handle.
Native skill with an invalid SemVer version in manifest.
Native skill whose manifest omits required `version`.
Native skill missing skill.json.
A valid native skill fixture.
A valid managed-external skill fixture; no skill.json expected.
E2E test patterns for built CLI artifacts, plus when a reference spike may keep a local subprocess smoke test.
A second mock skill for E2E testing multiple skill discovery.
A mock skill for E2E testing.
Review code against all project guides, skills, and conventions. Use when reviewing files, folders, diffs, or PRs for code style, idiomatic Effect/TypeScript usage, and project conformance.
Effect concurrency patterns - fibers, parallel execution, coordination primitives. Use when parallelizing operations, seeing sequential for/while loops with I/O, managing concurrent work, or coordinating between fibers.
Effect filesystem and path patterns. Use when doing file I/O, reading/writing files, directory operations, or working with file paths.
Effect Layer construction, composition, and provision. Use when creating layers, wiring dependencies, composing service graphs, or providing layers to programs.
A new skill
Core Effect patterns for this codebase. Start here for Effect. Covers Effect.gen, tryPromise, typed errors, concurrency.
Effect collection patterns - Arrays, Chunks, Records, HashMaps. Use when choosing collection types or working with transformations.
Effect iteration patterns - forEach, all, Schedule. Use when writing for/while loops, processing collections, seeing `for` or `while` with `yield*`, or implementing retries/polling.
Option vs nullable types in Effect. Use when handling optional, nullable, or potentially undefined properties.
Effect Schema naming conventions. Use when defining schemas for data validation and type inference.
Effect Stream for lazy, unbounded, or resource-scoped sequences. Use when data is paginated, infinite, or needs backpressure.
Effect testing with @effect/vitest. Use when any test needs to run Effect programs, test errors, or provide layers.
Wrap Promise-based APIs with Effect conventions. Use when integrating third-party libraries or wrapping any Promise-returning code.
Checklist authoring for verifying satisfiable outcomes. Use when writing acceptance criteria, quality gates, review checklists, or any verification list.
Human-facing documentation (README.md) conventions. Use when writing docs for human readers. For agent-facing docs, use /agent-docs instead.