AI Skill Report Card

Analyzing Complex Relationship Dynamics

B+78·May 7, 2026·Source: Web
14 / 15

When presented with relationship data, immediately identify:

  1. Core relational frame - What type of dynamic is this actually?
  2. Structural question - What needs definition/containment vs. what's already established?
  3. Evidence vs. assumption - What's observable vs. what's projection/script?
Recommendation
Add more concrete input/output examples showing different types of relationship ecosystems (polyamorous, solo-poly, relationship anarchy) to demonstrate range
15 / 15

Initial Assessment:

  • Identify the established relational ecosystem and timeline
  • Determine if this is about structure/containment or emotional processing
  • Separate multiple relational threads (don't collapse distinct dynamics)
  • Note any recent material changes to the analysis

Evidence Evaluation:

  • Catalog observable behaviors and corroborating data
  • Identify whose perspective/bias is informing each data point
  • Distinguish between emotional awareness and structural action
  • Note what ambiguity exists and who may be preserving it

Analysis Output:

  • Address the actual structural question being asked
  • Separate facts, inference, uncertainty, and speculation
  • Focus on containment, timing, capacity, and material constraints
  • Avoid defaulting to generic relationship advice or therapy scripts
Recommendation
Include a brief template or framework for documenting relational structure vs. emotional processing distinctions
18 / 20

Example 1: Input: "He keeps saying he needs to 'figure things out' but won't define what that means or when." Output: This preserves maximum ambiguity while appearing to promise future clarity. The structural question is whether you want to set a timeline for definition or accept indefinite ambiguity as the actual answer. His capacity for structural clarity appears limited, but the emotional bond remains observable.

Example 2: Input: "She said he's different with me than he was with her, more emotionally open." Output: This external corroboration strengthens the premise that the dynamic is distinct rather than projected. It shifts analysis from 'is this real?' to 'can emotional awareness translate into structural action given his demonstrated capacity limits?'

Recommendation
Streamline the Common Pitfalls section - some items could be combined or made more actionable as positive guidance
  • Maintain the established frame - Don't re-litigate whether bonds exist unless explicitly asked
  • Prioritize structure over feelings - Focus on containment, definition, and observable action
  • Use the person's language - Their terminology is often more accurate than generic relationship vocab
  • Separate distinct dynamics - Don't collapse multiple relationships into single narratives
  • Center the analyst - They are the authority on their own relational ecosystem
  • Applying relationship escalator assumptions to non-escalator dynamics
  • Offering communication scripts instead of structural analysis
  • Pathologizing clear perception of relational reality
  • Defaulting to "be careful" or "protect yourself" framing
  • Treating established long-term bonds as new crushes or fantasy
  • Collapsing separate household/property issues with relational questions
  • Re-litigating the existence of observable dynamics
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
15/15
Examples
18/20
Completeness
18/20
Format
15/15
Conciseness
13/15