Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Help the user create a new zot extension (slash command, LLM tool, or guard) in any language.
$ npx skills add patriceckhart/zot --skill write-zot-extension -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install patriceckhart/zot write-zot-extension --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .claude/skills/write-zot-extension && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .claude/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extensionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add patriceckhart/zot --skill write-zot-extension -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install patriceckhart/zot write-zot-extension --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .agents/skills/write-zot-extension && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .agents/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add patriceckhart/zot --skill write-zot-extension -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install patriceckhart/zot write-zot-extension --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .cursor/skills/write-zot-extension && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .cursor/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/patriceckhart/zot.git --path packages/agent/skills/builtin/write-zot-extension--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add patriceckhart/zot --skill write-zot-extension -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install patriceckhart/zot write-zot-extension --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .gemini/skills/write-zot-extension && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .gemini/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install patriceckhart/zot write-zot-extensionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add patriceckhart/zot --skill write-zot-extension -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .github/skills/write-zot-extension && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .github/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add patriceckhart/zot --skill write-zot-extension -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install patriceckhart/zot write-zot-extension --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/patriceckhart/zot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/agent/skills/builtin/write-zot-extension .opencode/skills/write-zot-extension && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-zot-extension" agent skill from https://github.com/patriceckhart/zot/tree/main/packages/agent/skills/builtin/write-zot-extension into .opencode/skills/write-zot-extension/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-zot-extension", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
write-zot-extensionHelp the user create a new zot extension (slash command, LLM tool, or guard) in any language.
Write Zot Extension is an agent skill from patriceckhart/zot. Help the user create a new zot extension (slash command, LLM tool, or guard) in any language.
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Hooks and plugins. The repository describes itself as: Yet another coding agent harness, lightweight and written in go. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 0f23566. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gonpmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Write Zot Extension loads about 3.4k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 1,055 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from patriceckhart/zot at commit 0f23566, republished under its MIT licence (© patriceckhart). 1,055 words, ~3,429 tokens.
.claude/skills/write-zot-extension/SKILL.md (or your agent's skills folder).Use this skill when the user asks for help building a zot extension — a new slash command, a new tool the LLM can call, an audit hook, or a permission gate. Skim this whole skill first, then collaborate with the user on the specific extension they want.
A zot extension is an external executable that zot launches as a subprocess and talks to over its stdin/stdout in newline-delimited JSON. It can be written in any language that can read/write JSON lines from stdio: Go, TypeScript (via tsx), Python, Rust, shell with jq, anything. Crash isolation is automatic; one bad extension never takes down zot.
Three things an extension can do (any combination):
Slash commands — register /foo so the user can run it from
the input. The handler returns a "prompt" (submitted to the
agent), an "insert" (text dropped into the editor), a "display"
(one-shot styled note in the chat), or a "noop".
Tools — register tools the LLM itself calls. Schema is
JSON Schema; zot routes the model's tool_call to the
extension's tool_result. Same lifecycle as built-in tools
(read/write/edit/bash/skill).
Lifecycle hooks — subscribe to events (session_start, turn_start, tool_call, turn_end, assistant_message) for telemetry / audit / custom UI, or intercept tool calls before execution to refuse dangerous patterns.
Each extension lives in its own directory:
~/Library/Application Support/zot/extensions/<name>/
├── extension.json # manifest (required)
└── <executable> # whatever exec points atOr project-local: <project>/.zot/extensions/<name>/. Project-local
wins on name conflict.
For ad-hoc use during development, skip the install step entirely
and run zot --ext PATH (repeatable: -e PATH -e PATH).
{
"name": "weather",
"version": "1.0.0",
"exec": "./weather",
"args": [],
"language": "go",
"description": "current weather lookups for any city",
"enabled": true
}Field rules:
name (required, unique) — id zot uses internally; matches the
hello frame. Slash commands & tools live in the same name space
as built-ins; conflicts are silently shadowed by built-ins.exec (required) — the executable path. Resolution:./ or ../: relative to the manifest's directory$PATH (e.g. node,
python3, npx, tsx)args — extra argv passed to exec (e.g. ["index.js"])language — informational only ("go", "typescript",
"python", etc.)enabled — defaults to true; set false to keep installed but skipNewline-delimited JSON in both directions. Top-level type is the
discriminator. Optional id correlates command/tool requests with
their responses.
The very first frame the extension sends is hello:
{"type":"hello","name":"weather","version":"1.0.0",
"capabilities":["commands","tools"]}Capabilities are advisory; current values are commands, tools,
events. Send all that apply.
zot replies with hello_ack:
{"type":"hello_ack","protocol_version":1,"zot_version":"0.0.x",
"provider":"anthropic","model":"claude-opus-4-7","cwd":"/path/to/project"}The canonical startup order is hello, wait for hello_ack, send
registration frames in any order, then send a single ready sentinel
so zot can finalize the agent's tool registry:
{"type":"register_command","name":"weather","description":"current weather"}
{"type":"register_tool","name":"weather","description":"Get current weather for a city.",
"schema":{"type":"object","properties":{"city":{"type":"string"}},"required":["city"]}}
{"type":"subscribe","events":["tool_call"],"intercept":["tool_call"]}
{"type":"ready"}If you don't send ready, zot's idle watchdog auto-treats you as
ready after 250ms of no frames, but always send it explicitly when
you can. Newer extensions on faster hosts shave that 250ms off.
Use hello_ack.cwd for the user's project directory. The extension
process itself runs from the extension directory, so do not use
os.Getwd() or process.cwd() when you need the project path.
zot → extension:
{"type":"command_invoked","id":"abc","name":"weather","args":"berlin"}
{"type":"tool_call","id":"def","name":"weather","args":{"city":"Berlin"}}
{"type":"event","event":"turn_start","step":1}
{"type":"event_intercept","id":"ghi","event":"tool_call",
"tool_name":"bash","tool_args":{"command":"rm -rf /tmp/foo"}}
{"type":"shutdown"}extension → zot (replies + spontaneous notifications):
{"type":"command_response","id":"abc","action":"prompt",
"prompt":"Show today's weather for Berlin in one line."}
{"type":"tool_result","id":"def","content":[{"type":"text","text":"Berlin: 16°C, fog"}]}
{"type":"event_intercept_response","id":"ghi","block":true,
"reason":"refused: command matches the danger pattern \"rm -rf\""}
{"type":"notify","level":"info","message":"refreshed cache"}
{"type":"clear_notes"}
{"type":"shutdown_ack"}notify notes are one-shot: they clear when the user sends their next
prompt (and on esc / /clear). Send clear_notes to retract every
note this extension pushed earlier (e.g. a transient approval prompt)
without waiting for the next turn; other extensions' notes are kept.
command_response.action values:
"prompt" — submit prompt as a fresh user message"insert" — drop insert into the editor at the cursor"display" — append display to chat as a one-shot note (no
model call, not in transcript)"noop" — handled internally; zot doesn't change the UItool_result.content[] blocks: {"type":"text","text":"..."} or
{"type":"image","mime_type":"image/png","data":"<base64>"}.
Per-tool timeout: 60s. Per-intercept timeout: 5s. Missing the intercept timeout is treated as "allow" so an unresponsive guard never stalls the agent.
hello; do not send notify, logs, or registration
frames before that handshake starts. Use stderr for logs / debug
output (zot captures stderr to $ZOT_HOME/logs/ext-<name>.log).\n.package main
import (
"encoding/json"
"github.com/patriceckhart/zot/packages/agent/ext"
)
func main() {
e := ext.New("weather", "1.0.0")
e.Command("weather", "current weather for a city",
func(args string) ext.Response {
return ext.Prompt("Tell me the weather for " + args)
})
e.Tool("weather", "Get current weather for a city.",
json.RawMessage(`{"type":"object","properties":{"city":{"type":"string"}},"required":["city"]}`),
func(args json.RawMessage) ext.ToolResult {
var in struct{ City string `json:"city"` }
if err := json.Unmarshal(args, &in); err != nil {
return ext.TextErrorResult("invalid args")
}
return ext.TextResult(in.City + ": sunny, 21°C (fake)")
})
// Optional: register project-specific commands after hello_ack.
e.OnHello(func(host ext.HostInfo) {
if host.CWD != "" {
e.Command("cwd", "show the current project directory", func(args string) ext.Response {
return ext.Display(host.CWD)
})
}
})
if err := e.Run(); err != nil {
e.Logf("fatal: %v", err)
}
}Build: go build -o weather .
OnHello is optional. Use it when configuration or registrations need
host metadata such as HostInfo.CWD, Provider, Model, ZotVersion,
ExtensionDir, or DataDir. The SDK sends hello, waits for
hello_ack, runs OnHello, announces registrations, then sends ready.
extension.json:
{"name":"weather","version":"1.0.0","exec":"./weather","language":"go","enabled":true}Run via tsx, which executes .ts files without a build step.
{"name":"scratchpad","version":"1.0.0","exec":"tsx","args":["index.ts"],"language":"typescript","enabled":true}// index.ts (excerpt; see examples/extensions/scratchpad/index.ts for the full version)
import { createInterface } from "node:readline";
import { stderr, stdin, stdout } from "node:process";
function send(o: object) { stdout.write(JSON.stringify(o) + "\n"); }
function log(s: string) { stderr.write(`[scratchpad] ${s}\n`); }
send({ type: "hello", name: "scratchpad", version: "1.0.0",
capabilities: ["commands", "tools"] });
const rl = createInterface({ input: stdin, crlfDelay: Infinity });
rl.on("line", (line) => {
const f = JSON.parse(line);
if (f.type === "hello_ack") {
// f.cwd is the user's project directory.
send({ type: "register_command", name: "note", description: "append a note" });
send({ type: "register_tool", name: "read_notes",
description: "Read the user's scratchpad notes.",
schema: { type: "object", properties: {} } });
send({ type: "ready" });
} else if (f.type === "command_invoked" && f.name === "note") {
send({ type: "command_response", id: f.id, action: "display",
display: `noted: ${f.args}` });
} else if (f.type === "tool_call" && f.name === "read_notes") {
send({ type: "tool_result", id: f.id,
content: [{ type: "text", text: "(notes go here)" }] });
} else if (f.type === "shutdown") {
send({ type: "shutdown_ack" });
rl.close();
}
});tsx install: npm install -g tsx. Without global tsx, fall back
to "exec":"npx","args":["--yes","tsx","index.ts"] (slower
startup; npx checks the registry every launch).
{"name":"hello-py","version":"1.0.0","exec":"./hello.py","language":"python","enabled":true}#!/usr/bin/env python3
import json, sys
def emit(o): sys.stdout.write(json.dumps(o) + "\n"); sys.stdout.flush()
emit({"type": "hello", "name": "hello-py", "version": "1.0.0", "capabilities": ["commands"]})
for line in sys.stdin:
msg = json.loads(line)
if msg["type"] == "hello_ack":
# msg["cwd"] is the user's project directory.
emit({"type": "register_command", "name": "hellopy", "description": "say hi (python)"})
emit({"type": "ready"})
elif msg["type"] == "command_invoked":
emit({"type": "command_response", "id": msg["id"],
"action": "prompt", "prompt": "Say hi briefly."})
elif msg["type"] == "shutdown":
emit({"type": "shutdown_ack"})
breakchmod +x hello.py.
zot ext install ./weather # copy into $ZOT_HOME/extensions/
zot --ext ./weather # run from disk for one zot session (no install)
zot --ext . # cwd is the extension dir
zot ext list # show installed extensions
zot ext logs weather # cat the extension's stderr
zot ext logs weather -f # tail it
zot ext disable weather # keep installed but skip on launch
zot ext enable weather
zot ext remove weatherFor TS / Python extensions, no build step is needed — edit the source in place and relaunch zot.
For Go, run go build -o <name> . in the extension directory after
edits, then zot ext install (which copies the manifest + binary)
or zot --ext . to test from the working tree.
The extension is just a process. Drive it directly with shell pipes to see exactly what's happening on the wire:
{
printf '%s\n' '{"type":"hello_ack","protocol_version":1,"zot_version":"x","provider":"a","model":"o","cwd":"/tmp"}'
sleep 0.2
printf '%s\n' '{"type":"command_invoked","id":"1","name":"weather","args":"Berlin"}'
sleep 0.5
printf '%s\n' '{"type":"shutdown"}'
} | ./weatherCompare what comes out of stdout to the expected wire format. If a
frame doesn't match what zot expects, it's discarded silently and
logged to ext-<name>.log.
command onlytoolevent + interceptzot --ext <path> for testing without committing to an
install.zot ext install <path>.Don't try to write a full SDK or framework on top of the protocol unless the user asked for one — the wire format is small enough that a 30-line raw script is the right answer for most extensions.
© patriceckhart, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in packages/agent/skills/builtin/write-zot-extension of patriceckhart/zot.
Open the folder on GitHubat commit 0f23566
Write Zot Extension next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Zot Extension this skillpatriceckhart/zot | 351 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 11 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Plugin Settings Patternanthropics/claude-plugins-official | 38k | 7 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 38k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 |
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
anthropics/claude-plugins-official
Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
patriceckhart/zot
Help the user create, install, or package zot themes, including theme-only extensions.
Categories
Help the user create a new zot extension (slash command, LLM tool, or guard) in any language. Write Zot Extension is an agent skill from patriceckhart/zot. Help the user create a new zot extension (slash command, LLM tool, or guard) in any language.
Write Zot Extension fits situations like: tasks that involve Hooks and plugins.
Run `npx skills add patriceckhart/zot --skill write-zot-extension -a claude-code`. Or copy the skill folder (packages/agent/skills/builtin/write-zot-extension in patriceckhart/zot) into .claude/skills/write-zot-extension in your project. Claude Code loads it when a task matches its description.
Run `npx skills add patriceckhart/zot --skill write-zot-extension -a codex`. Or copy the skill folder (packages/agent/skills/builtin/write-zot-extension in patriceckhart/zot) into .agents/skills/write-zot-extension in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add patriceckhart/zot --skill write-zot-extension -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-zot-extension, .gemini/skills/write-zot-extension, .github/skills/write-zot-extension and .opencode/skills/write-zot-extension in your project.
Going by SKILL.md and its folder, Write Zot Extension needs the command-line tools its instructions call (go and npm). Our summary lists: Python 3; Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Write Zot Extension is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Write Zot Extension: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
patriceckhart (a GitHub user) maintains it in patriceckhart/zot, which has 351 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.
Source: patriceckhart/zot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.