- 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.
864 results · Telecommunications
Summarize supplied work — Billing Analyst, Telecommunications
Summarize supplied work for Billing Analyst 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 — Billing Analyst, Telecommunications
Assess priority and risk for Billing Analyst 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 — Billing Analyst, Telecommunications
Recommend a routing decision for Billing Analyst 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 — Billing Analyst, Telecommunications
Query supplied historical data for Billing Analyst 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 — Billing Analyst, Telecommunications
Summarize observed trends for Billing Analyst 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 — Billing Analyst, Telecommunications
Prepare questions for forecast review for Billing Analyst 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.
Search approved onboarding knowledge — Billing Analyst, Telecommunications
Search approved onboarding knowledge for Billing Analyst teams in Telecommunications, delivered by the Onboarding Guide 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 step-by-step guidance — Billing Analyst, Telecommunications
Draft step-by-step guidance for Billing Analyst teams in Telecommunications, delivered by the Onboarding Guide 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 review checklist — Billing Analyst, Telecommunications
Prepare a review checklist for Billing Analyst teams in Telecommunications, delivered by the Onboarding Guide 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 feedback — Billing Analyst, Telecommunications
Summarize supplied feedback for Billing Analyst teams in Telecommunications, delivered by the Feedback Summary 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 recurring points — Billing Analyst, Telecommunications
Surface recurring points for Billing Analyst teams in Telecommunications, delivered by the Feedback Summary 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 follow-up questions — Billing Analyst, Telecommunications
Prepare follow-up questions for Billing Analyst teams in Telecommunications, delivered by the Feedback Summary 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.
Search approved knowledge — Billing Analyst, Telecommunications
Search approved knowledge for Billing Analyst teams in Telecommunications, delivered by the Research & Discovery 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 findings — Billing Analyst, Telecommunications
Summarize supplied findings for Billing Analyst teams in Telecommunications, delivered by the Research & Discovery 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 research brief — Billing Analyst, Telecommunications
Draft a research brief for Billing Analyst teams in Telecommunications, delivered by the Research & Discovery 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.
Search approved process knowledge — Billing Analyst, Telecommunications
Search approved process knowledge for Billing Analyst teams in Telecommunications, delivered by the Process Guidance 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 process context — Billing Analyst, Telecommunications
Summarize supplied process context for Billing Analyst teams in Telecommunications, delivered by the Process Guidance 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 next-step guidance — Billing Analyst, Telecommunications
Draft next-step guidance for Billing Analyst teams in Telecommunications, delivered by the Process Guidance 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 request context — Field Technician Dispatch, Telecommunications
Summarize supplied request context for Field Technician Dispatch teams in Telecommunications, delivered by the Intake Review & Triage 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 urgency and risk — Field Technician Dispatch, Telecommunications
Assess urgency and risk for Field Technician Dispatch teams in Telecommunications, delivered by the Intake Review & Triage 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 review priority — Field Technician Dispatch, Telecommunications
Recommend a review priority for Field Technician Dispatch teams in Telecommunications, delivered by the Intake Review & Triage 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.
Condense supplied content — Field Technician Dispatch, Telecommunications
Condense supplied content for Field Technician Dispatch teams in Telecommunications, delivered by the Document Summarizer 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 key points — Field Technician Dispatch, Telecommunications
Surface key points for Field Technician Dispatch teams in Telecommunications, delivered by the Document Summarizer 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.
Produce a concise brief — Field Technician Dispatch, Telecommunications
Produce a concise brief for Field Technician Dispatch teams in Telecommunications, delivered by the Document Summarizer 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.
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.