- Retirement income & withdrawal strategy
- Tax: Roth/RRSP, loss harvesting, rule changes
- Estate, insurance & cross-border planning
- Advisor tools: meeting prep, compliance pre-screen
21,500+ skills & agents. Every one governed.
5,814 pre-built agents and 15,654 library skills across 24 industries and 12 roles per industry — installable from the catalog, connected to your systems, and run through the same fail-closed gate chain as everything else on Cortex.
21,511 governed library items · counted live from the catalog, not a marketing number
Start from a curated collection.
Hand-built suites for the jobs enterprises automate first — every collection ships governed, with policies and audit built in.
- Service, Sales & Customer Success
- IT Service Desk, HR & Finance Ops
- Legal Intake, Procurement & Field Ops
- Risk & Compliance
- Inbox triage & email drafting
- Meeting prep, notes & follow-up
- Smart scheduling & daily brief
- Executive assistant orchestration
- Smart claims, actuarial & AML
- Audit, GRC & ESG reporting
- ITAM / ITSM & security operations
- Data & analytics workbenches
Find the skill your team needs.
Search 21,500+ governed skills and agents, or filter by industry and type — every result installs from the catalog and runs through the same gates.
648 results · Customer Support · skills
Check supplied context against policy — Technical Support, Customer Support
Check supplied context against policy for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface potential policy issues — Technical Support, Customer Support
Surface potential policy issues for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend review items — Technical Support, Customer Support
Recommend review items for Technical Support teams in Customer Support, delivered by the Compliance Checker pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied risk context — Technical Support, Customer Support
Assess supplied risk context for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Explain assessment drivers — Technical Support, Customer Support
Explain assessment drivers for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend human review — Technical Support, Customer Support
Recommend human review for Technical Support teams in Customer Support, delivered by the Risk Assessment pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied record data — Technical Support, Customer Support
Query supplied record data for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Technical Support, Customer Support
Summarize potential discrepancies for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Technical Support, Customer Support
Prepare a reconciliation brief for Technical Support teams in Customer Support, delivered by the Reconciliation Brief pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Technical Support, Customer Support
Assess a supplied exception for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Technical Support, Customer Support
Summarize the assessment for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Technical Support, Customer Support
Recommend follow-up review for Technical Support teams in Customer Support, delivered by the Exception Review pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run an on-demand read query — Technical Support, Customer Support
Run an on-demand read query for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize query results — Technical Support, Customer Support
Summarize query results for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Highlight supplied exceptions — Technical Support, Customer Support
Highlight supplied exceptions for Technical Support teams in Customer Support, delivered by the On-demand Reporting & Insights pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied context — Technical Support, Customer Support
Assess supplied context for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a recommended response — Technical Support, Customer Support
Draft a recommended response for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare rationale for review — Technical Support, Customer Support
Prepare rationale for review for Technical Support teams in Customer Support, delivered by the Decision Support pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied work — Technical Support, Customer Support
Summarize supplied work for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess priority and risk — Technical Support, Customer Support
Assess priority and risk for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a routing decision — Technical Support, Customer Support
Recommend a routing decision for Technical Support teams in Customer Support, delivered by the Routing Advisor pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied historical data — Technical Support, Customer Support
Query supplied historical data for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize observed trends — Technical Support, Customer Support
Summarize observed trends for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare questions for forecast review — Technical Support, Customer Support
Prepare questions for forecast review for Technical Support teams in Customer Support, delivered by the Trend Briefing pattern from supplied context. Zendesk and Intercom are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Install is the easy part. Governance comes with it.
Library agents aren't scripts — they're governed identities. Installing one registers it with an owner, a budget, allowed models and actions, and a place in the audit ledger.
Choose from the catalog
Filter by your industry and role; every item lists the systems it connects to and the skills it invokes.
Wire it to your stack
Connectors, MCP servers, and OpenAPI imports — scoped by allowlists and DLP at the gateway.
Every run through the gates
Identity, budget, guardrails, policy, oversight — then a signed receipt in the Trust Ledger. On every plan.
Don't see the skill you need?
The visual skill builder ships new skills without code — or tell us what's missing and we'll point you at the closest governed pattern.