Work Skills Setup Task Guidance
Purpose
Provides task-specific Work Skills orchestration under Scheduling and Dispatch.
Setup Task Skill Contract
- task_code:
ORA_FFS_TS_WORK_SKILLS - task_name:
Work Skills - parent_skill_id:
cx.field-service.scheduling-and-dispatch - pillar:
CX - offering:
Field Service - functional_area:
Scheduling and Dispatch - functional_area_code:
ORA_FFS_FA_SCHEDULING_AND_DISPATCH - available_flag:
Y - export_import_supported_flag:
UNKNOWN - csv_export_import_supported_flag:
UNKNOWN - source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use the Field Service offering skill as the starting point. This nested skill is
the only Work Skills task entry point and delegates shared workflow behavior to
pillars/cx/field-service/scripts/task_orchestration.py.
Setup Task Metadata
- Task name:
Work Skills - Task code:
ORA_FFS_TS_WORK_SKILLS - Available:
Y - Export/import supported:
UNKNOWN - CSV export/import supported:
UNKNOWN - CSV export/import routing:
not supported
Execution Directions
- Default:
core.data-loader.task-rest. The shared task runner delegates to that Core-owned route only; if it rejects PUT, it blocks and requires an explicitora_rest_executionrequest. - Explicit live-write route:
ora_rest_execution. It uses the task-local adapter, shared OAuth/Core REST client, immutable preview, exact-checksum approval, ordered Work Skill then Work Skill Group upsert PUTs, and GET verification. - No automatic fallback occurs between these directions.
Run Work Skills only through:
scripts/run_work_skills.py
The runner accepts free-format .xlsx field/value worksheets. Its task-local
adapter owns Work Skills workbook validation, OFSC Metadata paths, payload
mapping, and verification. The shared runner owns route selection, transport,
preview/approval binding, no-retry behavior, and safe write sequencing.
This runner handles Work Skill and Work Skill Group resource payloads. Group
members must reference a Work Skill included in the workbook or an existing
target Work Skill; optional group capabilities default to false. If the
workbook also contains Work Skill Conditions, it blocks: those are separate API
resources with their own POST/PUT identity contract and must not be silently
dropped.
Preflight and Approval
Before any live upsert, the runner validates the workbook and its required
fields, executes every registered Work Skills design rule using qualification,
routing/optimization, and onboarding/dispatcher evidence, and blocks configured
Work Skill Conditions until their separately approved API payload is implemented.
It validates group members and capacity rationale, resolves the requested execution direction, confirms an
active English language in the target environment, and retrieves an
object-or-absent baseline for every label. It then writes an immutable preview
containing the environment, PUT paths, request bodies, baselines, and SHA-256
checksum. A live PUT proceeds only when the caller explicitly selects
ora_rest_execution and supplies that fresh checksum as approval.
Failure Handling
Input and workbook failures stop before preview; route, baseline, language,
approval, and verification failures stop before the next side effect. The
runner does not automatically retry live PUT requests. It records redacted
run evidence under project/{project_id}/state/runs/, classifying failures as
input_validation, approval_or_workflow_blocker, or
unexpected_runner_error; it never records tokens, credentials, or request
bodies in durable project evidence.
Customer Input Template
Start customer data collection from
assets/Work_Skills_End_User_Input_Template.xlsx.
The Work Skills, Work Skill Groups, and Work Skill Group Members sheets
are executable input. Groups run only after their member Work Skills and retain
the declared member ratios. The Work Skill Conditions sheet is for design
capture only and remains blocked from execution until its separate API identity
contract is implemented.
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is UNKNOWN, so this task is not marked as CSV export/import supported in the effective setup-task catalog.
Do not route CSV export work to shared.setup-export.task-level-export or CSV import work to core.data-loader unless live Fusion metadata or Oracle guidance confirms support. Use shared.validation.setup-data-validator only when a setup data artifact is available for review. Use shared.validation.reference-data-validator when the task depends on cross-pillar reference data.
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
skill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill cx.field-service.scheduling-and-dispatch
for scope decisions. Persist only redacted run evidence under
project/{project_id}; never persist tokens, credentials, or customer payloads.