Agent skill · Workflow & Productivity

relationship-check-in

Run a calm, regular relationship check-in with your partner — a structured 'how are we doing' conversation that catches small things before they become big ones. Use when asked how to check in with my partner, we need to talk about our relationship, set up a relationship check-in, or improve communication with my partner. Produces a simple check-in structure (appreciations, what's working, what needs attention, needs and asks), ground rules that keep it safe not combative, prompts to surface the real stuff, a cadence that fits you, and a note on when an issue is bigger than a check-in.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/relationship-check-in/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Relationship Check-In Most relationship problems aren't sudden — they're small unspoken things that pile up. A regular, low-drama check-in surfaces them early, in a format that feels like teamwork rather than a confrontation. This gives you a simple structure, ground rules that keep it safe, and prompts that get past "we're fine" to what's actually going on. ## What This Skill Produces - **A check-in structure** — appreciations first, then what's working, what needs attention, and each person's needs/asks - **Ground rules** — how to keep it safe: no blame, no scorekeeping, listen to understand, one topic at a time - **Surfacing prompts** — questions that get past "everything's fine" to the real stuff (connection, stress, intimacy, division of labor, future) - **A cadence** — how often to do it (regular and short beats rare and heavy) and a low-key setting - **A bigger-issue flag** — when something surfaced needs more than a check-in (recurring conflict, trust, or a counselor) ## Required Inputs Ask for these if not provided: - **The prompt** — proactive habit, or something specific feeling off - **Where you're at** — generally good, some tension, or a rough patch - **What's on yo

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Safe, Structured, Regular
  4. Output Format
  5. Relationship check-in: [proactive / something's off]
  6. Quality Checks
  7. Anti-Patterns
  8. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the relationship-check-in skill do?

Run a calm, regular relationship check-in with your partner — a structured 'how are we doing' conversation that catches small things before they become big ones. Use when asked how to check in with my partner, we need to talk about our relationship, set up a relationship check-in, or improve communication with my partner. Produces a simple check-in structure (appreciations, what's working, what needs attention, needs and asks), ground rules that keep it safe not combative, prompts to surface the real stuff, a cadence that fits you, and a note on when an issue is bigger than a check-in.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going