customer-feedback-refresh

Audit customer feedback trackers for stale items, missing sources, and status inaccuracies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/solaius/ai-asset-registry --skill customer-feedback-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-feedback-refresh
Source: https://github.com/solaius/ai-asset-registry/tree/main/.claude/skills/customer-feedback-refresh
Command: npx skills add https://github.com/solaius/ai-asset-registry --skill customer-feedback-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps keep a customer interest tracker accurate by finding stale action items, missing meeting sources, and outdated status or interest notes before they create confusion.

Core Features & Use Cases

  • Staleness Review: Flags open action items that have not changed recently and identifies rows that may be resolved elsewhere.
  • Source Coverage Check: Compares tracker entries against transcription files to find meetings that were not ingested or entries that lack source evidence.
  • Status and Theme Validation: Verifies customer status tags, counts, production targeting, requested features, and cross-customer themes against current project reality.
  • Use Case: A product manager can use this Skill to audit a live customer tracker after new meetings, releases, or support updates and then decide what should be updated.

Quick Start

Use the customer-feedback-refresh skill to review the tracker for stale items, missing sources, and status inaccuracies.

Frequently Asked Questions about customer-feedback-refresh

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

FAQPage Schema
What is source coverage validation in a customer feedback tracker?

To audit a customer feedback tracker, review open action items for staleness, validate status tags against current project reality, and compare entries against meeting transcriptions to identify missing source evidence.

Can I use a staleness review to find resolved action items across cross-customer themes?

Checking source coverage compares tracker entries against transcription files to find meetings that were not ingested or rows lacking source evidence. This ensures every customer status tag and action item has supporting documentation.

What is the best way to review a live customer tracker after new meetings and product updates?

Validating cross-customer themes compares requested features, production targeting, and summary counts against current project reality. This verifies that customer status tags accurately reflect recent product release changes and updates.

How do I audit a customer feedback tracker for stale action items and outdated statuses?

The best way to review a live customer tracker is running a comprehensive audit covering action item freshness, source coverage against meeting transcriptions, and status tag accuracy. This identifies what should be updated after releases.

Can I use a staleness review to find resolved action items across cross-customer themes?

Tracker audit works best with meeting transcriptions and product release changes for source coverage validation. Without these inputs, staleness review can still flag unchanged action items but cannot fully validate missing source evidence or cross-customer themes.

What is the best way to review a live customer tracker after new meetings and product updates?

Validating cross-customer themes compares requested features, production targeting, and summary counts against current project reality. This verifies that customer status tags accurately reflect recent product release changes and updates.