2,740 件 ・ 関連度順
概要と使いどころ
Spearphishing simulation is a targeted social engineering attack vector used by red teams to gain initial access. Unlike broad phishing campaigns, spearphishing uses OSINT-derived intelligence to craf
日本語の概要は準備中です。原文の説明を表示しています。
Build and configure a resilient command-and-control infrastructure using BishopFox's Sliver C2 framework with redirectors, HTTPS listeners, and multi-operator support for authorized red team engagements.
日本語の概要は準備中です。原文の説明を表示しています。
Focused Signals scout for finding observability gaps in PostHog itself — significant event volumes the team isn't tracking, custom events with no insight or dashboard coverage, insights pointing at events that have stopped firing, dashboards missing related context, critical events with no alerts. Watches the event-stream-vs-saved- inventory delta as the team's product evolves and emits findings recommending new insights, dashboard additions, or alerts when gaps clear the confidence bar. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Discover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage "shared skills", "team skills", or references the "skills store" / "skill store".
日本語の概要は準備中です。原文の説明を表示しています。
Help teams prepare materials for an SCF referral. Use when a team wants to approach a referrer (SCF Pilot, SDF staff, alumni who completed deliverables, ambassador, or ecosystem partner) with a strong package that makes it easy for the referrer to evaluate and endorse them. Covers the referral form fields, what referrers assess, and how to present your project for referral.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a strong SCF Interest Form submission. Use when a team needs help writing the Interest Form that determines whether they get invited to submit a full Build Award application. Covers project positioning, Stellar integration framing, team presentation, and the concise format the Interest Form requires.
日本語の概要は準備中です。原文の説明を表示しています。
Help funded SCF teams write tranche submission reports. Use when a team has completed a tranche milestone and needs to document their deliverables for review to unlock the next payment. Covers deliverable documentation, completion evidence, demo preparation, and the specific format tranche reviewers expect.
日本語の概要は準備中です。原文の説明を表示しています。
Draft Stellar Community Fund Build Award applications interactively. Use when helping teams write their SCF submission — walks through project description, Stellar integration rationale, technical architecture, team section, deliverables, budget, and traction evidence. Produces a complete draft aligned with what funded projects look like.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Claude Code (code.claude.com) の拡張機能リファレンス。 Agent Skills (SKILL.md), slash commands, output styles, subagents, agent teams, agent view, workflows, routines, scheduled tasks, hooks (PreToolUse / PostToolUse), plugins, plugin marketplace, MCP 設定 (.mcp.json / claude mcp add), managed MCP, channels (--channels / claude/channel push events, webhook / telegram / discord / imessage), tools-reference, advisor, ultrareview。
プロジェクトのワークフローを管理するPM（プロジェクトマネージャー）。「プロジェクトを開始」「新規プロジェクト」「進捗確認」「次のタスク」「続きを進めて」「承認」「○○が完了」「Agent Teamで〜」などの指示で呼び出す。プロジェクトの状態（ファイルの有無・内容）に応じて適切な処理を自動で選択する。
Plan purple-team / adversary-simulation exercises against systems you are contracted to test. High-level objectives and detection gaps only. No live attack procedures or payloads.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
日本語の概要は準備中です。原文の説明を表示しています。
Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".
日本語の概要は準備中です。原文の説明を表示しています。
Automate Connecteam tasks via Rube MCP (Composio). Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Choose, compare, and decompose work into the right coordination topology: dag, workflow, manager-driven team, swarm, blackboard, team-builder, or recurring loop. Use when the coordination shape is unclear, when you need topology-native breakdown instructions instead of a generic DAG, or when planning topology and runtime topology may differ. NOT for actual execution, node-level skill matching, or framework/tool installation.
日本語の概要は準備中です。原文の説明を表示しています。
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.).
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user wants to "stress-test a design", "challenge an idea", "red team a proposal", "get critical feedback on a design", "validate a design", "adversarial architecture review", "risk assessment", "設計を検証して", "反論をもらいたい", "設計を批判的にレビュー", "デビルズアドボケート", "ストレステスト", "弱点を指摘して", "穴を見つけて", "この設計で良いか", "リスク評価", "設計のアーキテクチャレビュー", or mentions structured adversarial review of a proposal or design. NOTE: Use this for validating PROPOSALS and DESIGNS through adversarial debate, NOT for generic code review, PR review, or normal review requests (use /codex:review or /codex:adversarial-review for those). Also NOT for investigating unknown bugs (use /agent-dialectics:strong-inference for that).
クロスレビュー。有識者エージェント3つの並行レビュー + Codex レビュー + Codex 敵対的レビュー（red team）で変更を多視点レビューし、結果を統合報告する（コードは変更しない）。「クロスレビューして」「cross-reviewして」「複数視点でレビューして」で発動。Codex 単体で足りる軽いレビューは codex-review、レビュー結果の修正・実装まで任せる場合は forge を使う。
タスク着手時に codex にリードしてもらうワークフロー。codex に設計/方針を主導（リード）させ、その方針に沿って Claude が実装し、実装後は codex で設計適合・実装正当性・敵対的（red team）の 3 観点でレビューする。余っている codex トークンを積極的に消費したい時に使う。「codexにリードしてもらって」「設計から codex に任せて」「タスクを codex 主導で」「codex-lead」「/codex-lead」で発火。
codex exec review を基本に、必要なら codex exec を使ってコード変更のレビューを依頼し、指摘事項を報告する。通常 / 厳しめ (--strict) / 敵対的 (--adversarial、実装を壊しにいく red team) の 3 モードを持つ。「codexでレビューして」「codex-review」「/codex-review」「敵対的にレビューして」で発火。Codex 単体での単独レビュー用途。複数エージェント並行レビューは cross-review、差分ではなくコードベース全体の監査は audit を使う。
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Architecture Decision Records (ADR) — a lightweight method for capturing important architectural decisions with context, trade-offs, and rationale. Based on Michael Nygard's ADR pattern and Google/Meta/ByteDance's design documentation culture. USE WHEN: deciding between technology choices, designing new architecture, changing existing architecture, documenting why a decision was made, onboarding new team members, or preserving design context for future maintainers. Triggered by terms like "tech choice", "architecture decision", "why did we choose", "design rationale", "ADR", or "architectural decision record".
日本語の概要は準備中です。原文の説明を表示しています。
MediaClaw is an AI video content factory for teams that need brand video production and repurposing at scale. It turns one source video into localized clips, ad creatives, captioned shorts, voiceover variants, and platform-ready exports for TikTok, Reels, Shorts, Douyin, and Xiaohongshu. AI 视频工厂、品牌视频替换、批量视频生产、短视频自动化。
日本語の概要は準備中です。原文の説明を表示しています。