2,769 件 ・ 関連度順
概要と使いどころ
~/.claude/skills/ や任意のパスにあるスキルを claude-code-plugin リポジトリの 正しいディレクトリ構造 (<category>/<name>/skills/<name>/SKILL.md) にコピー・配置するスキル。 スキルの構造検証、既存スキルとの重複チェック、配置後の確認も行う。 Use when: スキルをプラグインリポジトリに公開したい、スキルを移動したい、 スキルをパッケージ化したい、スキルを整理したい。 Triggers: "スキルを公開", "プラグインに追加", "skill publish", "スキルを移動", "claude-code-plugin に追加", "スキルをコピー", "パッケージ化"
How to develop, modify, and extend the Claude Code codebase following its established programming style, patterns, and conventions. Use this skill whenever working on the claude-code source — adding tools, commands, utils, components, types, hooks, services, or fixing bugs. Also use when the user asks about claude-code architecture, coding standards, file organization, or wants to understand how the codebase works. This skill ensures all contributions match the existing codebase style exactly.
日本語の概要は準備中です。原文の説明を表示しています。
[Internal] claude-code-plugin リポジトリの marketplace 構造を検証し、 エラーを自動修正するスキル。CI バリデーション (validate-marketplace.sh) と 同等のチェックをローカルで実行し、missing plugin.json、未登録スキル、 frontmatter 不備、不正キーなどを検出・修正する。 Use when: marketplace を検証したい、CI が失敗した、バリデーションしたい、 プラグイン構造をチェックしたい、plugin.json がない、publish 後の確認。 Triggers: "validate", "バリデーション", "検証", "CI失敗", "CI fix", "marketplace check", "構造チェック", "plugin.json missing", "CI エラー"
Hook スクリプトを claude-code-plugin リポジトリの正しい構造に配置するスキル。 hook の構造検証、既存 hook との重複チェック、plugin.json 生成、marketplace.json 登録を行う。 Use when: hook をプラグインリポジトリに公開したい、hook を移動したい、hook をパッケージ化したい。 Triggers: "hook を公開", "hook publish", "hook をプラグインに追加", "PostToolUse hook を配置", "hook をコピー", "hook publisher"
Claude Code (code.claude.com) のデプロイ・CI/CD リファレンス。 Amazon Bedrock / Google Cloud Agent Platform (Vertex AI) / Microsoft Foundry / Claude Platform on AWS 経由、Claude apps gateway、LLM gateway (protocol / rollout)、 GitHub Actions (claude-code-action) / GitLab CI/CD / GitHub Enterprise Server (GHES)、 code review 自動化・ultrareview、Slack (Claude Tag)、headless mode、cloud environments、 devcontainer、self-hosted environments（runner 構成・identity 検証・本番デプロイ）。
Development skill from everything-claude-code
日本語の概要は準備中です。原文の説明を表示しています。
Routes Claude Code: plugin/Skill repair, marketplace, statusline, model profiles/source sync, 1M/[1m] context, usage/quota reset ping, memory→docs, .txt repair, turning auto memory off. Reads one bundled specialist; history, hooks, and Lark keep their own entries.
日本語の概要は準備中です。原文の説明を表示しています。
睡前/离开前额度耗尽时，设置一次性本机定时器，在 Claude 订阅额度重置后自动发一条极简 claude -p 消息，立刻开启新的 5 小时用量窗口——用户睡醒时新窗口已跑掉大半，等于白赚一个 冷却期。Use when 用户说「还有 X 小时重置额度，帮我定时戳一下 Claude」「我去睡觉了， 到点 ping 一下开启新窗口」「额度用完了，重置后帮我踩个点」「设个定时器开启新的 5 小时 冷却期」，或提到 定时戳、戳 Claude、quota ping、开窗、额度重置后自动发消息。 仅限一次性定时任务与 macOS 本机（caffeinate/BSD date）；周期性任务用 /loop 或 cron， 查询 ChatGPT/Codex 何时重置用 tibo-reset-codex，分析额度为什么烧完用 claude-usage-analyst。
日本語の概要は準備中です。原文の説明を表示しています。
Reads, searches and exports local OpenAI Codex history without continuing work: session inventory, timelines, verbatim user input, indexed search, and rollout identity/fork lineage. Use when the user asks what they told Codex, wants a Session ID, or evidence of what a run did. Not for Claude Code (use read-claude-code-history); with no platform named, start at local-conversation-history.
日本語の概要は準備中です。原文の説明を表示しています。
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).
日本語の概要は準備中です。原文の説明を表示しています。
Reads or exports the COMPLETE transcript of a Claude.ai web conversation — private /chat/... and public /share/... links — via Claude.ai's internal API in the user's logged-in Chrome, plus its files. Use when the user pastes a claude.ai link and asks to read, summarize, export, archive, or extract it — "读这个对话", "导出网页版对话", "拉到本地". Local sessions: read-claude-code-history; exported files: claude-export-txt-better.
日本語の概要は準備中です。原文の説明を表示しています。
Fixes broken line wrapping in Claude Code exported .txt conversation files — rebuilds tables, paragraphs, paths and tool calls hard-wrapped at a fixed width. Use for an export (YYYY-MM-DD-HHMMSS-*.txt) with broken tables, split paths, or mangled tool output, or "fix export" / "make export readable". Not for a live web conversation (use read-claude-web-conversation) or session history (use read-claude-code-history).
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes or restructures CLAUDE.md/AGENTS.md with progressive disclosure and zero information loss. Use when the user asks to optimize, audit, 精简/瘦身/重构, or split instruction files, asks for their best practices (最佳实践), sees Memory files taking a large share of /context, reports rules in instruction files being ignored, or a task starts moving instruction sections. Not for generic task drift unless instruction files are in scope; not for moving memory entries into docs (use claude-code-ops-router).
日本語の概要は準備中です。原文の説明を表示しています。
Writes, tests, registers and debugs Claude Code hooks (PreToolUse, PostToolUse, SessionStart, Stop) that turn a rule the model keeps breaking into a hard gate. Use when the user wants to block or intercept a tool call, add a guard rail, fix a misfiring hook, or says 拦截 / 守卫 / 钩子 — including "make it stop doing X".
日本語の概要は準備中です。原文の説明を表示しています。
Reads, searches and exports local Claude Code and Kimi CLI history without resuming work: timelines, verbatim user input, keyword or fuzzy recall, file recovery from transcripts, and which session ran a given command in a known time window. Use when the user asks what was said, wants a session ID or original context, needs proof of what a session contained, or needs past-session runtime evidence about commands, tool calls and hook runs — query this index instead of raw-scanning transcript files. Not for Codex (use read-codex-history); with no platform or several named, start at local-conversation-history.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "optimize CLAUDE.md", "create a new skill", "write a custom agent", "configure hooks", "manage context window", "set up MCP servers", "scaffold a skill package", "analyze token budget", "create subagents", "configure permissions", "set up worktrees", or "integrate Claude Code with editors". Covers Claude Code CLI mastery, skill authoring, context engineering, hooks automation, subagent creation, and development workflow optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in integrating Claude Code with CI/CD pipelines. Covers headless mode for non-interactive execution, GitHub Actions and GitLab CI/CD integration, automated code review, issue triage, and PR workflows. Essential for teams wanting AI-powered automation in their development pipelines. Use when "claude code CI/CD, headless mode, GitHub Actions claude, GitLab CI claude, automated code review, PR automation, issue triage, claude-code, cicd, automation, github-actions, gitlab, headless, pipeline, devops" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in creating custom slash commands for Claude Code. Slash commands encode repeatable workflows as markdown files, turning complex multi-step processes into simple one-line invocations. Essential for team standardization, onboarding, and reducing cognitive load during development. Use when "custom command, slash command, workflow template, /command, claude command, project commands, team workflows, claude-code, commands, slash-commands, workflow, automation, templates, productivity" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in Claude Code hooks - user-defined shell commands that execute at specific points in Claude Code's lifecycle. Provides guaranteed automation that doesn't rely on the LLM "remembering" to do something. Essential for enterprise workflows, code quality enforcement, and deterministic behavior in agentic coding. Use when "claude code hooks, automate claude, block tool use, pre tool use, post tool use, session start hook, claude lifecycle, claude-code, automation, hooks, lifecycle, cli, workflow, devtools" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
日本語の概要は準備中です。原文の説明を表示しています。
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
日本語の概要は準備中です。原文の説明を表示しています。
Look at real hardware, screens, panels, and wiring on a desk or workbench through a camera, so Claude can SEE physical output that no unit test, log, or API can. Use whenever the user says "are you seeing this?", "olha isso", "look at this", "watch this", "can you see...", "check the camera", "look at the screen" / "look at the display", "is this wired right?", or "what's this part?"; asks to visually verify a rendered display, LCD, LED, or panel; wants a wiring, polarity, or voltage-rail check before power-on; or needs to confirm a font, layout, clipping, or on-screen value renders correctly instead of trusting green tests. Grabs the current camera frame(s) and reads them; supports a watch mode for an action in progress. Needs a snapshot-capable camera reachable over HTTP (Android IP Webcam app, Raspberry Pi camera-streamer, or any snapshot URL) set via CCE_CAM_URL.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or review a Claude Design brief and convert its output into a deterministic SwiftUI implementation handoff with native iOS layout, tokens, states, transitions, and accessibility rules. Use for Claude Design mobile prototypes, three-screen iOS concepts, Design-to-Claude-Code handoffs, or when a visual prototype must be buildable without interpretation.
日本語の概要は準備中です。原文の説明を表示しています。