メニュー
Use when creating, updating, auditing, or validating Agent Skills. Provides validation scripts and guidance for keeping skills accurate and compliant with the Agent Skills specification.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Reference for the Nomarr Docker development environment. Use when working with Docker containers, running e2e tests, querying ArangoDB directly, debugging prod-like issues, testing DB migrations, or interacting with the containerized Nomarr API. Contains credentials, ports, PowerShell snippets, AQL queries, and collection schema.
Generates a structured prompt for spawning Support-Librarian to gather relevant ADRs, logs, and design docs before a design, planning, or execution task. Use before starting any significant work — designing a feature, creating a plan, executing a plan, or reviewing code — to ensure prior decisions and dead ends are known. Trigger automatically in agents that have this skill, or manually when entering an unfamiliar area.
Fetch authoritative, up-to-date external documentation using Context7 MCP tools. Use proactively — without being asked — whenever writing or reviewing code that involves a third-party library or framework API (method signatures, config keys, behavior); a named library version (e.g., "Next.js 15", "React 19", "AWS SDK v3"); non-trivial configuration such as auth flows, crypto, or security-critical patterns; unfamiliar error messages from external tools; or any situation where guessing an API would be risky. Skip for purely local refactors and language fundamentals with no external dependencies.
Guide for building Python applications using the GitHub Copilot SDK. Use when integrating GitHub Copilot into Python apps: creating CopilotClient sessions, defining custom tools, handling streaming responses, managing session lifecycle, Pydantic parameter validation, BYOK (Bring Your Own Key) provider configuration, or any GitHub Copilot SDK API pattern. Requires Python 3.9+, asyncio, and GitHub Copilot CLI in PATH.
Use when executing implementation plans produced by the feature-planning skill. Orchestrates execution subagents (one plan phase at a time), dispatches review subagents for thorough quality enforcement after each plan, and manages fix cycles when review finds issues. Trigger when user says "execute the plans", "implement the feature", "work through the plans", or when validated plans exist in artifacts/plans/pending/TASK-*-{A..Z}-*.md and need implementation. Not for single-plan execution — use plan_complete_step directly for those.
Use when decomposing a major feature design into dependency-ordered implementation plans. Handles the full pipeline from design document to validated, cross-referenced plan files with minimal drift. Trigger when user mentions planning a large feature, breaking down a design doc into parts, creating implementation plans for multi-part work, or coordinating plans that span multiple sessions. Not for single plans or simple tasks — use the Plan subagent directly for those.
| name | skill-maintenance |
| description | Use when creating, updating, auditing, or validating Agent Skills. Provides validation scripts and guidance for keeping skills accurate and compliant with the Agent Skills specification. |
When to use: When creating new skills, updating outdated skills, or auditing skill quality.
Purpose: Check skills for format compliance and invalid references.
Usage:
# Validate all skills
python scripts/validate_skills.py
# Validate one skill
python scripts/validate_skills.py layer-helpers
# JSON output
python scripts/validate_skills.py --format=json
# Also check if code references exist
python scripts/validate_skills.py --check-refs
Checks performed:
---name, descriptionname matches directory name, lowercase with hyphensname ≤ 64 chars, no consecutive hyphensdescription ≤ 1024 chars, non-empty--check-refs).github/skills/<skill-name>/SKILL.md with frontmatter:---
name: skill-name
description: Use when [trigger conditions]. Provides [capabilities].
---
# Skill Title
**When to use:** [Clear trigger description]
---
## Section 1
Instructions...
---
## Validation Checklist
- [ ] Check 1 **→ Consequence**
- [ ] Check 2 **→ Consequence**
python scripts/validate_skills.py skill-nameWhen: Architecture changed, code moved, or skill guidance is stale.
Process:
python scripts/validate_skills.py <skill-name> --check-refsRules:
| Field | Required | Constraints |
|---|---|---|
name | Yes | 1-64 chars, lowercase alphanumeric + hyphens, must match directory |
description | Yes | 1-1024 chars, describe WHAT and WHEN |
--)Good:
description: Use when creating or modifying code in nomarr/helpers/. Helpers are pure utilities with NO nomarr.* imports.
Poor:
description: Helper layer rules.
references/)--- separatorsCode references in skills can become stale when code moves.
# Find invalid references
python scripts/validate_skills.py --check-refs
# Check specific skill
python scripts/validate_skills.py layer-components --check-refs
Fix invalid references:
Run monthly or after major refactors:
# 1. Validate all skills
python scripts/validate_skills.py --check-refs
# 2. Review any invalid references
# 3. Update stale skills
# 4. Re-validate
python scripts/validate_skills.py
Nomarr skills are organized by purpose:
| Skill | Purpose |
|---|---|
layer-* | Architecture layer guidance |
code-discovery | Codebase exploration tools |
code-generation | Boilerplate generation |
quality-analysis | QC and linting tools |
skill-maintenance | This skill (meta) |
Before committing skill changes, verify:
name and description? → Requiredname match directory name? → Requiredname lowercase with hyphens only? → Requireddescription explain WHAT and WHEN? → Required--check-refsreferences/ if not