agentleFS
SimonKreis-RichardSimonKreis-Richard/oracle-fusion-agentic-toolkit/skills/fusion-reference/SKILL.md

fusion-reference

Skill0 starsChanged 51 days agoMITView on GitHub

Shared product knowledge on Oracle Fusion Cloud HCM, with no workflow in it. Read it when another skill points here, or when the user asks a plain knowledge question about how the product is put together, where configuration lives and where it does not, Redwood versus classic pages, what Transaction Design Studio governs versus Visual Builder Studio, how security is composed (job, abstract and duty roles, privileges, data security, security profiles, role mappings), or what the scheduled processes do. It contains verbatim Oracle documentation quotes with their URLs. Not for something broken (hcm-debugging), not for building a change (hcm-configuration), not for a recommendation (hcm-architecture).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not read all six. Every file carries verbatim sentences from the Oracle documentation with their URL: quote those, with the URL, rather …

    line 14
  2. Distinctive:

    No engagement data: no client name, no custom role name, no ticket key.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Oracle Fusion Cloud HCM: the shared reference

This skill is a knowledge base, not a procedure. It exists so that the three workflow skills (hcm-debugging, hcm-configuration, hcm-architecture) share one description of the product instead of three that drift apart. Nothing here says what to do: it says how the product is built, so that a workflow can reason about it.

How to use it: open the one file below that the question needs, read it, and cite from it. Do not read all six. Every file carries verbatim sentences from the Oracle documentation with their URL: quote those, with the URL, rather than restating them. When a question is not covered, the answer is on docs.oracle.com, found by web search restricted to that domain and read through fetch_oracle_page of the oracle-fusion-docs MCP, which is the only path to the verbatim text.

The six files

FileRead it for
navigation.mdthe full click path from the home page to each object (user roles, role mappings, data roles, document type security profiles, document records, change manager, scheduled processes, nudges), with whether each path was verified in an instance. Read it before writing any step that sends the operator into an instance
product-structure.mdenterprise structures (enterprise, legal employer, business unit, legislative data group), the person model (person, work relationship, assignment), date effectivity, correction versus update, data loading
configuration-map.mdwhere configuration lives: Setup and Maintenance (offerings, functional areas, tasks), profile options and their levels, lookups and their customisation levels, flexfields, approval rules, setup export and import, quarterly updates and opt-in features, and what is not configuration
pages-and-extensions.mdRedwood versus classic pages and how Redwood is enabled, what Transaction Design Studio governs, what Visual Builder Studio governs, what Page Composer and Autocomplete rules govern, and which of them applies to which page family
security-model.mdrole types (abstract, job, duty, aggregate privileges, data roles), function security versus data security, security profiles, role mappings and their conditions, autoprovisioning, areas of responsibility, the LDAP processes, and the one diagnostic tell that matters most
scheduled-processes.mdwhat a scheduled process is, the processes that must be scheduled for HCM to behave (manager hierarchy, position synchronisation, autoprovisioning, search keywords, alerts), and why schedules do not follow an environment copy

Two constants that every file assumes

The configuration lives only in the instance. There is usually no up-to-date configuration workbook on an AMS engagement. So a fact about the current configuration is something to read in the instance, with its path, never something to assume.

Two instances, one symptom. A problem is observed in production; the consultant can read and change only a test instance, a copy of production some weeks behind. Configuration mostly transfers across that gap. Scheduled process schedules, submissions and history do not. The workflow skills carry the detail of what transfers; the reference only explains why.

Conventions

  • A quoted sentence is copied character for character from the fetched page and carries the page title and URL. If a sentence has no URL, it is the author's reading, not Oracle's wording.
  • Oracle renames things across updates. Where a name changed (HCM Experience Design Studio and Transaction Design Studio, for one), both names are given.
  • No engagement data: no client name, no custom role name, no ticket key. Examples use generic names.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.