AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

interpreting-culture-index

Interprets Culture Index (CI) surveys, behavioral profiles, and personality assessment data. Supports individual profile interpretation, team composition analysis (gas/brake/glue), burnout detection, profile comparison, hiring profiles, manager coaching, interview transcript analysis for trait prediction, candidate debrief, onboarding planning, and conflict mediation. Accepts extracted JSON or PDF input via OpenCV extraction script. Use when the user shares a Culture Index PDF or JSON profile, asks what someone's CI traits mean, compares Culture Index profiles across a team or against a hiring profile, or asks about burnout risk from Survey-versus-Job gaps.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--interpreting-culture-index at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 43

references/conversation-starters.md

Conversation starters and engagement strategies based on Culture Index traits. Use these to build rapport, deliver feedback effectively, and engage team members based on their profile.

<by_pattern>

What engages them:

  • Strategic discussions, big picture thinking
  • Future vision and possibilities
  • ROI and business impact
  • Being asked for their opinion

Good conversation starters:

  • "What do you think is the biggest opportunity we're missing?"
  • "If you could redesign this from scratch, what would you change?"
  • "What's your take on [strategic topic]?"
  • "Where do you see this going in 2-3 years?"

How to deliver feedback:

  • Focus on outcomes and impact, not process
  • Be direct and confident - don't hedge
  • Frame as investment in their success
  • Bullet points, not paragraphs

