菜单
Checks and configures Outfitter marketplaces and plugins. Use when setting up projects or checking plugin configuration.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | outfitter-agents-check |
| description | Checks and configures Outfitter marketplaces and plugins. Use when setting up projects or checking plugin configuration. |
| metadata | {"version":"1.0.2","author":"outfitter","category":"setup","preprocess":true} |
Check and configure outfitter marketplaces in a project.
Checks both project (.claude/settings.json) and user (~/.claude/settings.json) levels.
!bun ${CLAUDE_PLUGIN_ROOT}/skills/outfitter-agents-check/scripts/check-outfitter.ts .
Claude Code settings use two keys for marketplace plugins:
extraKnownMarketplaces — registers a marketplace by alias, pointing to a GitHub repoenabledPlugins — enables individual plugins using <plugin>@<marketplace> identifiersThe check script above reports the concrete identifiers and their current status. Use its output to determine what needs to be added.
Patterns for @outfitter/daemon including lifecycle management, IPC communication, health checks, and PID files. Use when building background services, daemons, or when "daemon", "IPC", "health check", "background service", or "@outfitter/daemon" are mentioned.
Creates handlers, CLI commands, MCP tools, and daemon services following Outfitter Dev Kit conventions. Use when adding new components to a project, scaffolding code, or when "create handler", "new command", "add tool", or "daemon service" are mentioned.
Deep patterns for @outfitter/mcp including tool registration, Zod schemas, resources, and server configuration. Use when building MCP servers, registering tools, defining resources, or when "MCP server", "MCP tool", "registerTool", or "@outfitter/mcp" are mentioned.
Generates patterns, templates, and guides for @outfitter/* packages. Covers transport-agnostic handler systems, Result types, error taxonomy, and package APIs. Use when working with @outfitter/*, Result types, Handler contract, error taxonomy, or when Result, Handler, ValidationError, NotFoundError, OutfitterError, or package names like contracts, cli, mcp, schema, tui, daemon, config, logging are mentioned.
Verify Outfitter compliance in a codebase. Scans for anti-patterns (throws, console, hardcoded paths) and produces a severity-ranked compliance report. Use for pre-commit checks, code review, or migration validation.
Submit feedback to the Outfitter team via GitHub issues. Use after discovering bugs, missing features, unclear docs, or improvement opportunities in @outfitter/* packages.