9,530 件 ・ 関連度順
概要と使いどころ
Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
日本語の概要は準備中です。原文の説明を表示しています。
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
日本語の概要は準備中です。原文の説明を表示しています。
Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
日本語の概要は準備中です。原文の説明を表示しています。
Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
日本語の概要は準備中です。原文の説明を表示しています。
Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
日本語の概要は準備中です。原文の説明を表示しています。
Universal desktop application controller for Windows. Automate any desktop app — send messages, click buttons, type text, take screenshots, and interact with native Windows applications. Use this skill when the user asks to: "control my computer", "automate desktop", "send a message on [any chat app]", "click on [something]", "type into [app]", "take a screenshot", "操控电脑", "自动化桌面", "给某某发消息", "打开某某软件", "截个屏", or any task involving interacting with Windows desktop applications. WeChat triggers: "send a WeChat message", "message someone on WeChat", "打开微信发消息", "给某某发微信", "微信发送", "微信发消息", "用微信发", "帮我发微信". Email/Web triggers: "打开邮箱", "发邮件", "send email", "open browser", "操控浏览器", "网页操作". Supports: WeChat, WeCom, DingTalk, Feishu/Lark, QQ, Telegram, Slack, Teams, any browser-based web app, and any other Windows desktop application. Inspired by OpenAI's playwright-interactive skill, combining code-based automation with visual screenshot feedback loops. ROUTING: For web/Electron apps (email, Slack, browser), prefer Playwright with CSS selectors for speed and precision. For native desktop apps (WeChat, QQ, DingTalk), use Win32 API automation.
日本語の概要は準備中です。原文の説明を表示しています。
Zotero ローカル API + REST API (Web API v3) 連携スキル。DOI からの文献一括インポート、コレクション管理、アイテム検索・一覧表示を行う。 REST API 経由でコレクション作成・アイテム CRUD・タグ管理・添付ファイルアップロード・グループライブラリ操作も可能。 Use when: (1) DOI リストから Zotero に文献を登録する, (2) Zotero のコレクション一覧・アイテム一覧を取得する, (3) BibTeX/RIS データを Zotero にインポートする, (4) CrossRef API で文献の DOI を検索する, (5) REST API でコレクション作成・アイテム追加・タグ管理を行う, (6) グループライブラリを操作する。 Triggers: "zotero", "文献登録", "DOI インポート", "コレクション", "論文追加", "文献管理"
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until it reaches the repository's configured Greptile merge threshold with zero unresolved actionable comments, or until the five-review maximum is reached. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review only for new head SHAs unless a 5/5 score is already published, and repeats. Use when the user wants to optimize a PR/MR/CL against Greptile's code review standards without creating runaway review loops.
日本語の概要は準備中です。原文の説明を表示しています。
Load this skill whenever the project contains tooltip components, hover- triggered informational popups, title attribute tooltips, or any content revealed on hover or focus. Under no circumstances create tooltips that are only triggered by hover without keyboard equivalent access. Absolutely always ensure tooltips are dismissible, persistent enough to read, and not the sole source of essential information.
日本語の概要は準備中です。原文の説明を表示しています。
Before improving anything, show the spread of what can concretely be done on this specific input — a short menu of 3-5 interventions from lightest to heaviest touch, then wait for the user to pick. Domain-agnostic; works on any material the user hands over. Trigger when the user says "spread", "show me my options", "what can you do with this", or asks to improve or fix something without specifying how. Do NOT trigger when the user has already named a specific fix — then just do the fix.
日本語の概要は準備中です。原文の説明を表示しています。
Use when [trigger symptoms, user intents, task contexts]. Include Chinese trigger phrases when useful. Do not summarize workflow here.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Slang shaders, shader modules, HLSL-compatible GPU code, graphics pipelines, compute shaders, tessellation, ray tracing, parameter blocks, generics, interfaces, capabilities, cross-compilation, shader optimization, shader review, or C++ engine integration for Slang. Trigger on any mention of Slang, .slang files, slangc, SPIR-V from Slang, Slang modules, [shader("compute")], [shader("vertex")], or requests to write/review/refactor shader code with modern language features. Also trigger for Slang-to-HLSL/GLSL/Metal/CUDA cross-compile questions, or when the user says "shader" alongside "generics", "interfaces", "parameter blocks", "autodiff", or "capabilities".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
日本語の概要は準備中です。原文の説明を表示しています。
Refine an existing skill in place with minimal diffs. Trigger when asked to improve a skill's trigger description/frontmatter, workflow text, metadata, scripts/references/assets; also for requests to iterate, refactor, rename, or fix a skill using usage/session-mining evidence (for example from /tw-seq).
日本語の概要は準備中です。原文の説明を表示しています。
Durable categorized record-keeping for any predicate-enabled walk. Trigger when: - Classifying a step's output for recording (decision, finding, debt, feedback). - Promoting a scratch artifact to the ledger, to repo/docs, or to a category home (.ledger/tech-debt/, .ledger/process-feedback/). - Auditing whether a draft is structurally ready for its destination. - Running a zero-context sensibility read before committing to promotion. - Recording a known limitation as a tech-debt entry (not prose in the log). - Recording a friction, miss, improvement, or process amendment. - Prompt contains: /record, record-keeping, promote, ledger note, zettelkasten, scratch-to-ledger, zero-context read, over-strip, classification trigger, tech-debt, process-feedback, amendment.
日本語の概要は準備中です。原文の説明を表示しています。
The map of nuxt-crouton's GitHub workflows and the deploy-pipeline anatomy — what each workflow gates, how a merge reaches Cloudflare, which secrets/tokens exist where, and how the agent-pipeline workflows chain. Use when a CI check fails and you need to know what it is, when asked "which workflow deploys X / why did staging update / what does this check gate / where is that secret / why didn't my label trigger anything", when wiring a new app into CI, or when debugging a deploy that never fired. Trigger phrases: "what runs on merge to main", "map of the workflows", "WORKER_SECRETS_JSON", "why is the daily sweep not running", "deploy-apps vs deploy-app", "which token does this workflow use".
日本語の概要は準備中です。原文の説明を表示しています。
Activates a structured decorator framework that modifies how Claude reasons, responds, and formats output. Trigger this skill whenever a prompt contains one or more markers prefixed with +++, such as +++Reasoning, +++StepByStep, +++Tone(style=formal), or any other +++ marker, regardless of what follows in the prompt. Also trigger when the user asks to activate, list, or clear decorators, references the prompt decorator framework, or uses phrases like "use decorator", "apply +++", or "what decorators are available". This skill must be active for any +++ marker to take effect.
日本語の概要は準備中です。原文の説明を表示しています。
Solves complex, open-ended problems using an evolutionary search mechanism inspired by genetic algorithms. Generates a diverse population of candidate answers, scores them against a rubric, then iteratively applies selection, crossover, and mutation to breed progressively better solutions. Use this skill whenever the user wants to explore a solution space deeply, asks for the "best" answer to a subjective or multi-dimensional problem, wants to evaluate competing approaches and distill the strongest, or uses any of these triggers: "evolutionary search", "genetic algorithm", "evolve an answer", "breed solutions", "population-based search", or phrases like "give me multiple approaches and refine the best one". Also trigger when the problem is complex, open-ended, or has no obvious single correct answer and the user wants a high-quality, well-explored result, not just a quick response.
日本語の概要は準備中です。原文の説明を表示しています。
スキルを作成・更新・プロンプト改善するためのメタスキル。 **最初のアクションは必ず AskUserQuestion**（インタビュー深度確認）。 **collaborative**モードでユーザーと対話しながら共創し、抽象的なアイデアから具体的な実装まで柔軟に対応する。 **orchestrate**モードでタスクの実行エンジン（Claude Code / Codex / 連携）を選択。 Anchors（主要3件・全7件は references/anchors.md 参照）: • Continuous Delivery (Jez Humble) / 適用: 自動化パイプライン / 目的: 決定論的実行 • The Lean Startup (Eric Ries) / 適用: Build-Measure-Learn / 目的: 反復改善 • Domain-Driven Design (Eric Evans) / 適用: 戦略的設計・ユビキタス言語・Bounded Context / 目的: ドメイン構造の明確化 Trigger: 新規スキルの作成、既存スキルの更新、プロンプト改善を行う場合に使用。 スキル作成, スキル更新, プロンプト改善, skill creation, skill update, improve prompt, Codexに任せて, assign codex, 実行モード選択, IPC Bridge統一, safeInvoke/safeOn, Preload API標準化, contextBridge, Electron IPC pattern
7人の専門家による多角的レビューを経て、法的リスクを最小化した取引基本契約書を対話形式で自動生成するスキル。 AI事業・IT事業・コンサルティング等に対応し、フリーランス新法（2024）・民法改正（2020）に準拠。 Anchors: - 契約書の作成実務と書式（牧野和夫）/ 適用: 契約構成・条項設計 / 目的: 実務レベルの契約書構造 - AIと著作権に関する考え方について（文化庁 令和6年）/ 適用: AI著作権条項 / 目的: AI利用免責設計 - フリーランスとして安心して働ける環境を整備するためのガイドライン（公取委・厚労省）/ 適用: 支払条件・解約予告 / 目的: 法令準拠 Trigger: 取引基本契約書, 業務委託契約, 契約書作成, フリーランス契約, AI事業契約, 請負契約, 準委任契約, 著作権譲渡契約
Strategy cascade based on Roger Martin and A.G. Lafley's Playing to Win framework. Five interconnected choices that define a real strategy — not a vision statement, not a list of priorities, not a strategic plan that's really just a budget with adjectives. Runs in three modes — Diagnostic for building or rebuilding the full cascade, Review for pressure-testing an existing one, and Alert Triggers for defining the tripwires that tell you the cascade is breaking. Updates company-context.md after every run. Triggers on questions about strategy, strategic choices, winning aspiration, where to play, how to win, competitive strategy, or when someone says "we need a strategy" and means it. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。
Culture assessment and monitoring with three modes — Diagnostic for a deep session surfacing the gap between declared culture and actual culture, Review for periodic check-ins on whether behavior is shifting, and Alert Triggers for setting tripwires around culture-strategy misalignment, regression, and integration risk. Not a culture change programme — a mirror. Updates company-context.md after every run. Triggers on questions about culture, values, team dynamics, how decisions really get made, why change efforts stall, merger integration, or whether the organisation can actually execute its strategy. Based on practice by Eterdis (eterdis.com).
日本語の概要は準備中です。原文の説明を表示しています。