ウェルス＆リタイアメント · 121 スキル
- 退職後の収入と取り崩し戦略
- 税務: Roth/RRSP、損出し、ルール変更
- 相続・保険・クロスボーダーのプランニング
- アドバイザー向けツール: 面談準備、コンプライアンス事前チェック
Agent Library
21,500+ のスキルとエージェント。すべてガバナンス付き。
24 の業種と業種あたり 12 のロールにわたる、5,814 の既製エージェントと 15,654 のライブラリスキル。カタログからインストールし、お客様のシステムに接続し、Cortex 上の他のすべてと同じフェイルクローズのゲートチェーンを通して実行されます。
カタログマトリクス全体で 21,511 のライブラリテンプレート
Agent Studio
スキル
KB を検索チケット作成メール送信 追加
公開済みv4 · 信頼性 96
注文 #4471 はどこですか？
発送済みです。木曜日に到着予定です。ツール: KB を検索 · $0.004
studio ▸ 構築 → 公開 → チャットでテスト
コレクション
厳選されたコレクションから始める。
企業が最初に自動化する業務のために手作りしたスイート。すべてのコレクションはガバナンス付きで提供され、ポリシーと監査が最初から組み込まれています。
Enterprise Role Packs · 11 職種
- サービス、セールス、カスタマーサクセス
- IT サービスデスク、人事、財務オペレーション
- 法務受付、調達、現場オペレーション
- リスクとコンプライアンス
Productivity Pack · 9 エージェント
- 受信トレイのトリアージとメール下書き
- 会議の準備、議事メモ、フォローアップ
- スマートな日程調整とデイリーブリーフ
- エグゼクティブアシスタントのオーケストレーション
Gene コレクション · 630 エージェント
- スマートクレーム、アクチュアリー、AML
- 監査、GRC、ESG レポーティング
- ITAM / ITSM とセキュリティオペレーション
- データ・アナリティクスのワークベンチ
ライブラリを見る
チームに必要なスキルを見つける。
21,500+ のガバナンス済みスキルとエージェントを検索、または業種と種別で絞り込めます。どの結果もカタログからインストールでき、同じゲートを通過します。
すべての業種InsuranceBanking & Capital MarketsHealthcare & Hospital AdminLegal ServicesIT Service ManagementHuman ResourcesFinance & AccountingSalesMarketingCustomer SupportSupply Chain & LogisticsManufacturingRetail & E-commerceReal EstateEducationGovernment & Public SectorEnergy & UtilitiesTelecommunicationsPharmaceutical & Life SciencesHospitality & TravelConstruction & EngineeringAutomotiveCybersecurityProfessional Services
864 件の結果 · Cybersecurity
Search approved knowledge — Security Operations Lead, Cybersecurity
Search approved knowledge for Security Operations Lead teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a grounded response — Security Operations Lead, Cybersecurity
Draft a grounded response for Security Operations Lead teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review-ready answer — Security Operations Lead, Cybersecurity
Prepare a review-ready answer for Security Operations Lead teams in Cybersecurity, delivered by the Q&A Assistant pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft from supplied context — Security Operations Lead, Cybersecurity
Draft from supplied context for Security Operations Lead teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Follow configured behavior guidance — Security Operations Lead, Cybersecurity
Follow configured behavior guidance for Security Operations Lead teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare copy for revision — Security Operations Lead, Cybersecurity
Prepare copy for revision for Security Operations Lead teams in Cybersecurity, delivered by the Drafting & Generation pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize a supplied record — Security Operations Lead, Cybersecurity
Summarize a supplied record for Security Operations Lead teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess possible risk — Security Operations Lead, Cybersecurity
Assess possible risk for Security Operations Lead teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Flag items for human review — Security Operations Lead, Cybersecurity
Flag items for human review for Security Operations Lead teams in Cybersecurity, delivered by the Record Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run a parameterized read query — Security Operations Lead, Cybersecurity
Run a parameterized read query for Security Operations Lead teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize returned records — Security Operations Lead, Cybersecurity
Summarize returned records for Security Operations Lead teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a result-set overview — Security Operations Lead, Cybersecurity
Prepare a result-set overview for Security Operations Lead teams in Cybersecurity, delivered by the Data Query & Summary pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Check supplied context against policy — Security Operations Lead, Cybersecurity
Check supplied context against policy for Security Operations Lead teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Security Operations Lead, Cybersecurity
Surface potential policy issues for Security Operations Lead teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Security Operations Lead, Cybersecurity
Recommend review items for Security Operations Lead teams in Cybersecurity, delivered by the Compliance Checker pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Security Operations Lead, Cybersecurity
Assess supplied risk context for Security Operations Lead teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Security Operations Lead, Cybersecurity
Explain assessment drivers for Security Operations Lead teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Security Operations Lead, Cybersecurity
Recommend human review for Security Operations Lead teams in Cybersecurity, delivered by the Risk Assessment pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data — Security Operations Lead, Cybersecurity
Query supplied record data for Security Operations Lead teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Security Operations Lead, Cybersecurity
Summarize potential discrepancies for Security Operations Lead teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Security Operations Lead, Cybersecurity
Prepare a reconciliation brief for Security Operations Lead teams in Cybersecurity, delivered by the Reconciliation Brief pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Security Operations Lead, Cybersecurity
Assess a supplied exception for Security Operations Lead teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Security Operations Lead, Cybersecurity
Summarize the assessment for Security Operations Lead teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Security Operations Lead, Cybersecurity
Recommend follow-up review for Security Operations Lead teams in Cybersecurity, delivered by the Exception Review pattern from supplied context. Splunk and CrowdStrike are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
既定でガバナンス付き
導入は簡単な部分。ガバナンスも一緒に付いてくる。
ライブラリのエージェントはスクリプトではなく、ガバナンス付きのアイデンティティです。インストールすると、オーナー、予算、許可されたモデルとアクション、そして監査台帳上の位置とともに登録されます。
カタログから選ぶ
業種と役割で絞り込み。各項目には、接続先のシステムと呼び出すスキルが明記されています。
自社スタックに接続する
コネクタ、MCP サーバー、OpenAPI インポート——ゲートウェイでの許可リストと DLP によってスコープを限定。
すべての実行はゲートを通る
アイデンティティ、予算、ガードレール、レジストリ、Control Tower、実行、出力ガード——そして Trust Ledger に署名付きレシート。すべてのプランで。
必要なスキルが見つかりませんか。
ビジュアルなスキルビルダーなら、コードなしで新しいスキルを出せます。足りないものをお知らせいただければ、最も近いガバナンス付きパターンをご案内します。