スキルを探す

自动寻找当前网络环境下最快的 GitHub 代理镜像，用于克隆仓库、下载文件或获取 Release 资产。当需要从 github.com 下载任何内容时使用本 skill——包括 git clone、wget/curl 下载、Release 资产获取等。

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

Secure the path from an inbound event (webhook, email, SMS, GitHub comment, file, cron) to an agent spawn in the Port Daddy fleet. Use when wiring trigger sources to agents, reviewing the io-wiring registry, adding a trust/permission gate, hardening output sinks (SSRF/path traversal), scoping tools by provenance, or proving the spawn path is safe against prompt-injection → tool-abuse. Encodes ADR-0093 and the red-team threat model. NOT for generic Coast Guard sandboxing (ADR-0050), the macaroon push-grant gate alone (ADR-0053), or non-fleet code.

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

Expert DevOps engineer for CI/CD, IaC, Kubernetes, and deployment automation. Activate on: CI/CD, GitHub Actions, Terraform, Docker, Kubernetes, Helm, ArgoCD, GitOps, deployment pipeline, infrastructure as code, container orchestration. NOT for: application code (use language skills), database schema (use data-pipeline-engineer), API design (use api-architect).

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

Interprets GitHub Actions run status and logs, diagnoses CI failure patterns, and suggests targeted fixes. Handles dependency install failures, test timeouts, build OOM, flaky tests, and workflow misconfigurations. Activate on: 'CI failing', 'build broken', 'workflow error', 'GitHub Actions debug', 'flaky CI', 'pipeline timeout', 'CI red'. NOT for: writing new workflows from scratch (use github-actions-pipeline-builder), CI caching strategy (use ci-cache-optimizer), deployment orchestration (use devops-automator).

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

CI/CD caching optimizer for dependency caching, Docker layer caching, and build speed improvements. Activate on: CI cache, build speed, dependency caching, Docker layer cache, turbo remote cache, GitHub Actions cache, pnpm store cache. NOT for: CI/CD pipeline creation (use github-actions-pipeline-builder), deployment strategy (use blue-green-deployment-orchestrator), Docker image building (use docker-multi-stage-optimizer).

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

Cloudflare Pages CI/CD with preview environments, edge functions, and Wrangler automation. Activate on: Cloudflare Pages, Wrangler deploy, preview environment, edge function, Pages project, Cloudflare Workers integration, custom domain on Pages. NOT for: Worker-specific development (use cloudflare-worker-dev), DNS management (use devops-automator), full-stack app frameworks (use vercel-deployment).

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

Author a pull request an AI coding agent can actually get merged: a scoped, coherent diff; a Summary and Test Plan backed by real evidence; correct triage of required-and-blocking CI gates versus external/advisory checks (e.g. a Cloudflare Pages preview build); draft-while-WIP discipline; named fixup commits for real review findings; and a clean landing through a merge queue without force-pushing or bypassing branch protection. Use when opening, updating, triaging red CI on, or landing an agent-authored GitHub PR. NOT for this repo's internal release ceremony, actor embodiments, or contributor mirror-sync mechanics (use port-daddy-internal-dev), tracking backlog/issue lifecycle across a board (use agent-issue-tracker-workflow), or deciding what to build next / sequencing a roadmap (use legible-roadmap-with-sidequests).

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

Research AI coding assistant products, audiences, user stories, social proof, hacks, and unmet needs for apps like Cursor, Claude Code, Codex, Warp Code, Devin, Windsurf, GitHub Copilot, Cline, Aider, and homegrown agent stacks. Use when designing or positioning agentic developer tools, Port Daddy Agent Harbor, swarm consoles, background coding agents, or competitive/product research for AI software engineering. NOT for implementing the coding agent runtime, generic market research, or UX mockups without developer workflow evidence.

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

Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).

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

One-time recovery when a shared checkout has drifted far from GitHub main: hundreds ahead/behind, stacked worktrees and PRs, a dirty tree nobody owns. Use when tempted to reset or force-push. NOT for the ordinary 30-minute release loop (operations/INTEGRATION_MAINTAINER.md).

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