Topics to avoid:

  • Excessive detail about implementation
  • Step-by-step instructions
  • Past failures (they've moved on)
  • Lengthy consensus-building

What engages them:

  • Relationship building
  • Competitive challenges
  • Public recognition opportunities
  • Stories and narratives

Good conversation starters:

  • "How did you land that account?"
  • "What's your read on [person/client]?"
  • "Tell me about your biggest win this quarter"
  • "Who should I talk to about [topic]?"

How to deliver feedback:

  • Balance directness with relationship
  • Public praise, private criticism
  • Frame around their reputation and influence
  • Keep it brief - they'll want to talk

Topics to avoid:

  • Detailed process requirements
  • Solitary work expectations
  • Administrative tasks
  • Slow-moving, bureaucratic topics

What engages them:

  • Deep expertise discussions
  • Complex technical problems
  • Quality and precision topics
  • Learning opportunities

Good conversation starters:

  • "I'd like your expert opinion on [technical topic]"
  • "Can you walk me through how this works?"
  • "What do you think is the right way to approach this?"
  • "I'm trying to understand [complex topic] - can you help?"

How to deliver feedback:

  • Be specific and fact-based
  • Reference documentation or standards
  • Give them time to process
  • Private, not public
  • Written follow-up appreciated

Topics to avoid:

  • Forced small talk
  • Vague, unstructured discussions
  • Expecting quick verbal responses
  • Public attention or praise

<technical_expert label="Technical Expert (Low A, Low B, Low C, High D)">

What engages them:

  • Efficient, focused discussions
  • Clear problems with clear solutions
  • Quality and accuracy
  • Getting things done

Good conversation starters:

  • "I need your help solving [specific problem]"
  • "What's the correct way to do this?"
  • "Can you review this for accuracy?"
  • "Here's the situation - what's your take?"

How to deliver feedback:

  • Very direct and specific
  • Focus on the work, not the person
  • Provide clear standards to meet
  • Brief and efficient

Topics to avoid:

  • Extended social conversation
  • Vague or open-ended questions
  • Consensus-building meetings
  • Public recognition (uncomfortable)

</technical_expert>

What engages them:

  • Mastery and expertise
  • Consistent, reliable processes
  • Quality discussions
  • Predictable environments

Good conversation starters:

  • "You're the expert on this - what should I know?"
  • "What's the best practice for [specific task]?"
  • "I want to make sure we do this right"
  • "Can you help me understand the proper process?"

How to deliver feedback:

  • Frame as process improvement
  • Reference standards and best practices
  • One topic at a time
  • Allow time to process and respond

Topics to avoid:

  • Rapid-fire questions
  • Unstructured brainstorming
  • Public speaking or presentations
  • Frequent change of plans

What engages them:

  • Team and relationship discussions
  • Helping others succeed
  • Collaborative problem-solving
  • Stable, supportive environments

Good conversation starters:

  • "How's the team doing?"
  • "Who needs support right now?"
  • "What would make this easier for everyone?"
  • "How can I help you help the team?"

How to deliver feedback:

  • Gentle but clear
  • Acknowledge their contributions
  • Frame around team impact
  • Give time to adjust

Topics to avoid:

  • Aggressive confrontation
  • Demanding immediate decisions
  • Forcing them to take sides
  • Public criticism

What engages them:

  • Deep analytical discussions
  • Strategic thinking
  • Independent problem-solving
  • Time to think and process

Good conversation starters:

  • "What's your analysis of [complex situation]?"
  • "I'd value your perspective on this"
  • "If you had to choose a direction, what would it be?"
  • "What patterns are you seeing?"

How to deliver feedback:

  • Logical, fact-based
  • Allow processing time
  • Written communication works well
  • Respect their independence

Topics to avoid:

  • Forced team activities
  • Rapid decision demands
  • Excessive small talk
  • Public group discussions

</by_pattern>

<by_trait>

<high_a label="Engaging High A (Autonomous/Assertive)">

Do:

  • Ask for their opinion before sharing yours
  • Give outcomes, not instructions
  • Respect their time (be efficient)
  • Challenge them intellectually
  • Acknowledge their expertise

Don't:

  • Micromanage or over-explain
  • Expect consensus-building
  • Take too long to get to the point
  • Show hesitation or uncertainty
  • Dismiss their ideas without discussion

Feedback style:

  • Direct, confident, brief
  • Focus on ROI and impact
  • Their investment in success

</high_a>

<low_a label="Engaging Low A (Supportive/Collaborative)">

Do:

  • Include them in discussions
  • Acknowledge their contributions
  • Provide clear direction
  • Give specific praise
  • Allow time for input

Don't:

  • Put them on the spot for decisions
  • Expect aggressive initiative
  • Skip collaboration for speed
  • Interpret silence as agreement
  • Assume they'll speak up with concerns

Feedback style:

  • Specific, supportive
  • Private, not public
  • Clear expectations

</low_a>

<high_b label="Engaging High B (Social/Relational)">

Do:

  • Start with personal connection
  • Allow time for rapport
  • Include in group activities
  • Praise publicly
  • Ask about relationships and team

Don't:

  • Skip small talk
  • Isolate with solo work
  • Give criticism publicly
  • Expect brief, task-only interaction
  • Forget they process verbally

Feedback style:

  • Start with relationship
  • Verbal praise matters
  • Private for criticism

</high_b>

<low_b label="Engaging Low B (Reserved/Task-Focused)">

Do:

  • Get to the point
  • Respect their focus time
  • Use written communication
  • Give private recognition
  • Allow solo work time

Don't:

  • Force extended social interaction
  • Expect verbal processing
  • Praise publicly (uncomfortable)
  • Require constant meetings
  • Mistake quiet for disengagement

Feedback style:

  • Efficient, task-focused
  • Written is appreciated
  • Private, not public

</low_b>

<high_c label="Engaging High C (Patient/Steady)">

Do:

  • Send agendas in advance
  • One topic at a time
  • Give advance notice of changes
  • Respect their routines
  • Allow processing time

Don't:

  • Surprise them with changes
  • Rush decisions
  • Interrupt their focus time
  • Multi-topic meetings
  • Create unnecessary urgency

Feedback style:

  • Scheduled, predictable
  • Advance notice helpful
  • One issue at a time

</high_c>

<low_c label="Engaging Low C (Urgent/Fast-Paced)">

Do:

  • Put deadlines in subject lines
  • Keep them busy with variety
  • Accept their urgency
  • Use their energy productively
  • Be ready for interruptions

Don't:

  • Expect patient waiting
  • Give slow, drawn-out responses
  • Bore them with routine
  • Slow-walk decisions
  • Be surprised by multitasking

Feedback style:

  • Quick and direct
  • Deadlines motivate
  • Don't delay

</low_c>

<high_d label="Engaging High D (Detail/Precise)">

Do:

  • Be accurate and specific
  • Reference standards and process
  • Provide documentation
  • Acknowledge their precision
  • Build trust carefully

Don't:

  • Make it personal
  • Skip details that matter
  • Break commitments
  • Expect flexibility on quality
  • Give vague instructions

Feedback style:

  • Process improvement framing
  • Specific, documented
  • Don't break trust

</high_d>

<low_d label="Engaging Low D (Flexible/Big-Picture)">

Do:

  • Give creative problems
  • Provide options
  • Focus on outcomes
  • Accept 80% solutions
  • Allow flexibility

Don't:

  • Over-structure
  • Expect precise documentation
  • Hold grudges for missed details
  • Box them in with rules
  • Require perfection

Feedback style:

  • Focus on what matters
  • Pick your battles
  • Options over mandates

</low_d>

</by_trait>

<quick_reference>

| Pattern | Open With | Avoid | Feedback Style | |---------|-----------|-------|----------------| | Architect | "What's your vision..." | Detail-heavy | Direct, ROI-focused | | Rainmaker | "How did you..." | Solitary topics | Public praise, private critique | | Scholar | "Walk me through..." | Small talk | Written, specific | | Technical Expert | "I need help with..." | Open-ended | Direct, efficient | | Craftsman | "What's the right way..." | Rapid-fire | Process improvement | | Accommodator | "How's the team..." | Confrontation | Gentle, supportive | | Philosopher | "What's your analysis..." | Forced social | Logical, written |

</quick_reference>