5,635 件 ・ 関連度順
概要と使いどころ
Use this skill when reviewing, designing, or improving a workshop, lesson, training session, facilitation plan, talk, or educational explanation. Use it when the user provides a topic, concept, or explanation and wants better framing questions, curiosity hooks, opening prompts, discussion questions, learner reflection prompts, or ways to make participants think before being taught.
日本語の概要は準備中です。原文の説明を表示しています。
Assess and address review feedback on GitHub PRs, GitLab MRs, or in conversation. Use when checking new reviews, responding to comments, rechecking after a push, or following up on approvals and change requests.
日本語の概要は準備中です。原文の説明を表示しています。
Relay agent results without corrupting exact counts, failure reasons, source scope or status. Use when receiving agent output or handing results to another actor; distinguish observations from attributed conclusions and reference complete artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Runs structured Python cleanup and modernization — static analysis via prek/ruff, smell investigation to root cause, typed-boundary hardening by inventorying Any usage, and modernization within the project's requires-python lane. Use when refactoring Python code, removing dead code, hardening type boundaries, or running a modernization pass on a file or scope.
日本語の概要は準備中です。原文の説明を表示しています。
Review pytest test effectiveness against authoritative contracts, relevant faults, behavior-preserving refactors, realistic boundaries, isolation, and diagnostics. Use for test-quality audits, coverage-gap reviews, regression-test changes, or mocking reviews; preserve existing project gates rather than inventing coverage targets.
日本語の概要は準備中です。原文の説明を表示しています。
Activates on any Python task involving *.py files, uv, ruff, ty, pytest, or pyproject.toml — loads the shared Python 3.11+ standards and routes the task to the specialist skill that applies them: TDD, CLI, web, data, async, typing, packaging, publishing, documentation sites, test design, test-failure analysis, or stdlib-only constrained environments.
日本語の概要は準備中です。原文の説明を表示しています。
Validates and corrects Python shebangs and PEP 723 inline script metadata by applying four shebang-selection rules. Use when auditing or fixing shebangs in Python files — choosing between plain python3 and the uv shebang for standalone scripts with external dependencies, adding or removing PEP 723 metadata blocks to match actual import requirements, checking execute bit presence, or avoiding redundant transitive dependencies when typer is declared.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize CLAUDE.md files and Skills for Claude Code CLI. Use when reviewing, creating, or improving system prompts, CLAUDE.md configurations, or Skill files. Transforms negative instructions into positive patterns following Anthropic's official best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the full plugin development lifecycle from blank canvas to marketplace-ready. Use when creating a new plugin, improving an existing plugin, fixing validation errors, or taking a plugin through assessment, research, design, creation, debugging, optimization, and verification. Complements /plugin-creator:plugin-creator which provides the detailed new-plugin creation workflow with discussion capture, parallel research, and atomic implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Code plugin and marketplace router. Use when creating plugins, configuring component paths, resolving installed files, validating plugin roots, or distributing local, Git, and archive sources.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and improve processes or systems using an explicit semantic model, adaptive instruction resolution, evidence-driven change, and claim-level validation. Use when reviewing process quality, resolving ambiguity or gaps, deciding how much procedural detail is necessary, or validating consequential process behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize existing CLAUDE.md, SKILL.md, agent definitions, and other AI-facing files for Claude comprehension and economy. Scope: optimization of existing content only — not upstream sync, not read-only auditing. Measures baseline metrics, delegates to the ai-doc-optimizer agent with file-type-specific context, runs independent verification via second agent, measures post-optimization metrics, and presents comprehensive before/after report. Supports iterative mode for large targets. Use when improving prompt effectiveness, reducing token waste, or rewriting instructions for LLM consumption. Invoke with /optimize-claude-md <file-or-directory>.
日本語の概要は準備中です。原文の説明を表示しています。
Synchronize existing documentation with an observed code/configuration/API change while preserving each document's purpose and authority. Use after implementation changes can make documentation stale, incomplete, or internally inconsistent.
日本語の概要は準備中です。原文の説明を表示しています。
Scientific validation protocol for verifying fixes work through observation, not assumption. Use when claiming a bug fix, code change, refactoring, or implementation is complete — enforces reproduce-broken-state then define-success-criteria then apply-fix then verify-outcome. Success means observing intended behavior, not absence of errors.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or validating GitLab CI/CD and automatic release lifecycles, inspecting pipeline and job state read-only, composing non-interactive merge-request commands, or setting up protected refs and release credentials. Also covers reusable components and inputs, GitLab Functions, gitlab-ci-local, glab command composition, and GitLab Flavored Markdown. For pipeline execution or retry requests, provide inspection and command drafting while leaving execution to the operator.
日本語の概要は準備中です。原文の説明を表示しています。
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.
日本語の概要は準備中です。原文の説明を表示しています。
Review test effectiveness against authoritative contracts, relevant fault detection, refactor tolerance, boundary fidelity, isolation, and diagnostic value. Use when auditing test quality, reviewing coverage gaps, improving regression protection, or assessing tests after a change.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate and iterate on the SDLC Layer Separation Architecture implementation. Runs validation checks (cross-references, doc completeness, layer metadata, integration points), produces a findings report, and supports iterative fixes. Use when validating first-pass implementation, before claiming layer work is complete, or when improving layer docs/schema.
日本語の概要は準備中です。原文の説明を表示しています。
Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a referee report for a journal editor. Produces a recommendation, claim-and-design summary, three to six decision-driving concerns, additional concerns, and a revision plan through five parallel adversarial finders, Breaker, Butcher, Shredder, Void, Situator, a Blue Team error filter, Chief Reviewer synthesis, Tone Guard legal pass, and optional confidential editor note. Use when the user has been asked to referee a manuscript. Self-audits go to paper-review-lite or presubmit, and author responses go to referee-response.
日本語の概要は準備中です。原文の説明を表示しています。
Plans a research project as a decision map that persists across sessions, resolving one ticket per session until the design is defensible and pre-registerable. The map lives as Markdown in the repository, literature sweeps run as parallel research tickets, and the resolved map compiles into a pre-analysis plan. Use at project start, when a design has more open decisions than one conversation can hold, or when planning restarts each session. Not for executing analyses or writing the paper.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a methods section against a 45-item checklist drawn from the APSA Experimental Section rubric, JARS-Quant, CONSORT, and DA-RT. Use before submission or archiving, or to document a pre-analysis-plan deviation.
日本語の概要は準備中です。原文の説明を表示しています。
Plans a research project as a durable decision map, resolving one design decision per session until the design is defensible and pre-registerable. Use at project start, when a design has more open decisions than one conversation holds, or when planning keeps restarting. Not for running analyses or writing the paper.
日本語の概要は準備中です。原文の説明を表示しています。
Select, define, create, inspect, update, attach, detach, and verify reusable Vapi tools through the public API. Use for native call-control tools, supported provider integrations, API Request tools, custom function tools, MCP tools, tool messages, credentials, or configuration-preserving assistant attachment changes.
日本語の概要は準備中です。原文の説明を表示しています。