agentleFS
appuniteappunite/skills/communication-analyst/SKILL.md

communication-analyst

Skill1 starsChanged 8 months agoMITView on GitHub

Analyze meeting transcriptions using transactional analysis and communication best practices. Provides comprehensive feedback on communication patterns, ego states, transaction types, psychological games, power dynamics, and meeting effectiveness from a specific person's perspective. Use when user requests: (1) "Analyze my communication in this meeting", (2) "Review my communication patterns", (3) "How did I come across in this meeting", (4) Communication feedback on transcripts (.vtt or .txt files), or (5) Transactional analysis of conversations.

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. About 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look for possessive language: "my communication", "how did I..."

    line 41
  2. Distinctive:

    Check vault context for user name (Karol Wojtaszek in this system)

    line 42
  3. Distinctive:

    If unclear: Ask explicitly: "Whose communication perspective should I analyze?

    line 45
  4. Distinctive:

    Read the entire transcript to understand:

    line 49
  5. Distinctive:

    Document patterns across multiple instances

    line 77
  6. Distinctive:

    Follow the structure in references/analysis-template.md:

    line 83
  7. Distinctive:

    Verify analysis meets standards:

    line 97
  8. Distinctive:

    Every observation supported by specific quotes

    line 178
  9. Distinctive:

    Look for Free Child (authentic) vs.

    line 239
  10. Distinctive:

    Check for healthy disagreement markers (focus on ideas, curiosity)

    line 243
  11. Distinctive:

    Look for unhealthy patterns (avoidance, escalation, triangulation)

    line 244
  12. Distinctive:

    Document evidence across multiple instances

    line 249
  13. Distinctive:

    Check for: decisions documented, owners assigned, deadlines set

    line 255
  14. Distinctive:

    Evidence-based: Every claim supported by quotes + timestamps

    line 325

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Communication Analyst

Analyze communication patterns in meeting transcripts using transactional analysis (TA) principles and communication best practices.

Overview

This skill produces comprehensive communication analyses that:

  • Identify ego states (Parent, Adult, Child) and transaction patterns
  • Diagnose communication effectiveness and problematic patterns
  • Provide evidence-based feedback with specific quotes and timestamps
  • Offer actionable recommendations for improvement

Input Requirements

Supported Formats

  • .vtt (WebVTT video transcription files)
  • .txt (plain text transcripts)

Transcript Structure

Transcripts should include:

  • Speaker identification (names or roles)
  • Timestamps (for quote attribution)
  • Complete conversation content

Analysis Workflow

Step 1: Identify the Focal Person

Auto-detection strategy:

  • Look for possessive language: "my communication", "how did I..."
  • Check vault context for user name (Karol Wojtaszek in this system)
  • Infer from conversation history

If unclear: Ask explicitly: "Whose communication perspective should I analyze? (e.g., 'Analyze Karol's communication' or 'Analyze from Maria's perspective')"

Step 2: Read and Process Transcript

Read the entire transcript to understand:

  • Meeting context and purpose
  • Participants and their roles
  • Key discussion topics
  • Overall dynamics

Step 3: Apply TA Framework

Consult references/ta-framework.md for:

  • Ego state identification: Parent, Adult, Child indicators
  • Transaction analysis: Complementary, crossed, ulterior
  • Psychological games: "Yes, but...", ITHY, NIGYSOB patterns
  • Life positions: OK Corral dynamics

Step 4: Diagnose Communication Patterns

Consult references/communication-patterns.md for:

  • Speaking time distribution: Ratios and balance
  • Listening quality: Active, empathic, passive
  • Question patterns: Open vs. closed, genuine vs. rhetorical
  • Meeting structure: Openings, closures, facilitation
  • Power dynamics: Authority, influence, deference
  • Participation balance: Equal airtime, invitation patterns

Step 5: Extract Evidence

For each observation:

  • Find supporting quotes with exact timestamps
  • Document patterns across multiple instances
  • Note specific behaviors (not just interpretations)
  • Track both strengths and development areas

Step 6: Generate Analysis

Follow the structure in references/analysis-template.md:

  1. YAML frontmatter with metadata
  2. Meeting context for each segment
  3. Transactional dynamics analysis
  4. What works well (strengths)
  5. What needs improvement (development areas)
  6. Key moments with deep dives
  7. Communication patterns (systemic diagnosis)
  8. Recommendations (actionable guidance)
  9. TA summary (overall conclusion)

Step 7: Quality Check

Verify analysis meets standards:

  • Every claim supported by quote + timestamp
  • TA concepts explained clearly (not jargon-heavy)
  • Recommendations specific and actionable
  • Balanced: includes both strengths and development areas
  • Polish diacritics preserved (ą, ć, ę, ł, ń, ó, ś, ź, ż)
  • Focal person's perspective clearly addressed
  • Evidence-based throughout

Output Structure

YAML Frontmatter

---
type: Analysis
title: [Descriptive analysis title]
description: [Brief description]
tags:
  - communication
  - transactional-analysis
  - leadership
  - feedback
category: Career Development
date: [YYYY-MM-DD]
sources:
  - "[[Link to transcript 1]]"
  - "[[Link to transcript 2]]"
---

Analysis Sections

For one-on-one meetings:

## Meeting: [Person A] -- [Person B] ([context])

**Context**: [Brief description]

### Dynamika transakcyjna
[Ego state analysis with quotes]

### What works well
[Strengths with evidence]

### What needs improvement
[Development areas with specific examples]

