3,386 件 ・ 関連度順
概要と使いどころ
Ensure every factual claim in a response is backed by verifiable evidence from the codebase, documentation, or external sources. Use when preparing technical documentation, code reviews, or any output where accuracy is non-negotiable.
日本語の概要は準備中です。原文の説明を表示しています。
Normalize and screen scattered foreign-trade leads into a conservative, structured lead pool that can flow into customer-intel research. Use when an operator has company names, websites, emails, or contact clues from search results and needs a standardized output with missing-field warnings, review flags, next-step suggestions, and customer-intel-ready JSON.
日本語の概要は準備中です。原文の説明を表示しています。
Find the first batch of foreign-trade prospect companies from public web, LinkedIn, and user-authorized data sources such as customs exports, trade show lists, association directories, CRM/Excel files, or historical customer data, then output a conservative, structured candidate list ready for lead screening.
日本語の概要は準備中です。原文の説明を表示しています。
Discover prospect companies from a structured OpenClaw search brief, including public search and user-authorized data sources, then output a conservative candidate list ready for lead screening.
日本語の概要は準備中です。原文の説明を表示しています。
Show stored output for a Claude Companion job.
日本語の概要は準備中です。原文の説明を表示しています。
Verify like Fable 5 — obsessive, systematic, evidence-based quality assurance woven into your reasoning. Use this skill when you have just written or modified code, need to confirm something works, are running tests, or need to validate output against requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.
日本語の概要は準備中です。原文の説明を表示しています。
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".
日本語の概要は準備中です。原文の説明を表示しています。
Post findings from the most recent review output as inline GitHub PR comments and record them in today's daily note. Use when invoked as `$pr-post-review-findings` or when the user asks to post review findings to the current PR.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, debugging, or configuring an omp hook or extension — blocking or rewriting tool calls, redacting tool output, reshaping LLM context, registering tools/commands, or wiring modules through config.yml. Covers ExtensionAPI (current) vs HookAPI (legacy), the event catalog, discovery and load order, and disable controls. Not for Claude Code hooks (~/.claude/settings.json) or the shared harness safety guard (~/.agents/harness/hooks/).
日本語の概要は準備中です。原文の説明を表示しています。
Codex workflow tips from Boris Cherny (creator of Codex) and the Codex team. Use when: setting up Codex, optimizing workflows, running parallel sessions, configuring AGENTS.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Code workflow tips from Boris Cherny (creator of Claude Code) and the Claude Code team. Use when: setting up Claude Code, optimizing workflows, running parallel sessions, configuring CLAUDE.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.
日本語の概要は準備中です。原文の説明を表示しています。
Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.
日本語の概要は準備中です。原文の説明を表示しています。
Quality gate for agent-flow. Runs the repo's test, typecheck and lint commands in the issue worktree, re-runs failures once, reports raw output as JSON. Never modifies code. Use when launched with AGENT_FLOW_ROLE=qa after a review is approved.
日本語の概要は準備中です。原文の説明を表示しています。
話したい素材を整理し章・項の構成に落とし込みoutline.mdに保存する。完了後に自動でoutline-refineを起動する。
アウトプット（LT・技術記事・書籍）のアウトラインを作成するワークフローを管理する。プロジェクト状態を自動判定し適切なフェーズから開始する。「アウトライン」「骨格」「構成を作りたい」で起動。
アウトラインのゴール（受け手に期待する行動・変化）を対話形式で設定しgoal.mdに保存する。完了後に自動でoutline-draftを起動する。
アウトプットのネタ帳を管理する。ネタの追加・一覧・詳細表示・ブラッシュアップを行う。まだアウトラインを作るほど固まっていないアイデアの記録と育成に使う。「ネタ」「ネタ帳」「アイデア」「思いついた」「idea」で起動。
4つの観点（整合性・流れ・ロジック・独自価値）でアウトラインを並列レビューし深掘り・言語化する。何度でも繰り返し実行可能。
5つの観点（ゴール整合性・読みやすさ・独自価値・構成・LLM表現）で下書きを並列レビューし推敲する。何度でも繰り返し実行可能。「推敲」「レビュー」「write-review」で起動。