conventions-claude

Validate Claude Code plugin artifacts against schema and path conventions.

111|29|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/xiaolai/nlpm --skill conventions-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventions-claude
Source: https://github.com/xiaolai/nlpm/tree/main/codex/skills/conventions-claude
Command: npx skills add https://github.com/xiaolai/nlpm --skill conventions-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents Claude Code plugin content from drifting into invalid or inconsistently structured formats by documenting the expected conventions for commands, skills, manifests, hooks, memory, and related configuration surfaces.

Core Features & Use Cases

  • Claude Code artifact schema guidance: Standardizes how to structure .claude/ skills, commands, plugin manifests, and associated configuration files so they score and validate reliably.
  • Hook and event correctness: Clarifies event names, hook matcher behavior, and hooks.json structure to reduce silent failures caused by incorrect casing or schema mismatches.
  • Multi-surface alignment (commands vs skills): Explains the Claude Code v2.1.x merged architecture and the canonical paths used by NLPM’s Claude-specific overlay.

Quick Start

Use the conventions-claude skill to validate that your Claude Code plugin’s SKILL.md structure, plugin.json, and hooks.json match the expected schemas and formatting.

Frequently Asked Questions about conventions-claude

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Claude Code plugin artifacts for correct schema compliance?

To validate Claude Code plugin artifacts for schema compliance, ensure your SKILL.md, plugin.json, and hooks.json files follow the expected YAML frontmatter fields and .claude/ path conventions so NLPM can reliably score and validate them.

What is the correct hooks.json schema structure for Claude Code?

The correct hooks.json schema for Claude Code requires supported tool and event naming with proper casing to clarify hook matcher behavior, reducing silent failures caused by schema mismatches during plugin validation and execution.

How do I structure a Claude Code skill to meet discovery and scoring conventions?

Structure a Claude Code skill by placing it under the canonical .claude/ paths and including the required YAML frontmatter fields in SKILL.md, aligning with the merged v2.1.x architecture so NLPM’s Claude-specific overlay can discover and score it.

Does Claude Code use the same path conventions for commands and skills?

Claude Code uses a merged architecture for commands and skills that aligns multi-surface configurations under canonical .claude/ paths, ensuring both artifact types are consistently discovered and validated by the NLPM overlay.

Why does my Claude Code hook fail silently during plugin validation?

Claude Code hooks fail silently during plugin validation when the hooks.json schema contains incorrect event name casing or schema mismatches, preventing the hook matcher behavior from executing the expected tool events.