- 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 · Healthcare & Hospital Admin
Query supplied record data — Patient Access, Healthcare & Hospital Admin
Query supplied record data for Patient Access teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize potential discrepancies — Patient Access, Healthcare & Hospital Admin
Summarize potential discrepancies for Patient Access teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a reconciliation brief — Patient Access, Healthcare & Hospital Admin
Prepare a reconciliation brief for Patient Access teams in Healthcare & Hospital Admin, delivered by the Reconciliation Brief pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess a supplied exception — Patient Access, Healthcare & Hospital Admin
Assess a supplied exception for Patient Access teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize the assessment — Patient Access, Healthcare & Hospital Admin
Summarize the assessment for Patient Access teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend follow-up review — Patient Access, Healthcare & Hospital Admin
Recommend follow-up review for Patient Access teams in Healthcare & Hospital Admin, delivered by the Exception Review pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Run an on-demand read query — Patient Access, Healthcare & Hospital Admin
Run an on-demand read query for Patient Access teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize query results — Patient Access, Healthcare & Hospital Admin
Summarize query results for Patient Access teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Highlight supplied exceptions — Patient Access, Healthcare & Hospital Admin
Highlight supplied exceptions for Patient Access teams in Healthcare & Hospital Admin, delivered by the On-demand Reporting & Insights pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess supplied context — Patient Access, Healthcare & Hospital Admin
Assess supplied context for Patient Access teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft a recommended response — Patient Access, Healthcare & Hospital Admin
Draft a recommended response for Patient Access teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare rationale for review — Patient Access, Healthcare & Hospital Admin
Prepare rationale for review for Patient Access teams in Healthcare & Hospital Admin, delivered by the Decision Support pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied work — Patient Access, Healthcare & Hospital Admin
Summarize supplied work for Patient Access teams in Healthcare & Hospital Admin, delivered by the Routing Advisor pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Assess priority and risk — Patient Access, Healthcare & Hospital Admin
Assess priority and risk for Patient Access teams in Healthcare & Hospital Admin, delivered by the Routing Advisor pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Recommend a routing decision — Patient Access, Healthcare & Hospital Admin
Recommend a routing decision for Patient Access teams in Healthcare & Hospital Admin, delivered by the Routing Advisor pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Query supplied historical data — Patient Access, Healthcare & Hospital Admin
Query supplied historical data for Patient Access teams in Healthcare & Hospital Admin, delivered by the Trend Briefing pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize observed trends — Patient Access, Healthcare & Hospital Admin
Summarize observed trends for Patient Access teams in Healthcare & Hospital Admin, delivered by the Trend Briefing pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare questions for forecast review — Patient Access, Healthcare & Hospital Admin
Prepare questions for forecast review for Patient Access teams in Healthcare & Hospital Admin, delivered by the Trend Briefing pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Search approved onboarding knowledge — Patient Access, Healthcare & Hospital Admin
Search approved onboarding knowledge for Patient Access teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Draft step-by-step guidance — Patient Access, Healthcare & Hospital Admin
Draft step-by-step guidance for Patient Access teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare a review checklist — Patient Access, Healthcare & Hospital Admin
Prepare a review checklist for Patient Access teams in Healthcare & Hospital Admin, delivered by the Onboarding Guide pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Summarize supplied feedback — Patient Access, Healthcare & Hospital Admin
Summarize supplied feedback for Patient Access teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Surface recurring points — Patient Access, Healthcare & Hospital Admin
Surface recurring points for Patient Access teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner are possible integration contexts that must be configured separately. Runs governed by policy, budgets, and the audit ledger.
Prepare follow-up questions — Patient Access, Healthcare & Hospital Admin
Prepare follow-up questions for Patient Access teams in Healthcare & Hospital Admin, delivered by the Feedback Summary pattern from supplied context. Epic and Cerner 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.