For group meetings, add:

### Mapa transakcji -- kto w jakiej pozycji operuje

| Person | Dominant Position | Pattern |
|--------|------------------|---------|
| **[Name]** | [Ego State] | [Behavior pattern] |

### Key Moments Analysis
[Deep dives on pivotal interactions]

### Communication Patterns -- Systemic Diagnosis
[Patterns affecting entire group]

Always include:

## Recommendations

### For [Focal Person]
[Specific, actionable guidance]

### For [Group/Dynamic]
[Systemic recommendations]

## Summary from TA Perspective
[Overall transactional analysis conclusion]

Analysis Principles

Evidence-Based

  • Every observation supported by specific quotes
  • Include timestamps for all evidence
  • Document patterns across multiple instances
  • Distinguish observation from interpretation

Balanced Perspective

  • Ratio: ~30% strengths, ~70% development areas
  • Purpose is growth, not criticism
  • Acknowledge what's working before suggesting improvements
  • Frame development areas as opportunities

TA Framework Application

  • Ego states: Identify Parent, Adult, Child positions
  • Transactions: Map complementary, crossed, ulterior patterns
  • Games: Detect "Yes, but...", ITHY, and other games
  • Life positions: Assess I'm OK/You're OK dynamics

Practical Utility

  • Recommendations must be specific and actionable
  • Provide examples of alternative approaches
  • Connect insights to real impact on outcomes
  • Focus on patterns, not one-off moments

Cultural Sensitivity

  • Preserve Polish diacritics correctly
  • Respect professional context and norms
  • Balance directness with tact
  • Honor emotional vulnerability when expressed

Common Analysis Patterns

For Leaders/Facilitators

Focus on:

  • Speaking time ratio (should be 20-30% in groups)
  • Question quality (open vs. closed)
  • Participation balance (active invitations)
  • Emotional intelligence (honoring feelings before problem-solving)
  • Closure quality (clear next steps and owners)

For Individual Contributors

Focus on:

  • Assertiveness vs. compliance patterns
  • Adult-Adult transaction capability
  • Contribution quality and frequency
  • Resistance or game patterns
  • Authentic expression vs. adapted responses

For Power Dynamics

Identify:

  • Who speaks first and most
  • Who gets interrupted vs. who interrupts
  • Whose ideas get built on
  • Deference patterns
  • Authority vs. expertise dynamics

Special Considerations

When Emotions Surface

  • Note emotional expressions as valuable data
  • Distinguish between honoring emotion and rationalizing it
  • Identify if emotions were validated before problem-solving
  • Look for Free Child (authentic) vs. Adapted Child (defensive)

When Conflict Emerges

  • Identify if conflict was named explicitly
  • Check for healthy disagreement markers (focus on ideas, curiosity)
  • Look for unhealthy patterns (avoidance, escalation, triangulation)
  • Assess conflict resolution approaches

When Games Are Detected

  • Name the game pattern (e.g., "Yes, but...")
  • Document evidence across multiple instances
  • Identify roles (Victim, Persecutor, Rescuer)
  • Note the payoff (what each player gains)
  • Suggest Adult-Adult alternatives

For False Closures

  • Check for: decisions documented, owners assigned, deadlines set
  • Note what was NOT decided (parking lot)
  • Identify vague commitments ("we'll sync", "let's figure it out")
  • Recommend specific closure practices

Reference Materials

For TA Concepts

See references/ta-framework.md for comprehensive coverage of:

  • Ego states (Parent, Adult, Child)
  • Transaction types
  • Psychological games
  • Strokes and recognition
  • Life positions

For Communication Patterns

See references/communication-patterns.md for diagnostic frameworks:

  • Speaking time distribution
  • Participation balance
  • Listening quality levels
  • Question patterns
  • Conflict and disagreement
  • Meeting structure problems
  • Power dynamics
  • Feedback patterns

For Output Structure

See references/analysis-template.md for:

  • Complete template with all sections
  • Evidence standards
  • Language and tone guidelines
  • Quality checklist

Output Location

Save analysis to: 2-Areas/Career-Development/Communication/[YYYY-MM-DD] [Descriptive title].md

Link to source transcripts using wiki links: [[YYYY-MM-DD Meeting Name Transcription]]

Common Triggers

This skill activates when user says:

  • "Analyze my communication in this meeting"
  • "Review my communication patterns from this meeting"
  • "How did I come across in this transcript?"
  • "Give me communication feedback on this meeting"
  • "Analyze [Name]'s communication style"
  • "What are my communication strengths and weaknesses?"

Example Analysis Flow

User: "Analyze my communication in the strategy meeting"

1. Clarify if needed: "I'll analyze from your (Karol's) perspective. Is that correct?"
2. Read transcript file
3. Apply TA framework to identify ego states and transactions
4. Diagnose communication patterns using pattern diagnostics
5. Extract specific quotes with timestamps as evidence
6. Generate structured analysis following template
7. Provide balanced feedback (strengths + development)
8. Offer specific, actionable recommendations
9. Save to Career-Development/Communication folder

Quality Standards

Analysis should be:

  • Evidence-based: Every claim supported by quotes + timestamps
  • Comprehensive: Covers ego states, transactions, patterns, and recommendations
  • Balanced: Acknowledges strengths while identifying development areas
  • Actionable: Recommendations are specific and implementable
  • Professional: Descriptive, not judgmental; tactful yet direct
  • Culturally appropriate: Preserves Polish diacritics, respects professional norms

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.