- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add athola/claude-night-market --skill claude-code-plugin-reference -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add athola/claude-night-market --skill claude-code-plugin-reference -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add athola/claude-night-market --skill claude-code-plugin-reference -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add athola/claude-night-market --skill claude-code-plugin-reference -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/athola/claude-night-market/tree/HEAD/.claude/skills/claude-code-plugin-referenceจากผู้เผยแพร่
This is the domain pack for how Claude Code plugin machinery works in this
repository. It covers manifests, skills, commands, agents, hooks, and the
marketplace registry, with the local conventions layered on top. Every
contract below was checked against a shipped plugin (mostly plugins/imbue,
plugins/abstract, and plugins/herald) on 2026-07-02 at repo v1.9.15.
When another night-market skill says "see the plugin reference for what a
hook payload is," this is the file it means.
Each term is defined once here and used without redefinition below.
Verified tree (imbue, trimmed):
plugins/imbue/
├── .claude-plugin/
│ ├── plugin.json # Claude Code manifest: registers everything
│ └── metadata.json # inter-plugin dependency manifest
├── openpackage.yml # cross-framework export manifest
├── skills/<name>/
│ ├── SKILL.md # hub document with frontmatter
│ └── modules/*.md # spokes, loaded on demand
├── commands/*.md # slash commands
├── agents/*.md # subagents
├── hooks/
│ ├── hooks.json # hook registration (auto-loaded)
│ ├── *.py, *.sh # hook scripts
│ └── shared/ # vendored helpers (hook_io, vow_utils, ...)
├── scripts/ # Python utilities skills shell out to
├── tests/ # pytest suite, run per plugin
├── Makefile # per-plugin test/lint/typecheck targets
├── pyproject.toml # package config, per-plugin coverage threshold
└── README.md
Second manifest in .claude-plugin/. Fields verified on imbue: name,
version (lockstep), main, a skills subset, dependencies,
provides (infrastructure/patterns/tools), and a claude block
(skill_prefix, auto_load, categories). One trap: dependency ranges
here use their own semver namespace. imbue declares "abstract": ">=2.0.0"
while every plugin ships 1.9.15. The range is not compared against the
marketplace version, so do not "fix" it to 1.9.15 during a bump. The
update_versions.py bumper knows which fields to touch.
Cross-framework manifest consumed by the export pipeline
(make cross-framework, scripts/clawhub_export.py). Lists the skills
exported outside Claude Code and dependency sources in
gh@athola/claude-night-market form. Its version is also lockstep.
Fields verified on plugins/imbue/skills/proof-of-work/SKILL.md. Only
name and description are consumed by Claude Code itself. The rest are
house conventions read by repo tooling.
Role taxonomy (from docs/skill-integration-guide.md):
A skill's SKILL.md is the hub: it carries the always-loaded core and a
routing table into modules/*.md spokes. The model loads a spoke only when
the hub tells it to. This keeps the initial token cost near the
estimated_tokens value instead of the whole directory. The pattern is
specified in Skill(leyline:progressive-loading).
SKILL.md needs a ## Exit Criteria section with
concrete, observable, falsifiable checkboxes
(.claude/rules/skill-exit-criteria.md). A pre-commit ratchet,
scripts/check_skill_exit_criteria_drift.py, fails when the count of
missing sections rises above scripts/skill_exit_criteria_baseline.json.Skill(plugin:name) references in prose are scanned by
plugins/abstract/scripts/skill_graph.py. A second ratchet,
scripts/check_skill_graph_drift.py, blocks commits that add dangling
references (the bugs category) above
scripts/skill_graph_baseline.json. When your change lowers the count,
lower the baseline too so the ratchet tightens.SKILL.md tests, plus a
plugin test where the skill's contract matters, usually
tests/unit/skills/test_<name>.py (e.g. imbue's test_proof_of_work.py).Skill(imbue:proof-of-work) resolves imbue to the plugin registered in
the marketplace, then proof-of-work to the directory listed in that
plugin's plugin.json skills array. If the directory or the manifest
entry is missing, the reference is dangling and the skill-graph ratchet
will flag it.
Frontmatter verified on plugins/imbue/commands/justify.md and
plugins/sanctum/commands/fixit.md:
---
name: fixit
description: Fix broken functionality from pasted error output...
usage: /fixit <pasted-error-or-description> [--file <path>] ...
extends: "imbue:proof-of-work"
---
name and description are required. usage documents the argument
shape. extends (optional) names the skill the command routes into.$ARGUMENTS in the body is replaced with the raw argument string the
user typed after the command (see fixit: "The input is $ARGUMENTS (a
paste) or the contents of --file <path>").When to write a command versus a skill:
The Exit Criteria rule does not apply to command files.
Frontmatter verified on plugins/imbue/agents/review-analyst.md:
---
name: review-analyst
description: Autonomous agent for conducting structured reviews with
evidence gathering. Use when detailed code reviews requiring evidence
trails... Do not use when quick code check without formal review...
model: opus
tools:
- Read
- Glob
- Grep
- Bash
skills: imbue:review-core, imbue:proof-of-work, ...
---
description drives dispatch: Claude decides whether to hand a task
to the agent by matching it, so it must carry "Use when" and "Do not use
when" clauses just like a skill description.tools is the allowlist the subagent gets. model pins the model tier.skills lists skills the agent should load. The body below the
frontmatter is the agent's system prompt.Plugin agents read a fixed field set (code.claude.com/docs/en/plugins/
components, "Frontmatter fields in plugin agents"): name, description,
model, effort, maxTurns, tools, disallowedTools, skills,
memory, background, omitClaudeMd, isolation (worktree only),
color, and experimental.cacheTtl. They ignore permissionMode,
hooks, mcpServers and initialPrompt without an error, and never read
allowed-tools (a skill field) or max_iterations. Seven agents here ran
with every tool for months because they wrote allowed-tools.
FrontmatterProcessor.validate_plugin_agent reports each case, and
plugins/abstract/tests/test_every_plugin_agent_uses_read_fields.py runs
it over every agent. Hooks an agent needs go in the plugin's
hooks/hooks.json, matched with SubagentStart/SubagentStop on the
agent's scoped name.
omitClaudeMd: true (2.1.271) suits an agent whose delegation prompt
carries everything it needs: it skips about 79 KB of CLAUDE.md and rules
here. Agents that must apply repo rules keep loading them.
The hardest-won knowledge in the repo. Read modules/hooks.md whole
before writing or editing any hook. It carries the events registered
here, registration through hooks/hooks.json with empty plugin.json
hooks arrays, the stdin payload contract, exit-code and verdict
semantics, timeout budgets, the Python 3.9 floor, cache-dir execution
and hook testing.
Every plugin ships dynamic-workflow scripts under workflows/,
invoked as /plugin-name:workflow-name. Location, the meta format,
the forbidden calls and the refuse-with-next convention are in
modules/workflows.md.
.claude-plugin/marketplace.json. Top-level name,
version, description, owner, and a plugins array of
{name, source: "./plugins/<dir>", description, version, keywords}./plugin marketplace add athola/claude-night-market
(README quick start), then /plugin install <name>@claude-night-market.
The install form is documented in the book's getting-started pages;
re-verify there if it fails.plugin.json, metadata.json, openpackage.yml,
pyproject.toml, and package __init__.py. Bump with:uv run python plugins/sanctum/scripts/update_versions.py 1.9.16 --dry-run
uv run python plugins/sanctum/scripts/update_versions.py 1.9.16
/sanctum:update-plugins [plugin] [--fix] audits
plugin.json arrays against disk contents. make docs-sync-check (and
the capabilities-sync.yml CI job) verifies
book/src/reference/capabilities-*.md matches registrations. Fix drift
with /sanctum:sync-capabilities --fix, never by hand-editing the
generated capabilities files.A mod is a plugin whose hooks/hooks.json names a TypeScript module
under "modules". Its register(on, options) API, the events it can
hook and how mods are tested are in modules/mods.md.
claude plugin validate [--json] [--strict]: manifests, hooks, agent
and skill frontmatter, MCP entries, unquoted ${CLAUDE_PLUGIN_ROOT}.
make validate-plugins runs it over every plugin.claude plugin eval: scored eval suites run against a no-plugin
baseline. Runs are billed./skill-doctor: loaded skills that go unused, and what they cost in
context./doctor prompt-audit: prompting written for older models.book/src/ (mdBook, published by deploy-book.yml).
book/src/reference/capabilities-*.md are generated by the sync
tooling. Getting-started and plugin pages are hand-written.docs/plugin-development-guide.md,
docs/skill-description-guide.md, docs/skill-integration-guide.md.
Note: the dev guide's make create-plugin NAME=... target does not
exist in the root Makefile as of 2026-07-02 (stale doc). Scaffold with
Skill(abstract:create-skill) and copy an existing plugin's layout.hooks/hooks.json only, and python3 scripts/check_plugin_hooks.py
exits 0 afterward.CLAUDE_TOOL_* env vars) and exits 0 when fed malformed input:
echo not-json | python3 <hook>.py; echo $? prints 0.timeout registered in hooks.json.from __future__ import annotations,
uses timezone.utc rather than datetime.UTC, imports no unguarded
third-party package, and the python39-compat.yml gates pass.plugin.json skills
array, its description is at most 160 characters, it has an
## Exit Criteria section, and both ratchet scripts
(check_skill_graph_drift.py, check_skill_exit_criteria_drift.py)
pass.plugin.json hooks arrays are empty
in this repo and what error appears if they are not.plugins/abstract/tests/test_every_plugin_agent_uses_read_fields.py.tests/test_hook_commands_quote_plugin_root.py, and claude plugin validate on its plugin reports no warnings for it.Compiled 2026-07-02 against repo v1.9.15 (branch discussions-fix-1.9.14).
PreToolUse verdict contract corrected to allow|deny|ask and the imbue
vow-hook warn/block anomaly flagged on 2026-07-03.
Volatile facts and how to re-verify them:
# Hook events per plugin
for f in plugins/*/hooks/hooks.json; do
echo "$f"
python3 -c "import json,sys; print(list(json.load(open(sys.argv[1]))['hooks']))" "$f"
done
# All plugin.json hooks arrays empty (exit 0 = clean)
python3 scripts/check_plugin_hooks.py
rg '"hooks": \[' plugins/*/.claude-plugin/plugin.json
# 160-char description cap still in force
rg -n 'DESCRIPTION_MAX' plugins/abstract/scripts/validate_budget.py
# Payload-on-stdin contract (read the module docstring)
head -15 plugins/abstract/hooks/shared/hook_io.py
# Exit-2 semantics comment
rg -n 'exit 2 blocks' plugins/imbue/hooks/tdd_bdd_gate.py
# permissionDecision values in repo hooks (deny is correct; the
# warn/block hits in vow_no_ai_attribution.py are the known anomaly)
rg -n '"permissionDecision"' plugins/*/hooks/*.py
# Herald timeout pairing (registered 10s vs internal 8s)
rg -n 'LLM_TIMEOUT_SECONDS|timeout' plugins/herald/hooks/
# py39 gates and covered plugins
head -50 .github/workflows/python39-compat.yml
# Version lockstep fields touched by the bumper
rg -n 'def main' -A 12 plugins/sanctum/scripts/update_versions.py
# Marketplace entry shape
head -60 .claude-plugin/marketplace.json
# Stale make create-plugin claim (doc says it exists, Makefile disagrees)
rg -n 'create-plugin' Makefile docs/plugin-development-guide.md
Unverified/candidate items are labeled inline: the
/plugin install <name>@claude-night-market form (book-documented, not
exercised here) and the explanation that metadata.json dependency ranges
form a separate semver namespace (observed, not specified anywhere).
Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.
---name: claude-code-plugin-referencedescription: Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins…---# .claude/skills/claude-code-plugin-reference/SKILL.mdFAQ
ดาวน์โหลด .claude/skills/claude-code-plugin-reference/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/athola/claude-night-market
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต