2,676 件 ・ 関連度順
概要と使いどころ
Purple team automation skill that links offensive emulation (Atomic Red Team, Caldera, Stratus Red Team, Leonidas) with detection validation, telemetry-gap analysis, and continuous control testing. Use to design adversary emulation plans tied to MITRE ATT&CK, execute safe tests in lab or controlled environments, and produce evidence-backed detection coverage reports.
日本語の概要は準備中です。原文の説明を表示しています。
Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.
日本語の概要は準備中です。原文の説明を表示しています。
Full-pipeline orchestrator. Runs all 7 roles (BA → TechLead → PM → BE Dev → FE Dev → Tester → QA/QC) in sequence by loading and following each per-role skill. Uses pre_write_validator.py hook enforcement and each role's self-validation. Use per-agent commands ($team-ba, $team-techlead, etc.) for manual control.
日本語の概要は準備中です。原文の説明を表示しています。
Full-pipeline orchestrator. Runs all 7 agents (BA → TechLead → PM → BE Dev → FE Dev → Tester → QA/QC) in sequence by invoking each per-agent skill via the Skill tool. All writes go through the pre_write_validator.py hook for hard enforcement. Use per-agent commands (/team-ba, /team-techlead, etc.) for manual control.
日本語の概要は準備中です。原文の説明を表示しています。
Configuring Salesforce opportunity management: sales stages, sales processes, opportunity record types, Path configuration, opportunity teams, opportunity splits, and forecasting categories. Use when setting up or restructuring the opportunity lifecycle for Sales Cloud. NOT for forecast types, rollup methods, quotas or manager adjustments — use admin/collaborative-forecasts. NOT for agreeing what the stages and exit criteria should be before any build — use admin/sales-process-mapping. NOT for CPQ pricing or product configuration. Keywords: BusinessProcess, sales process, OpportunityStage, ForecastCategoryName, PathAssistant, OpportunitySplit, OpportunitySplitType, OpportunityTeamMember, Opportunity.settings, enableOpportunityTeam, IsClosed, IsWon, IsPrivate.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and configure the Havoc C2 framework with teamserver, HTTPS listeners, redirectors, and Demon agents for authorized red team operations.
日本語の概要は準備中です。原文の説明を表示しています。
Team standup board (Busabase App-in-Skill) for team leads. Use when the user invokes $kelly-standup or /kelly-standup, or asks for standup, daily standup, 晨会, daily check-in, team status board, 团队日报, blockers, who's working on what, team digest, check-in streaks, missing check-in reminders, or collecting async updates from Slack/WeCom/Discord/WhatsApp/docs into one board.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and configure the Havoc C2 framework with teamserver, HTTPS listeners, redirectors, and Demon agents for authorized red team operations.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about team driving — two-driver OTR operations, how teams maximize miles, HOS rules with sleeper berth swap, pay structures, equipment requirements (sleeper berth specs), team retention, and common challenges. Reference 49 CFR 395.1(g).
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end Coval adversarial / red-team testing workflow. Builds one adversarial test set (12 core attack vectors plus legitimate controls, each with an expected-behavior checklist), creates a persistent "Adversarial User" persona and a Composite Evaluation metric that scores each scenario against its own expected behaviors, launches a multi-iteration run against the agent (voice or chat), polls for completion, builds a per-scenario pass/fail scorecard, and creates a saved report grouped by Test Case. Use when a user wants to follow the Adversarial & Red-Team Testing cookbook (https://docs.coval.dev/guides/adversarial-red-team-testing) without doing each step by hand. Triggers: "adversarial test set", "red team my agent", "jailbreak / prompt-injection testing", "test my agent against bad actors".
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy and configure the Havoc C2 framework with teamserver, HTTPS listeners, redirectors, and Demon agents for authorized red team operations.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities.
日本語の概要は準備中です。原文の説明を表示しています。
Client-facing red-team deliverable format — codifies the Subject / Observations / Description / Impact / Recommendation / PoC structure used for external red-team engagements (not bug-bounty platform reports). Different audience, different tone, different cadence. Built from an authorized engagement deliverable where 14 findings were packaged into a 52KB MD + 2.2MB DOCX with 16 embedded screenshots. Use when the engagement is 'external red team for an enterprise client' (not H1/Bugcrowd/Intigriti), when generating the final report, when the client has specified a custom report format, or when packaging findings into DOCX/PDF.
日本語の概要は準備中です。原文の説明を表示しています。
Floxで開発ツールやデータベースの構成・バージョンを設定ファイルにまとめ、macOSとLinuxで再現できる開発環境を作り、チームで共有するスキル。
売上・返金・重複課金を請求データから整理し、チーム課金や利用権限の実装まで確認するスキル。料金表示と実際の動作を照合し、運営の判断材料をまとめます。
Review a connected Paperclip team's agents, tasks, blockers and pending approvals when the user asks for a team summary or what needs attention.
日本語の概要は準備中です。原文の説明を表示しています。
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
日本語の概要は準備中です。原文の説明を表示しています。
Pauses, resumes, or completes an AI team, or marks a run complete, while keeping its evidence. Use when the user asks to pause, stop, resume, wrap up, or close a team or run. Changes coordination state only and deletes nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Plans and creates an AI team for a goal, with roles, a run that carries a unit budget, and bounded tasks. Use when the user asks to start, set up or staff a team, or to split a larger goal across roles. Records coordination state only; nothing is executed.
日本語の概要は準備中です。原文の説明を表示しています。
Capture surprises, workarounds, and rough edges hit while *consuming* the public surface of Prisma 8, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour while using one of these three products from the outside (extension authoring, example apps, integration tests, customer reproductions, internal demos, manual repros). Does NOT fire on bugs in code the operator's own team maintains — those are normal product-backlog bugs. In product-team repos (e.g. `prisma-8-ws`), surfaces the gotcha and offers the operator three paths (capture-as-gotcha, file a normal bug, or note-and-move-on). Outside product-team repos (pet projects, hackathon entries, customer codebases), silent-captures into the project's gotchas log AND a Triage-state Linear ticket in the matching gotchas project — no operator escalation. Do not skip the recording step.
日本語の概要は準備中です。原文の説明を表示しています。
Headcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
日本語の概要は準備中です。原文の説明を表示しています。