Create a new find-XXXX preprocessor Python script from scratch (no existing SKILL.md), add configs/<GAMEVER>.yaml skill and symbol entries. Covers xref-string-based and LLM_DECOMPILE-based discovery patterns. Use when a GitHub issue or user instruction specifies a new function to find.

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

Create a GitHub pull request from staged task changes or an already-committed current branch. Deliver source/config/ reference changes together with their computed source-owned `bin_artifacts` closure. PR validation routing is owned by the default-branch trusted workflow; snapshots, gamedata, and manifests are Release-derived only.

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

One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.

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

Create and manage teams of specialized AI agents that work together on tasks. Use when setting up multi-agent workflows, agent squads for content/marketing/research pipelines, configuring heartbeat-based agent coordination, or managing agent personalities via SOUL.md files. Enables orchestration of multiple OpenClaw sessions as a coordinated team with shared task systems (Linear, Trello, etc.).

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

Interact with GitHub using the `gh` CLI. Use when managing issues, PRs, workflow runs, or advanced API queries via `gh issue`, `gh pr`, `gh run`, and `gh api`.

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

Marpテーマのビルドパイプライン構築。SCSS→CSSコンパイル、サンプル画像生成、Makefile設定、Git hook、GitHub Actions CI設定を支援。「テーマのビルド環境を整備」などのリクエスト時に使用。

リリース単位（単一パッケージか monorepo か）を判定し，SemVer でバージョンを上げ（マニフェストと全参照箇所を整合），bump コミット・タグ・push・About 欄・GitHub Release までの文面を提案．承認後に一気に実行する．「リリースして」「公開して」「バージョンを上げて」など版を公にすることを求められたときに使う．記録するだけなら /capstone:commit を使う．

This skill should be used when the user asks to "既存プロジェクトのタスクを整理して", "技術的負債をIssue化して", "このコードベースを改善するタスクを洗い出して", "GitHub Projectに健全化タスクを登録して", "break down what needs to be fixed in this project", "surface tech debt as issues", or "create a project board for cleanup work". Diagnoses pain points and codebase health of an existing project, then registers improvement tasks as GitHub Issues and a Project Board.

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

This skill should be used when the user asks to "PR を出す前に確認して", "check if this branch is ready to merge", "run pre-PR checks", "PRを作る前にチェックして", or wants to verify a branch before opening a pull request. Executes verification commands, validates Conventional Commits format, and confirms documentation is updated, then reports whether gh pr create is safe to run.

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

This skill should be used when the user asks to "これらのIssueを全部実装して", "implement these issues autonomously", "Issue一覧を自動で片付けて", "これらのタスクを順番に実装してPRにして", or provides a list of GitHub Issue numbers/URLs for autonomous batch implementation. Fetches all specified Issues, resolves dependency order, then iterates through each — creating a worktree, implementing, and opening a PR — without user intervention.

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

Guide the user through starting a new web application project — elicit requirements (MoSCoW scoping), create architecture and requirements documents, break work into tasks, and register them as a GitHub Project kanban board. Use when the user says "新しいWebアプリを作りたい", "Webアプリの立ち上げを手伝って", "start a new web app project", "プロジェクトの要件を整理したい", or "GitHub Projectにタスクを登録したい".

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

This skill should be used when the user asks to "最小再現環境を作って", "再現環境を構築して", "問題を切り分けたい", "パッケージの不具合か確認したい", "create a minimal reproduction", "isolate the issue", "build a repro environment", "reproduce this bug", "narrow down the cause", "is this a package bug or my code", "このPRの問題を再現して", "this commit broke something", or wants to determine whether a bug is caused by a package, the environment, or application code. Accepts PR URLs, commit hashes, or branch names as input.

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

This skill should be used when the user asks to "このIssueを実装して", "implement this issue", "fix this bug", "このタスクをやって", "Issue

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

Git Flow ワークフローで開発からdevelopへのマージまでを実行。 「フィーチャーブランチ作って」「PR出して」「コードレビューして」「マージして」などのリクエスト時に使用。 開発中の差分がある状態からブランチを作成します。 develop → main のリリースフローもサポート。 ※ develop → main のマージは人間が実行します。