ウェルス＆リタイアメント · 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 件の結果 · Telecommunications
Check supplied context against policy — Customer Retention, Telecommunications
Check supplied context against policy for Customer Retention teams in Telecommunications, delivered by the Compliance Checker pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Customer Retention, Telecommunications
Surface potential policy issues for Customer Retention teams in Telecommunications, delivered by the Compliance Checker pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Customer Retention, Telecommunications
Recommend review items for Customer Retention teams in Telecommunications, delivered by the Compliance Checker pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Customer Retention, Telecommunications
Assess supplied risk context for Customer Retention teams in Telecommunications, delivered by the Risk Assessment pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Customer Retention, Telecommunications
Explain assessment drivers for Customer Retention teams in Telecommunications, delivered by the Risk Assessment pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Customer Retention, Telecommunications
Recommend human review for Customer Retention teams in Telecommunications, delivered by the Risk Assessment pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data — Customer Retention, Telecommunications
Query supplied record data for Customer Retention teams in Telecommunications, delivered by the Reconciliation Brief pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Customer Retention, Telecommunications
Summarize potential discrepancies for Customer Retention teams in Telecommunications, delivered by the Reconciliation Brief pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Customer Retention, Telecommunications
Prepare a reconciliation brief for Customer Retention teams in Telecommunications, delivered by the Reconciliation Brief pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Customer Retention, Telecommunications
Assess a supplied exception for Customer Retention teams in Telecommunications, delivered by the Exception Review pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Customer Retention, Telecommunications
Summarize the assessment for Customer Retention teams in Telecommunications, delivered by the Exception Review pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Customer Retention, Telecommunications
Recommend follow-up review for Customer Retention teams in Telecommunications, delivered by the Exception Review pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run an on-demand read query — Customer Retention, Telecommunications
Run an on-demand read query for Customer Retention teams in Telecommunications, delivered by the On-demand Reporting & Insights pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize query results — Customer Retention, Telecommunications
Summarize query results for Customer Retention teams in Telecommunications, delivered by the On-demand Reporting & Insights pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Highlight supplied exceptions — Customer Retention, Telecommunications
Highlight supplied exceptions for Customer Retention teams in Telecommunications, delivered by the On-demand Reporting & Insights pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied context — Customer Retention, Telecommunications
Assess supplied context for Customer Retention teams in Telecommunications, delivered by the Decision Support pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a recommended response — Customer Retention, Telecommunications
Draft a recommended response for Customer Retention teams in Telecommunications, delivered by the Decision Support pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare rationale for review — Customer Retention, Telecommunications
Prepare rationale for review for Customer Retention teams in Telecommunications, delivered by the Decision Support pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied work — Customer Retention, Telecommunications
Summarize supplied work for Customer Retention teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess priority and risk — Customer Retention, Telecommunications
Assess priority and risk for Customer Retention teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a routing decision — Customer Retention, Telecommunications
Recommend a routing decision for Customer Retention teams in Telecommunications, delivered by the Routing Advisor pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied historical data — Customer Retention, Telecommunications
Query supplied historical data for Customer Retention teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize observed trends — Customer Retention, Telecommunications
Summarize observed trends for Customer Retention teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare questions for forecast review — Customer Retention, Telecommunications
Prepare questions for forecast review for Customer Retention teams in Telecommunications, delivered by the Trend Briefing pattern from supplied context. Amdocs and Netcracker 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 に署名付きレシート。すべてのプランで。
必要なスキルが見つかりませんか。
ビジュアルなスキルビルダーなら、コードなしで新しいスキルを出せます。足りないものをお知らせいただければ、最も近いガバナンス付きパターンをご案内します。