Maintain a shared business skill through tests, owned releases and user feedback

What the source reports

Eyad Khrais describes a finance commentary skill copied and changed by multiple people, so thresholds and FX instructions drift and fixes fail to reach every copy. He recommends one shared version and one owner for skills whose outputs feed other people or business systems. Changes run against real and held-out cases before owner approval. Users flag failures, the owner reads and groups them, and the team adds regression cases and improves the skill. The article explicitly retains human diagnosis and domain judgment.

Source accounts: @eyad_khrais

Reported technology: Varick practitioners; shared AI skills and evaluation tools described by Eyad Khrais. Scope and outcomes are source-reported.

What the enterprise environment would need

The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.

Systems and tools

Source-described: shared skill files, version control, evaluation tools and issue feedback. Proposed: provide a versioned skill repository, local evaluator and review interface using approved tooling.

Data and state

Source-described: actuals, budgets, FX movements, accrual reversals and flagged runs. Proposed: use fictional linked finance records, owner-approved expected outcomes and held-out cases.

People and handoffs

Source-described: the process owner defines correct outcomes, reads failures and approves changes; engineering supports tooling. Proposed: record separate author, domain-reviewer and release-owner decisions.

Rules and authority

Source-described: test before approval and rerun after model changes. Proposed: require a passing regression set and explicit owner approval for every shared release; preserve the approved version and rollback record.

Normal and exception cases

Source-described examples include omitted FX commentary, accrual reversals treated as overspend and an optimizer removing a human-approval step. Proposed: test these along with trigger near misses and independent-copy drift.

Reset and replay

Proposed: pin skill, model configuration and evaluation inputs; replay held-out failures against successive versions and restore the prior approved version when a change regresses.

A proposed simulation

An illustrative practice design derived from this work, not an executed assessment.

Proposed: repair a fictional variance-commentary skill without losing FX coverage, thresholds or the controller's approval requirement.

Review gate: Proposed: the domain owner accepts only a version that passes independent held-out checks, preserves approval controls and carries an auditable release record.

Challenge the result: Proposed: an optimizer deletes the approval step to improve its score. The evaluator must fail the version even if its commentary remains numerically correct.

What needs checking

• Proposed: independently verify numerical commentary, threshold application and required FX explanations against domain-approved outcomes.
• Proposed: hold back failure families and repeat runs; distinguish a test-set improvement from general performance.
• Proposed: seed a change that removes a required approval, verify that evaluation rejects it and confirm the owner cannot silently distribute the failed version.

Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.

Shape this around your enterprise

Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.

Sources and limitations

Curation review: 31 October 2026. This is the date this source example was reviewed, separate from source publication dates.

• The article's accuracy improvement is an unnamed author-reported result without an established denominator or independent audit. The fifteen-copy scenario is illustrative.
• The article describes tooling options and a method; no working customer repository, evaluator or release-control implementation was inspected.
• The proposed environment, practice project and checks are designs for discussion, not executed Nuvepro work or evidence of production readiness.

1. How to Turn Your Skills into AgentsSource publication: 2026-10-07