TypingMindTypingMindThe best frontend for AI
Manage Job Roles logo

Manage Job Roles

Organization
oracle
Manage Job Roles

Prepare individual custom-role creation, updates, redesign and deletion requests, and route supported role changes through validated FSM CSV packages and approval-gated Data Loader execution. Also export, migrate or restore Manage Job Roles setup data.

Overview

Publisheroracle
RepositoryFusion-Setup-Configuration-Registry
Skill nameManage Job Roles
Stars
112
Forks
26
Bundled files
5
LicenseUPL-1.0
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by oracle on GitHub. Read the source before you install it.

Installation

Install the Manage Job Roles AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/oracle/Fusion-Setup-Configuration-Registry/tree/main/pillars/common/security-console/manage-job-roles
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/oracle/Fusion-Setup-Configuration-Registry.git /tmp/Fusion-Setup-Configuration-Registry
mkdir -p .claude/skills
cp -r /tmp/Fusion-Setup-Configuration-Registry/pillars/common/security-console/manage-job-roles .claude/skills/oracle-manage-job-roles
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Manage Job Roles in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Manage Job Roles on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Manage Job Roles is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Manage Job Roles

Purpose

Provide a controlled, cross-pillar method to create, update, redesign and process deletion requests for individual custom roles, and to export, validate and approval-gate the import of the Manage Job Roles FSM setup task. Delegate transport and live import execution to the declared shared and core dependencies. Prepare user-specified role values only against a verified FSM CSV template, retaining its headers, metadata and supported operations.

Export and move the FSM setup task Manage Job Roles only through the declared dependency workflows. The catalog identity is task code ASXS_MANAGE_JOB_ROLES; require a current catalog or live-task lookup to confirm that its export/import flags remain supported before execution.

Scope and boundaries

  • Accept creation, update, redesign and deletion requests for individual custom roles. Prepare only operations supported by the current FSM CSV contract; execute supported changes through core.data-loader.
  • Support task-level FSM CSV export and import of an exported, supplied or template-conformant candidate archive.
  • Honor the user's role design and explicit changes in this skill. Preserve unrelated fields and memberships; do not substitute another skill's missing execution classification for this declared FSM/Data Loader route.
  • Do not call Fusion, OAuth, UCM, REST, FSM, or loader commands directly. shared.setup-export.task-level-export owns export; core.data-loader owns every import preflight, upload, initiation, and monitoring route.
  • Treat a changed archive, source scope, target environment, or validation result as a new request that must pass all gates again.

Required preflight

  1. Resolve the project workspace, requested operation, source and target environments, and the exact job-role scope. Require source and target to be distinct for a migration request; require explicit confirmation for a same-environment restore.
  2. Confirm the exact task name and code with shared.setup-export.task-level-export and verify its current CSVExportImportSupportedFlag is Y. If the task is ambiguous, unavailable, or unsupported, record a catalog-mismatch diagnostic and stop.
  3. Confirm the operator has Functional Setup Manager export access in the source and Data Loader import privileges in the target. Do not request or expose credentials, access tokens, or tenant secrets.
  4. Record the source/target identities, task code, scope, and a redacted execution plan in the project workspace before any side effect.

Individual custom-role operations

Requested operationPreparation and execution boundary
CreatePrepare a custom-role definition and explicit hierarchy or privilege membership rows using the verified template.
UpdateIdentify the existing custom role by exact code; change only the requested supported definition fields or memberships.
RedesignPrepare an explicit before/after plan for the requested role, hierarchy and direct privilege changes. Use ADD for additions and REMOVE for requested membership removals.
Delete a hierarchy or privilege membershipRetain a row identifying the parent and member and set the documented membership action to REMOVE. Removing a CSV row is not a deletion operation.
Delete an individual roleAccept and scope the request, then confirm an explicit whole-role deletion operation in current Oracle guidance and the target's FSM import contract. Execute only if that operation is supported by Data Loader's selected FSM route. The existing role-definition template has no deletion-action column; do not invent DELETE, treat membership REMOVE as role deletion, or silently switch to browser, REST, SCIM or HDL. If no supported operation is established, record the operation-support gap and required next action.

Creation, updates and redesign are intentional changes in the selected target; they are not automatically same-environment restores. Preserve source metadata and construct a new candidate before validation. Once validated, leave the archive unchanged through the Data Loader approval and execution steps.

Do not edit or delete Oracle-seeded roles as if they were custom roles. Role code changes, user provisioning and data-security-policy changes require an explicit supported contract; this CSV route does not add or remove direct data-security policies. Inherited data access can change when memberships change.

For deletion or removal, identify the exact affected role and memberships and show the intended removal in the operation plan before Data Loader's approval preview. Do not infer deletion from an omitted row, a blank value or a redesign request. Keep template-export auto-authorization separate from actual role mutations; Core Data Loader remains the authoritative import approval gate.

Export Manage Job Roles

  1. Route the export to shared.setup-export.task-level-export with task name Manage Job Roles, task code ASXS_MANAGE_JOB_ROLES, the source environment, and project ID.
  2. Let that skill perform the task lookup, support-flag validation, export process creation, polling, download, and project export persistence. Do not substitute a template export for a data export.
  3. Preserve the returned ZIP unchanged. Register its path, SHA-256, process ID, task identity, source environment, and export timestamp as the export record.
  4. On an export timeout or failure, preserve the task code, process ID, last status, process log reference, elapsed wait, and next-check path. Do not start another export process automatically.

