understanding-integrator-workspace

Resolves and audits Divalto Harmony integrator workspace paths, profiles, and SQL connections.

6|Updated May 11, 2026
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill understanding-integrator-workspace-divalto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: understanding-integrator-workspace
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/understanding-integrator-workspace
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill understanding-integrator-workspace-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? On a Divalto integrator workstation, multiple ERP versions, client databases, and integration projects coexist, so blind file reads or copies routinely target the wrong version or base. This Skill establishes a mandatory session protocol that identifies the workspace's implicit file, resolves harmony paths, classifies standard versus specific directories, and verifies SQL connectivity before any file operation begins. ## Core Features & Use Cases - Workspace path resolution: Parses the implicit file's ordered search path and resolves harmony aliases (/specifs/, /sources/, /divalto/) via divaltopath.cfg, fconfig, and a whitelisted Windows registry lookup. - Canonical file location (R-13): Finds the correct version of a standard source file by walking the declared search path in order instead of running a blind filesystem find. - Coherence auditing: Cross-checks the implicit file against .dhpt profiles, divaltoserver.cfg, connexions.xml, and ODBC DSN registry entries, reporting findings by severity. - Use Case: Before creating a _base.dhsf companion for a surcharge, run the audit to confirm which ERP version the workspace targets, then copy the companion from the canonical resolved path rather than a generic standard tree. ## Quick Start Ask the assistant to analyze the current Divalto integrator workspace and confirm the implicit file before making any changes.

Frequently Asked Questions about understanding-integrator-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the correct version of a Divalto standard file on an integrator workstation?

Use the R-13 workflow: parse the workspace's implicit file to get the ordered search path, resolve each harmony alias via divaltopath.cfg or fconfig, then search for the file in order and take the first hit. Never run a blind find across generic standard trees, which would return an arbitrary installed version.

How to audit a Divalto workspace for configuration inconsistencies?

Run scripts/check_workspace_coherence.py with --workspace, --implicit, and --confirmed-by-user after the user confirms the implicit file. It verifies physical path existence, cross-checks .dhpt profiles against the implicit file, detects divergent cheminbases or versioncible values, and reports findings by severity.

How does Divalto resolve the SQL database for a workspace?

Through two doors: the Harmony door parses divaltoserver.cfg for the SQL path, extracts the DSN from fhsql.dhfd, and reads the ODBC configuration from the registry; the ADO.NET door maps the implicit file's XML companion to an entry in connexions.xml. Both doors must point to the same database.

Why do the audit scripts exit with code 3?

Exit code 3 means the --confirmed-by-user flag was missing. The scripts enforce rule R-1 and principle P-B by refusing to run until the collaborator has explicitly confirmed the implicit file, preventing the assistant from presuming a candidate.

Can this skill read any Windows registry key for diagnostics?

No. Registry access is restricted to a strict whitelist: the Divalto divalto.ini System keys (CheminUl1, CheminFpartd) and the ODBC.INI keys for a specific DSN. Recursive queries, key enumeration, and exploration of neighboring keys are explicitly forbidden under principle P-C.

What are the limitations of the workspace audit scripts?

Registry discovery requires Windows with the winreg module; on other systems it returns an error requiring manual input. The fconfig.dhfd read uses a raw-bytes heuristic pending a proper ISAM structure definition, and R-8 (fconfig SQL fallback) is not yet implemented.