allocating-zoom-numbers

Finds free zoom numbers by cross-checking DIVA source files and ISAM records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Allocating a new zoom number in Divalto Harmony by scanning only a5f.dhfi risks collisions, because partner-specific zooms live in a5fu.dhfi and declared constants in a5tczoom.dhsp may not yet be recorded. This Skill builds a global used-set from all sources and verifies candidates against actual specific source code before allocation. ## Core Features & Use Cases - Cross-source used-set detection: Unions zoom numbers from a5tczoom.dhsp constants, standard a5f.dhfi, specific/overlay a5fu.dhfi, and optional versionx9 copies, detecting usage across all ranges. - Phase 2 broad verification: Searches candidate numbers in specific/surcharge sources (.dhsp, .dhsf) and labels occurrences (zoom_call, touche_masque, affectation, non_reconnu) for human judgment, never auto-rejecting. - Domain and partner range allocation: Supports standard domain ranges (DAV, DAFF, DPAIE, etc.) and defaults to the partner convention range 90000-99999 for new specific zooms. - Use Case: Before creating a new entity or zoom for a partner customization, run the script to get confirmed free numbers above 90000 plus a report of suspicious candidates with file:line evidence. ## Quick Start Ask the assistant to find a free zoom number for a new specific zoom by running find_free_zoom.py with the paths to a5tczoom.dhsp, a5f.dhfi, a5fu.dhfi, and the specific sources root directory.

Frequently Asked Questions about allocating-zoom-numbers

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

FAQPage Schema
How do I find a free zoom number in Divalto Harmony?

Run find_free_zoom.py with --a5tczoom pointing to a5tczoom.dhsp, optionally adding --a5f-local, --a5fu, and --specifs-root. It returns JSON with confirmed free numbers, defaulting to the partner range 90000-99999 when no domain or range is given.

Why is scanning a5f.dhfi alone not enough to allocate a zoom number?

a5f.dhfi only holds standard zooms and is never modified; partner-specific zooms live in a5fu.dhfi, and constants declared in a5tczoom.dhsp may be used without being recorded yet. The used-set must be the union of all these sources.

What is the 90000 convention for partner zoom numbers?

New partner-specific zooms start at 90000 by convention, which is the default allocation range. Detection of used numbers remains global across all ranges, since specific zooms below 90000 also exist.

Does the script automatically reject zoom numbers found in specific sources?

No. Phase 2 labels each occurrence (zoom_call, touche_masque, affectation, or non_reconnu) with file, line, and confidence, then reports them as suspects for human judgment. Only candidates with zero occurrences are returned as free.

What is the maximum zoom number range supported?

ZoomNum is stored on 5 characters in the M4 structure of a5f/a5fu, so ranges above 99999 are rejected with exit code 2. For menu EnrNo values above 100000, use the allocating-menu-enrno skill instead.