Template-first import preparation

Read FSM input preparation when the user needs help with the template. Accept plain-language requirements, safely extract the package, explain the columns and prepare the candidate; do not require the user to understand or populate the CSV before work can start.

For user-specified custom role data, use the target environment's task-level CSV template/spec package through shared.setup-export.task-level-export. Template acquisition is not a migration or a same-environment restore. Automatically authorize and execute the template/spec export needed to prepare a user-requested role import; do not ask for a separate template-export approval. This user-authorized exception applies only to setupTaskCSVTemplateExports for the selected task and environment. It does not authorize populated data exports, uploads, role imports, or retries after an uncertain POST outcome. Retain identity, privilege, catalog, payload and audit checks, and leave actual import approval to core.data-loader. Verify the template supports every requested field and hierarchy reference; do not invent values, columns, category codes or an IP-access encoding.

Oracle documents role code, name, description, category and all-IP-address access in Functional Security Custom Roles, plus parent/member codes and ADD/REMOVE operations in the hierarchy file. Direct data-security policies are not included in this CSV route. Consult the Oracle CSV role contract and CSV package editing guidance. The target's template and import validations remain authoritative for a new role; catalog flags alone do not prove the complete supplied request is valid. This workflow uses core.data-loader for execution, never browser creation.

  1. Unless the user explicitly overrides this sequence, export the task first and provide that export as the import template before asking for import content. Explain that the template establishes the supported archive and file structure; it is not approval to import.
  2. When the user provides an input file, compare it with the export template for file names, headers, column order, encoding, required values, and task-specific references. Help correct structural defects in a separate candidate file; preserve the supplied original and do not silently alter business values.
  3. Give the user a concise change summary and identify any unresolved values or references. Use the corrected file only after it conforms to the export structure and has been assembled into a new candidate archive using the supported archive shape. That candidate is a new artifact and must pass the validation and approval gates below.
  4. The user may override the export-first sequence, template choice, or proposed file corrections at any time. Honor that direction, while retaining the required task-identity, validation, and immediate import-approval gates.

Validate the archive for import

  1. Require the supplied archive to be a non-empty ZIP and bind its SHA-256 to task code ASXS_MANAGE_JOB_ROLES, source environment, and target environment.
  2. Route setup-data validation to shared.validation.setup-data-validator and preserve the resulting validation evidence. Fail closed on archive-shape, task-identity, scope, catalog, environment, or privilege mismatch.
  3. Do not alter, unpack-and-repack, merge, or otherwise transform the archive after validation. Any change invalidates the evidence and approval preview.

Import the validated archive

  1. Route the immutable validated archive to core.data-loader as an FSM, task-routed import. Provide the task context, target environment, archive SHA-256, and validation evidence.
  2. Let core.data-loader complete its required source and API validation and produce its immutable approval preview. This skill must not bypass or replace the Data Loader route with a direct FSM API, UCM upload, REST call, CSV utility, or browser action.
  3. Present the exact target environment, task code, archive name and SHA-256, validation result, and expected import impact. Stop before the first POST.
  4. Proceed only after the user gives a separate, immediate approval for that immutable preview. core.data-loader revalidates the archive and owns the upload, initiation, process monitoring, and diagnostics.
  5. Do not retry an upload, initiation, import, overwrite, or replacement process without a fresh approval. Preserve returned request IDs, process-log references, and redacted diagnostics in the project workspace.

Failure handling

Classify failures as input validation, catalog mismatch, authorization, transport/environment, Fusion API, process timeout, process failed, artifact persistence, or approval blocker. Redact credentials, tokens, customer data, and sensitive role configuration. For any ambiguity or unsafe path, record the blocker and recommended next action, then stop.

Setup Tasks

No setup tasks were supplied when this skill was generated.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Manage Job Roles AI skill do?

Prepare individual custom-role creation, updates, redesign and deletion requests, and route supported role changes through validated FSM CSV packages and approval-gated Data Loader execution. Also export, migrate or restore Manage Job Roles setup data.

Why use Manage Job Roles on TypingMind?

Because you install it once and use it with any model. Manage Job Roles is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Manage Job Roles in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/oracle/Fusion-Setup-Configuration-Registry/tree/main/pillars/common/security-console/manage-job-roles. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Manage Job Roles?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Manage Job Roles?

As many as you like. As long as a model supports skills, you can use Manage Job Roles with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Manage Job Roles AI skill free?

Yes. It is published on GitHub by oracle under the UPL-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
NousResearch logo

Huggingface Hub

NousResearch
OrganizationPopular

HuggingFace hf CLI: search/download/upload models, datasets.

53.5K
250.4K
Instructions
View
NousResearch logo

Pinecone

NousResearch
OrganizationPopular

Managed vector DB for production RAG and search.

53.5K
250.4K
1 files
View
NousResearch logo

Qdrant

NousResearch
OrganizationPopular

Vector search engine for production RAG systems.

53.5K
250.4K
2 files
View
NousResearch logo

Tensorrt Llm

NousResearch
OrganizationPopular

High-throughput LLM inference on NVIDIA GPUs.

53.5K
250.4K
3 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