← HR OmniCONTENT HISTORY
WHAT CHANGED
Update to HR Omni
Snapshot Nov 3, 2026 · 19:19 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save HR Omni and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use for customer-facing questions about HR Omni products, capabilities, workflows, limitations, pricing, switching, security, terminology, and product discovery.",
"included_files": [
{
"relative_path": "references/access-control.md",
"size_in_bytes": 1235
},
{
"relative_path": "references/assets-inventory.md",
"size_in_bytes": 1087
},
{
"relative_path": "references/calendar-reporting.md",
"size_in_bytes": 1485
},
{
"relative_path": "references/documents.md",
"size_in_bytes": 1728
},
{
"relative_path": "references/index.md",
"size_in_bytes": 3657
},
{
"relative_path": "references/leave-management.md",
"size_in_bytes": 2018
},
{
"relative_path": "references/platform-core.md",
"size_in_bytes": 1925
},
{
"relative_path": "references/pricing-switching.md",
"size_in_bytes": 1298
},
{
"relative_path": "references/security.md",
"size_in_bytes": 1064
},
{
"relative_path": "references/sources.md",
"size_in_bytes": 1897
},
{
"relative_path": "references/sso.md",
"size_in_bytes": 1149
},
{
"relative_path": "references/terminology.md",
"size_in_bytes": 739
},
{
"relative_path": "references/worklogs.md",
"size_in_bytes": 1837
}
],
"name": "hr-omni-product",
"skill_md_contents": "---\nname: hr-omni-product\ndescription: Use for customer-facing questions about HR Omni products, capabilities, workflows, limitations, pricing, switching, security, terminology, and product discovery.\n---\n\n# HR Omni Product Knowledge\n\nUse `references/index.md` first. Read only the detailed reference files relevant to the user's question.\n\n## Source order\n\n1. Bundled verified customer-safe references.\n2. If the bundled references do not answer the question, check current official HR Omni sources listed in `references/sources.md`, starting with `llms.txt` and the relevant official product page.\n3. Use pricing, FAQ, security, privacy, terms or knowledge-base pages where relevant.\n4. Use HR Omni blog content only as supporting context, not as primary product truth.\n5. Use the wider web only when the question genuinely requires external information such as law, standards, market context or competitor facts.\n\nIf a live official page conflicts with a bundled verified fact, do not silently choose one. State that the sources conflict and avoid asserting the disputed fact until clarified.\n\n## Messaging\n\nLead with the operational outcome where useful: control, visibility, accountability, consistency, simplicity or scalability. Then explain the exact HR Omni workflow that creates that outcome.\n\nDo not invent features, integrations, certifications, imports, exports, migration automation, analytics or customer outcomes. Do not describe roadmap work as available. Do not claim HR Omni guarantees legal or regulatory compliance.\n\nUse UK English unless the user asks for another language.\n"
}SHA-256 of public snapshot: 1ee84feadfe0bf51d620066af940a66a7628775e612e08cc0a47a864f0330441