1,912 件 ・ 関連度順
概要と使いどころ
Hook system fundamentals — all events, configuration structure, matchers per event type, environment variables, execution behavior, security, and debugging. Use when creating hooks, understanding hook events, matchers, configuration locations, environment variables, or troubleshooting hook issues.
日本語の概要は準備中です。原文の説明を表示しています。
Install and configure the GitHub CLI (gh) for AI agent environments where gh may not be pre-installed and git remotes use local proxies instead of github.com. Use when gh command not found, shutil.which returns None, need GitHub API access for issues or PRs or releases or workflow runs, or repository operations fail with 'failed to determine base repo' error. Provides auto-install script with SHA256 verification, GITHUB_TOKEN auth with anonymous fallback, and the required -R flag pattern for proxy environments. Covers project management via GitHub Projects V2, milestones via REST API, issue lifecycle templates, and label taxonomy management.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a git worktree for parallel feature development. Use after planning to prepare an isolated development environment with all necessary environment files.
日本語の概要は準備中です。原文の説明を表示しています。
Operate E2B agent sandboxes using the CLI. Use when user needs to run code in isolation, test packages, execute commands safely, or work with binary files in a sandbox environment. Keywords: sandbox, e2b, isolated environment, run code, test code, safe execution.
日本語の概要は準備中です。原文の説明を表示しています。
Bedrock is a WordPress boilerplate with Composer-based dependency management, environment-specific configuration via .env files, and an improved folder structure. It separates WordPress core from application code for cleaner version control and deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Scan Python requirements and environments for known vulnerable or malicious packages before they move further through delivery or promotion workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Check Python environments and requirements files for published vulnerabilities before shipping, upgrading, or approving dependency changes.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates local Kubernetes development environment management.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and manage Netlify projects using Next.js with serverless functions, environment variables, and continuous deployment. Use this skill when working with Netlify deployments, configuring netlify.toml, managing Netlify Functions, debugging webhooks, setting environment variables, or troubleshooting deployment issues for Next.js applications on Netlify. Essential for Twilio-Aldea and similar serverless SMS/telephony projects. v2.0 includes official Netlify documentation, production patterns from Twilio-Aldea (webhook timeout solutions, background functions), and TypeScript code examples.
日本語の概要は準備中です。原文の説明を表示しています。
Audits Claude Code repositories. Two-phase workflow — Phase 1 sweeps 14 hygiene categories (permissions, hooks, CLAUDE.md bloat, Skills hygiene, process-abstraction, plus structural) and an optional 7-layer leak check. Phase 2 executes [APPROVED] markers from the report file. Use for repo cleanup, pre-distribution sanity, post-feature hygiene, environment audit, process-abstraction discovery. Trigger on "audit my CC repo," "sweep my repository for hygiene," "check this CC environment," "find process abstraction candidates," "review my CLAUDE.md," "clean up my .claude directory," "pre-distribution hygiene check," "find layer leaks in my CC setup." Routes structural findings to rootnode-cc-design REMEDIATE. Composes with rootnode-critic-gate. CC-only — does not scan Claude Projects. Do NOT use for building a Skill (use rootnode-skill-builder), compiling a prompt (use rootnode-prompt-compilation), scoring a single prompt (use rootnode-prompt-validation), or auditing a Project (use rootnode-project-audit).
日本語の概要は準備中です。原文の説明を表示しています。
Run the jigsawR test suite via WSL R execution. Supports full suite, filtered by pattern, or single file. Interprets pass/fail/skip counts and identifies failing tests. Never uses --vanilla flag (renv needs .Rprofile for activation). Use after modifying any R source code, after adding a new puzzle type or feature, before committing changes to verify nothing is broken, or when debugging a specific test failure.
日本語の概要は準備中です。原文の説明を表示しています。
Preserve and conserve library and archival materials. Covers environmental controls (temperature, humidity, light), handling procedures, book repair techniques (torn pages, loose spines, foxing), acid-free storage, digitization for preservation, and disaster recovery planning. Use when establishing preservation practices for a new or existing collection, when materials show signs of deterioration, when setting up environmental controls for storage, when planning digitization to preserve fragile originals, or when creating a disaster recovery plan for a library or archive.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct structured insect behavior observations using sampling protocols, ethogram categories, event recording, interaction logging, environmental context, and summary analysis. Covers focal animal sampling, scan sampling, all-occurrences sampling, and instantaneous sampling methods. Defines a standard insect ethogram with locomotion, feeding, grooming, mating, defense, communication, and rest categories. Includes timestamped event recording, intraspecific and interspecific interaction logging, environmental covariate documentation, and time budget analysis. Use when studying insect behavior for ecological research, documenting behavioral repertoires for a species, observing pollinator activity or predator-prey dynamics, or supporting conservation assessments with behavioral data.
日本語の概要は準備中です。原文の説明を表示しています。
Implement GitOps continuous delivery using Argo CD or Flux with app-of-apps pattern, automated sync policies, drift detection, and multi-environment promotion. Manage Kubernetes deployments declaratively from Git with automated reconciliation. Use when implementing declarative infrastructure management, migrating from imperative kubectl commands to Git-driven deployments, setting up multi-environment promotion workflows, enforcing code review gates for production, or meeting audit and compliance requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Install and configure the putior R package for workflow visualization. Covers CRAN and GitHub installation, optional dependencies (mcptools, ellmer, shiny, shinyAce, logger, plumber2), and verification of the complete annotation-to-diagram pipeline. Use when setting up putior for the first time, preparing a machine for workflow visualization tasks, when a downstream skill requires putior to be installed, or restoring an environment after an R version upgrade or renv wipe.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy a Next.js application to Vercel. Covers project linking, environment variables, preview deployments, custom domains, and production deployment configuration. Use when deploying a Next.js app for the first time, setting up preview deployments for pull requests, configuring custom domains, or managing environment variables in a production Vercel deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Create multi-stage Dockerfiles that separate build and runtime environments for minimal production images. Covers builder/runtime stage separation, artifact copying, scratch/distroless/alpine targets, and size comparison. Use when production images are too large, when build tools are included in the final image, when you need separate dev and prod images from one Dockerfile, or when deploying to constrained environments like edge or serverless.
日本語の概要は準備中です。原文の説明を表示しています。
Scaffold a new R package with complete structure including DESCRIPTION, NAMESPACE, testthat, roxygen2, renv, Git, GitHub Actions CI, and development configuration files (.Rprofile, .Renviron.example, CLAUDE.md). Follows usethis conventions and tidyverse style. Use when starting a new R package from scratch, converting loose R scripts into a structured package, or setting up a package skeleton for collaborative development.
日本語の概要は準備中です。原文の説明を表示しています。
FastAPI-specific delta on top of python-foundation:sqlalchemy-patterns: async engine and AsyncSession lifecycle, get_db dependency injection, async-safe lazy loading rules, async Alembic env.py wiring. Used by fastapi-architect (model definitions) and alembic-specialist (column type finalization and migration generation). Activated automatically by fastapi-plugin/stack.md. Use this skill to: - Manage async database sessions with AsyncSession and async_sessionmaker. - Inject sessions into routes via the get_db() dependency. - Apply async-safe lazy loading (lazy="selectin" or "raise"; never sync lazy loads). - Integrate async Alembic env.py for migration autogeneration. Do NOT use this skill for: - Framework-agnostic model, column, relationship, and querying rules — see python-foundation:sqlalchemy-patterns (load it first). - FastAPI routing and Pydantic schemas — see fastapi-plugin:fastapi-conventions. - Alembic migration execution (that's alembic-specialist's job) — this skill covers definitions.
日本語の概要は準備中です。原文の説明を表示しています。
Python project tooling: pyproject.toml as the single source of truth, package managers (pip, Poetry, uv, pipenv), virtual environments, lockfiles, ruff (lint + format), mypy (type checking), and console scripts / entry points. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Read pyproject.toml (or requirements.txt / Pipfile) to learn which package manager and Python version the project uses. - Install, add, and remove dependencies with the project's package manager. - Run ruff for formatting and linting, mypy for type checking. - Define console scripts and entry points for CLI applications. Do NOT use this skill for: - Language idioms — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing. - Framework-specific tooling (django management commands, flask CLI) — see framework plugin skills.
日本語の概要は準備中です。原文の説明を表示しています。
Set up a new git worktree for parallel development. Creates the worktree, copies .env files, installs dependencies, and generates Prisma client. TRIGGER when user asks to set up a worktree, work on a branch in isolation, or needs a separate environment for a branch or PR.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to review learning progress after a milestone. Not for engineering retrospectives, use engineering-retrospective. For agent-environment ones, use agent-environment-retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user requests an engineering retrospective for a period. Not for agent-environment retrospectives: use agent-environment-retrospective. For learning milestones: use learning-retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
日本語の概要は準備中です。原文の説明を表示しています。