「pipeline」の検索結果

Detect, respond to, and prevent software supply chain attacks on package registries, container images, and CI/CD pipelines with lockfile auditing, provenance verification, and emergency response playbooks.

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

Automate security workflows and remediation. Build security pipelines, automate compliance checks, and implement SOAR capabilities. Use when scaling security operations or implementing DevSecOps.

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

Secure OpenClaw deployments with preflight hardening checks, CI/CD guardrails, container runtime restrictions, and post-deploy verification. Use when shipping OpenClaw with Docker, Kubernetes, or automated release pipelines.

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

Build and operate Retrieval-Augmented Generation (RAG) infrastructure with vector stores, embedding pipelines, and hybrid search. Covers ingestion, chunking strategies, reranking, and production deployment patterns.

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

Migrate from Terraform to OpenTofu with state compatibility, provider registry setup, and CI/CD pipeline updates. Use when adopting the open-source Terraform fork or evaluating license-free IaC.

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

Build, test, and deploy applications using GitHub Actions workflows. Create CI/CD pipelines, configure runners, manage secrets, and automate software delivery. Use when working with GitHub repositories, automating builds, running tests, or deploying applications.

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

Create and manage Jenkins CI/CD pipelines, configure agents, manage plugins, and automate builds. Use when working with Jenkins servers, creating Jenkinsfiles, or setting up build automation for enterprise environments.

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

Configure GitLab CI/CD pipelines and runners for automated building, testing, and deployment. Create .gitlab-ci.yml configurations, manage runners, and implement DevOps workflows. Use when working with GitLab repositories or self-hosted GitLab instances.

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

Configure CircleCI workflows and orbs for continuous integration and deployment. Create config.yml pipelines, use orbs for reusable configurations, and optimize build performance. Use when working with CircleCI for CI/CD automation.

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

Deploy and manage the ELK Stack (Elasticsearch, Logstash, Kibana) for log aggregation and analysis. Configure log pipelines, create visualizations, and implement log-based monitoring. Use when centralizing logs, implementing search functionality, or building log analytics platforms.

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

Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/). Encodes why the long tail of control-plane capabilities is deliberately NOT wrapped as MCP/CLI tools, the API-first admission test for whether a capability deserves a recipe, the negative and positive lists, the fixed recipe structure, the writing rules distilled from writing-for-agents, the user-facing copy red lines, and the product regeneration/verification pipeline. Also routes contributors (and their agents) to the contribution flow and the pre-PR self-test protocol in references/contributing.md. Use when adding a recipe, judging whether a scenario belongs in the recipe set, updating the recipes index, re-checking existing recipes against the admission test, or onboarding someone who wants to submit one.

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

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

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

Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.

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

Automated content creation pipeline for business growth. Creates blog posts, landing pages, email sequences, social media content, and video scripts with a supply-demand topic gate, 5-dimensional quality diagnosis, one-core resonance check, per-sentence information density scoring, 12-signal authenticity audit, headline impact matrix, content substance scoring, and a cheap-format MVP testing ladder. Use when the user needs content marketing, blog posts, email sequences, copywriting, video scripts, or says 'write content', 'blog post', 'email sequence', 'content calendar', 'marketing copy', 'video script', or 'hook'.

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

Automated outreach and sales pipeline — cold email sequences, partnership outreach, lead generation, and prospect management. Use when the user needs cold email campaigns, sales sequences, lead generation, partnership outreach, B2B sales, or says 'cold email', 'outreach', 'lead gen', 'find prospects', 'sales sequence', or 'partnerships'.

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

Codify a successful workflow from the current conversation into a permanent project-local skill. After you discover (e.g.) a cold-email sequence that converts, an ad-creative format that beats baseline, or a content-pipeline cadence that compounds — /money-skillify writes it as a SKILL.md under the project's local skills directory so future sessions can re-invoke it without re-discovery. Use when the user says: 'this worked, save it', 'codify this', 'turn this into a skill', '把这个固化下来', '存成 skill'.

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

Save the current business state to disk so future Claude Code sessions can pick up where you left off. Captures confirmed conclusions, ruled-out directions, open hypotheses, and the next recommended skill. Use when the user has just reached a conclusion in /money-discover, /money-strategy, /money-diagnose, or any pipeline phase, and wants to lock the state in. Also triggered by: 'save this', 'checkpoint', 'remember this', 'lock it in', '保存', '存档', '记下来', '这个结论留着'.

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

当用户操作 Redis 相关代码（go-redis、Jedis、redis-py、ioredis）时触发。涵盖禁止 KEYS 命令、SCAN 替代、大 key 控制、Pipeline 批量、TTL 规范等安全与性能要点。

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

当用户操作 Redis 相关代码（go-redis、Jedis、redis-py、ioredis）时触发。涵盖禁止 KEYS 命令、SCAN 替代、大 key 控制、Pipeline 批量、TTL 规范等安全与性能要点。

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

Project layout, module architecture, compiler pipeline, and design patterns.

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

Expert guidance for the Fabric CLI (`fab`) and the Fabric and Power BI REST APIs: workspaces, items, lakehouses, notebooks, pipelines, semantic models, reports, capacities, OneLake, deployment and admin. Also estimates the capacity units (CU) an operation will consume and its impact on the capacity before running it. Automatically invoke whenever the user mentions Fabric, Power BI Service, a Fabric or Power BI workspace, a capacity or F SKU, OneLake, `fab`, or asks to create, run, refresh, schedule, deploy or delete anything in Fabric, including preview items such as Plan, Ontology, Graph or Copilot.

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

Use when an agent drives Unity 6.3 (6000.3) on a Mac for any task: batch mode and -executeMethod jobs, a running editor (the user's GUI editor or a headless one), the Unity CLI and com.unity.pipeline, MCP servers, the Test Framework, command-line builds; when a batch run fails silently, 'Scripts have compiler errors', a capture comes back black or pink, or a result must be proven with numbers and a frame; or when a Unity brief must go to the right scenario-unity-* specialist.

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

Use when Godot 4.7 work must run without a mouse or at scale: batch import of hundreds of GLB props or an AI image-to-3D art drop, naming rules, import presets and post-import scripts, editor plugins, EditorScript and @tool, EditorImportPlugin, GUT or gdUnit4 tests in CI, a GitHub Actions export workflow, GDExtension basics, or a Godot MCP server; also when --import is slow, textures stay uncompressed, tests pass locally but CI fails, or an export ships test folders.

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

Use when a task involves running a Scenario workflow through MCP, including anything the user calls a Scenario app, a saved pipeline, or a multi-step generation graph. Triggers include listing workflows, building workflow_run's inputs object, pricing a run with a dry run, approving or rejecting a stuck approval node, a run rejected for input length, or a workflows_list reply flooding the context. Creating or editing graphs is scenario-workflow-authoring. Keywords: workflow, app, approval gate.

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