Individual skill

client-communications-research

Use when turning client calls, chats, CRM notes, call recordings, messenger exports, transcripts, or support/sales conversations into an advertising, positioning, objection, FAQ, or customer-language research package.

plugins/nebelov/yandex-direct-for-all/skills/client-communications-research/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Client Communications Research

Use this skill when the task is to analyze real client communications and produce conclusions, quotes, objections, audience language, sales insights, ad angles, or positioning.

This skill starts after source acquisition is planned or under way. For amoCRM access and corpus acquisition, use `amocrm-api-control` first. For calls and meetings, first look for a ready transcript or meeting notes from the user's existing tools (meeting recorder, messenger bot, voice-memo transcripts). Start a paid transcription only when no ready transcript exists, and only with the service the user approved. This skill governs the research package and final synthesis boundary.

## Required Inputs

Before synthesis, create or read a compact corpus ledger with:

- source systems and source types: amoCRM notes, calls, recordings, chats, email, messenger exports, telephony exports, support tickets, or files;
- requested date window and actual acquired date window;
- event counts by source type;
- audio file count, transcript count, empty/missing/failed count, and duplicate count;