customer-feedback-sync

Compare local HTML customer feedback trackers with shared Google Sheets for safe sync.

Updated Aug 27, 2026

Search Tags:#diff analysis #google sheets #customer feedback #upsert #html parsing #product operations #tracker sync

Ready to run

npx skills add https://github.com/solaius/ai-asset-registry --skill customer-feedback-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: customer-feedback-sync
Source: https://github.com/solaius/ai-asset-registry/tree/main/.claude/skills/customer-feedback-sync
Command: npx skills add https://github.com/solaius/ai-asset-registry --skill customer-feedback-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual work of reconciling a local customer interest tracker with a shared Google Sheet, so product teams can keep one trusted view of customer feedback and status.

Core Features & Use Cases

Local-to-Remote Diffing: Compares the HTML tracker against the centralized sheet and identifies new, updated, and remote-only customer records.
Field Mapping and Upsert Planning: Translates tracker content into the rhai-tracker schema, including contacts, pain points, feature feedback, wishlist items, comments, and status.
Safe Sync Workflow: Presents a clear summary before pushing changes and preserves remote-only data through upsert-based merging.
Use Case: A PM updates the local tracker after customer meetings and uses this Skill to see exactly what changed before syncing the approved updates to the shared sheet.

Quick Start

Ask the skill to compare the local customer tracker with the shared sheet and summarize the customers that are new, updated, or remote-only.

Frequently Asked Questions about customer-feedback-sync

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

FAQPage Schema

How do I sync a local customer feedback tracker to a shared Google Sheet?▼

To sync a local HTML customer feedback tracker to a Google Sheet, the Skill parses the local file, maps fields to the remote schema, and prepares an upsert-safe import that preserves remote-only records.

What is the best way to compare local HTML tracker updates with a shared sheet?▼

Comparing local HTML tracker updates with a shared sheet requires directional change detection. This Skill identifies new, updated, and remote-only customer records to ensure a safe sync workflow without overwriting existing remote data.

How does upsert-safe import handling work for customer feedback records?▼

Upsert-safe import handling works by merging local tracker updates into the shared Google Sheet without overwriting remote-only fields, ensuring existing customer records are updated while remote-exclusive data is preserved during sync.

Can I review changes before pushing tracker updates to the shared sheet?▼

Yes, you can review changes before pushing tracker updates. The Skill generates a clear summary of new, updated, and remote-only records, allowing you to approve the safe sync before any data is pushed to the sheet.

Does the customer feedback sync support field-level enrichment like pain points and wishlist items?▼

Yes, the sync supports field-level enrichment by translating tracker content into the rhai-tracker schema, specifically mapping contacts, pain points, feature feedback, wishlist items, comments, and status to the shared sheet.

What happens to remote-only customer records when syncing from a local tracker?▼

When syncing from a local tracker, remote-only customer records are preserved through upsert-based merging. The Skill flags remote-only entries during the diff analysis to ensure no existing shared sheet data is lost.