agentic-sales-sync

Reconcile agentic-sales narration JSON with the authoritative text script.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/v9ai/ai-engineer-roadmap --skill agentic-sales-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-sales-sync
Source: https://github.com/v9ai/ai-engineer-roadmap/tree/main/.claude/skills/agentic-sales-sync
Command: npx skills add https://github.com/v9ai/ai-engineer-roadmap --skill agentic-sales-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prevents the live, page-served agentic-sales narration content from drifting away from the authoritative written script by enforcing a deterministic text-only reconciliation.

Core Features & Use Cases

  • Deterministic, text-only sync: Reconciles data/agentic-sales.json against data/audio/agentic-sales.script.md without re-generating audio or modifying audio-related fields.
  • Drift-aware PR automation: Opens a single review PR when text changes are detected, or creates a reconcile PR/issue when structural chapter counts/titles don’t match.
  • Idempotent safety guards: Detects existing open sync PRs to avoid duplicate PRs, and never merges or deploys.

Quick Start

Trigger it by running /agentic-sales-sync.

Frequently Asked Questions about agentic-sales-sync

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

FAQPage Schema
How do I sync narration JSON with a text script without losing audio fields?

To sync narration JSON with a text script, use a deterministic Node engine to reconcile text-only content while preserving all audio fields. This prevents content drift by matching JSON against the authoritative script without modifying audio fields.

How do I prevent content drift in a page-served narration JSON file?

Prevent content drift by running a deterministic script during daily maintenance to enforce a text-only reconciliation. This process aligns the page-served JSON with the authoritative text script and opens a review PR when changes are detected.

How do I automate a GitHub pull request for JSON script drift detection?

Automate a GitHub pull request for JSON script drift by running a deterministic Node engine that detects text changes and opens a single review PR. It includes idempotent safety guards to detect existing open sync PRs and avoid creating duplicates.

What happens when chapter counts or titles don't match during JSON reconciliation?

When chapter counts or titles don't match during JSON reconciliation, the script detects a structural mismatch and creates a reconcile PR or issue instead of a standard text sync PR, ensuring structural integrity is reviewed manually.

Does the narration JSON sync script automatically merge or deploy changes?

The narration JSON sync script does not automatically merge or deploy changes. It includes idempotent safety guards that only open a single review PR for text drift detection, requiring manual review and deployment.

Do I need a Node environment to run the agentic-sales narration sync?

You need a Node environment to run the agentic-sales narration sync because the process requires executing the deterministic Node engine `scripts/sync-agentic-sales.mjs` to reconcile the JSON and script files.