「env」の検索結果

Run x86 Linux binaries in the browser via WebAssembly. Self-host development environments, interpreters, and even this skill itself.

日本語の概要は準備中です。原文の説明を表示しています。

This skill integrates **Boxxy sandbox boundary testing** with the complete Trail of Bits firmware extraction methodology. Use this for extracting and analyzing firmware in heavily obfuscated, containerized, or restricted environments.

日本語の概要は準備中です。原文の説明を表示しています。

Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API.

日本語の概要は準備中です。原文の説明を表示しています。

Interact with Azure DevOps repositories, pull requests, and APIs using the AZURE_DEVOPS_TOKEN environment variable. Use when working with code hosted on Azure DevOps or managing Azure DevOps resources.

日本語の概要は準備中です。原文の説明を表示しています。

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

日本語の概要は準備中です。原文の説明を表示しています。

Implement affective valence as directional derivative of interoceptive energy landscapes for AI alignment. Use when building alignment-aware RL agents, validating GF(3) conservation in reward signals, training Langevin-based policies, or analyzing fold-change detection signals in POMDP environments.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Use when writing Python scripts that must run on Windows, Linux, and macOS — especially when Rich or Typer output breaks on Windows, when dealing with Unicode/encoding errors, ANSI escape handling, terminal detection, path separators, or console color support. Provides verified cross-platform patterns covering stdout/stderr encoding guards, Windows console quirks, terminal capability detection, and portable I/O for CLI, TUI (Rich/Textual), and GUI environments.

日本語の概要は準備中です。原文の説明を表示しています。

Use when building or debugging Typer/Rich CLI applications. Activates on Rich table rendering, console output in non-TTY environments, CliRunner testing with Rich output, snapshot testing, Typer command wiring, exception chain prevention with AppExit/AppExitRich patterns, table width at 80-column wrapping, Progress/Live in non-interactive contexts, stderr/stdout separation, or force_terminal vs width configuration. Grounds AI-generated CLI code in verified correctness patterns and prevents known Typer/Rich integration mistakes.

日本語の概要は準備中です。原文の説明を表示しています。

Integrate MCP servers into Claude Code plugins — covers .mcp.json configuration, plugin.json mcpServers field, server types (stdio, SSE, HTTP, WebSocket), environment variable expansion, tool naming conventions, OAuth and token authentication, security best practices, and testing workflows. Use when adding an MCP server to a plugin, configuring MCP authentication, debugging MCP tool discovery, setting up Model Context Protocol integration, or choosing between stdio and SSE transport types.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews Node.js runtime behavior in JavaScript or TypeScript, including server entrypoints, route handlers, middleware, streams, processes, dependencies, and environment configuration. Loads alongside language and CLI checks when applicable; investigates blocking I/O, backpressure, injection, lifecycle leaks, and misleading failure signals.

日本語の概要は準備中です。原文の説明を表示しています。

Register a plan artifact via the MCP backlog server. Use when you produce a document or report that downstream agents or worktree-isolated environments need to retrieve — feature-context, codebase-analysis, architect, T0-baseline, TN-verification, or research artifacts. Triggers include "store an artifact", "register a plan artifact", "write a report to the backlog", "upload artifact content".

日本語の概要は準備中です。原文の説明を表示しています。

Spawns full Claude Code peer sessions in separate terminal panes and git worktrees, real sessions rather than subagents, each with a directed task and contract brief, monitored and merged by the spawning lead. Detects the environment and uses herdr first, then tmux, then a native claude background agent. Use when work must persist or run beside the current session, needs a separate worktree or permission settings, should remain user-steerable in a visible pane, or when the user asks to spawn, hand off, or parallelize full sessions. Also spawns Codex peers into those panes. Excludes bounded consults and subagent-scale work.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deploying to production environment

日本語の概要は準備中です。原文の説明を表示しています。

Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.

日本語の概要は準備中です。原文の説明を表示しています。

Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Managing local .NET tools with dotnet-tools.json for consistent tooling across development environments and CI/CD pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

Configure Aspire AppHost to emit explicit app config via environment variables; keep app code free of Aspire clients and service discovery.

日本語の概要は準備中です。原文の説明を表示しています。

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

日本語の概要は準備中です。原文の説明を表示しています。

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

日本語の概要は準備中です。原文の説明を表示しています。

Security best practices and guidelines for the Jarvy CLI codebase - a cross-platform development environment provisioning tool that executes system commands with elevated privileges

日本語の概要は準備中です。原文の説明を表示しています。

Testing guidelines for Jarvy CLI - unit testing patterns, integration tests with assert_cmd, test environment variables, platform-specific testing, and CI coverage strategies.

日本語の概要は準備中です。原文の説明を表示しています。

Use whenever the user wants to find, shortlist, vet, or enrich US engineering firms — civil, structural, MEP, mechanical, electrical, geotechnical, transportation, environmental, and manufacturing. **For real-world engineering (buildings, infrastructure, manufacturing) — NOT software engineering.** Triggers on "find civil engineering firms in Florida for transportation", "shortlist three structural engineering firms with high-rise experience", "MEP consultancy for a hospital project", or "pull contact info for these 12 engineering firm domains", even when described indirectly (PE-stamped drawings, building-permit review). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer software-dev / "engineering team" / SaaS-architecture asks to find-software-developer. Skip in-house engineering-manager hires, DIY questions, software-product comparisons (Revit, AutoCAD), non-US firms, individual freelancers.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain the opt-in encrypted Documents API, immutable account ownership, SQLite ciphertext storage, chunk transactions, recipient key envelopes, configuration parser, and TLS/browser cryptographic tests. The separately maintained React application has its own integration skill.

日本語の概要は準備中です。原文の説明を表示しています。