vendor-pulse

Summarize weekly vendor activity from captain's log entries.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/tenexity/cowork-distributor-plugins --skill vendor-pulse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-pulse
Source: https://github.com/tenexity/cowork-distributor-plugins/tree/main/plugins/tenexity-setup-team-hvac-plumbing/skills/vendor-pulse
Command: npx skills add https://github.com/tenexity/cowork-distributor-plugins --skill vendor-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vendor conversations can disappear into daily noise, making it easy to miss quiet relationships, overdue follow-ups, rebate issues, and other signals that deserve attention.

Core Features & Use Cases

  • Weekly vendor activity summary: Reads the last 7 days of captain's log entries and groups vendor mentions by tone and frequency.
  • Quiet-vendor detection: Surfaces vendors that have not appeared recently so you can decide whether to check in, prep for a QBR, or watch for drift.
  • Task and signal review: Cross-checks open vendor tasks and concerning mentions such as allocation cuts, rebate disputes, and price increases.
  • Use case: A distributor can ask for a weekly vendor pulse to see which reps, programs, or accounts need follow-up before issues grow.

Quick Start

Use the vendor pulse skill to review the last seven days of captain's log entries and produce a weekly summary of active vendors, quiet vendors, open tasks, and concerning signals.

Frequently Asked Questions about vendor-pulse

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

FAQPage Schema
How do I generate a weekly vendor activity summary from captain's log entries?

To generate a weekly vendor activity summary, the system reads the last seven days of captain's log entries to count vendor mentions, classify tone, surface quiet vendors, and cross-check open tasks to produce an actionable report.

What is quiet-vendor detection in HVAC and plumbing distributor workflows?

Quiet-vendor detection identifies HVAC and plumbing vendors that have not appeared in recent captain's log entries, helping you decide whether to check in, prep for a QBR, or watch for relationship drift.

Can I track concerning vendor signals like allocation cuts and rebate disputes automatically?

Yes, you can track concerning vendor signals automatically by cross-checking open vendor tasks and recent log entries to surface allocation cuts, rebate disputes, and price increases before issues grow.

What do I need to start summarizing vendor relationship tracking data?

To start summarizing vendor relationship tracking data, you need existing captain's log entries, top vendor lists, task records, and inventory action logs covering at least the last seven days of activity.

When should I run a vendor pulse review for overdue follow-ups?

You should run a vendor pulse review weekly to catch overdue follow-ups and quiet relationships, ensuring you see which reps, programs, or accounts need attention before issues grow.