Carrier Relationship Management
sickn33/agentic-awesome-skills
Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships.
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.
MITAuto-check passed
Install Relationship Check In
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-in --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/relationship-check-in .claude/skills/relationship-check-in && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .claude/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-inType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-in --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/relationship-check-in .agents/skills/relationship-check-in && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .agents/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-in --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/relationship-check-in .cursor/skills/relationship-check-in && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .cursor/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/relationship-check-in--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-in --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/relationship-check-in .gemini/skills/relationship-check-in && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .gemini/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-inInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/relationship-check-in .github/skills/relationship-check-in && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .github/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills relationship-check-in --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/relationship-check-in .opencode/skills/relationship-check-in && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "relationship-check-in" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/relationship-check-in into .opencode/skills/relationship-check-in/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "relationship-check-in", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
relationship-check-in- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 572 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 6 steps: Open with appreciation. Start by naming… → Set safety ground rules. No blame or… → Move through the structure. What's… → …
- Asked how to check in with my partner
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Safe, Structured,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Relationship Check In is an agent skill from mohitagw15856/pm-claude-skills. 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…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked how to check in with my partner
- We need to talk about our relationship
- Set up a relationship check-in
- Improve communication with my partner
Example prompts
- “how are we doing”
- “/relationship-check-in”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Open with appreciation. Start by naming what you value and what's going well — it sets a collaborative, non-threatening tone.
- Set safety ground rules. No blame or scorekeeping, listen to understand not to rebut, one issue at a time, and take breaks if it heats up.
- Move through the structure. What's working → what needs attention → each person's needs and specific asks. Structure prevents it becoming…
- Use prompts to go deeper. Gentle questions surface connection, stress, intimacy, chores/fairness, and future — past the reflexive "we're…
- Keep it regular and light. A short check-in often (weekly/monthly) catches things early far better than a rare, loaded Big Talk.
- Know when it's bigger. If the same issue keeps recurring, or trust/serious conflict surfaces, name that a check-in isn't enough — consider…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Relationship Check In loads about 1.1k tokens when it runs. Until then it costs about 154 tokens; SKILL.md has 572 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 572 words, ~1,147 tokens.
Download SKILL.mdSave it as
.claude/skills/relationship-check-in/SKILL.md (or your agent's skills folder).- name
- relationship-check-in
- description
- 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.
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 your mind — anything you want the check-in to make space for
- Both temperaments — is your partner open to this, or conflict-avoidant
- History — do you already talk openly, or is this new territory
Framework: Safe, Structured, Regular
- Open with appreciation. Start by naming what you value and what's going well — it sets a collaborative, non-threatening tone.
- Set safety ground rules. No blame or scorekeeping, listen to understand not to rebut, one issue at a time, and take breaks if it heats up.
- Move through the structure. What's working → what needs attention → each person's needs and specific asks. Structure prevents it becoming a vague gripe session.
- Use prompts to go deeper. Gentle questions surface connection, stress, intimacy, chores/fairness, and future — past the reflexive "we're fine."
- Keep it regular and light. A short check-in often (weekly/monthly) catches things early far better than a rare, loaded Big Talk.
- Know when it's bigger. If the same issue keeps recurring, or trust/serious conflict surfaces, name that a check-in isn't enough — consider a counselor.
Show full SKILL.md (221 more words)Show less
Output Format
Relationship check-in: [proactive / something's off]
Ground rules: no blame/scorekeeping · listen to understand · one topic · pause if heated.
The structure
- Appreciations: [what we each value / what's going well].
- What's working: […].
- What needs attention: [gently, one at a time].
- Needs & asks: [each person's specific request].
Prompts to go deeper: [connection · stress · intimacy · fairness/chores · future]. Cadence: [regular + short] in a [low-key setting]. Bigger than a check-in? [recurring issue / trust / serious conflict → consider a counselor].
Quality Checks
- Opens with appreciation to set a safe tone
- Includes ground rules against blame/scorekeeping
- Follows a structure (working → attention → needs/asks)
- Provides prompts that get past "we're fine"
- Recommends a regular, light cadence
- Flags when an issue needs more than a check-in
Anti-Patterns
- A grievance dump disguised as a check-in.
- Scorekeeping and blame that make it unsafe.
- Only doing it in crisis — rare, loaded Big Talks.
- Staying at "we're fine" with no deeper prompts.
- Treating a serious issue (trust, recurring conflict) as check-in material.
Example Trigger Phrases
- "How do my partner and I do a relationship check-in?"
- "We need to talk about us but I don't want it to become a fight."
- "Set up a regular way to check in on our relationship."
- "Questions to ask my partner about how we're doing."
- "Something feels off with us — how do I bring it up calmly?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/relationship-check-in of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Relationship Check In next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Relationship Check In this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Carrier Relationship Managementsickn33/agentic-awesome-skills | 47k | 2 repos | ~5.9k | Automated safety check: Pass | MIT | |
| Carrier Relationship Managementaffaan-m/ECC | 277k | 5 repos | ~5.9k | Automated safety check: Pass | Apache-2.0 | |
| Carrier Relationship Managementaffaan-m/ECC | 277k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Carrier Relationship Managementaffaan-m/ECC | 276k | — | ~700 | Automated safety check: Pass | Apache-2.0 | |
| Partner and Affiliate Programstech-leads-club/agent-skills | 7k | — | ~4k | Automated safety check: Pass | Custom licence |
Similar skills
Carrier Relationship Management
affaan-m/ECC
Supports freight managers in sourcing and vetting carriers, running RFPs, negotiating rates, building routing guides and scoring carrier performance.
Carrier Relationship Management
affaan-m/ECC
用于管理承运商组合、协商运费、跟踪承运商绩效、分配货运以及维护战略承运商关系的编码专业知识。基于拥有15年以上经验的运输经理提供的信息。包括记分卡框架、RFP流程、市场情报和合规性审查。适用于管理承运商、协商费率、评估承运商绩效或制定货运策略时使用。
Carrier Relationship Management
affaan-m/ECC
キャリアポートフォリオの管理、運賃交渉、キャリアパフォーマンスの追跡、貨物割り当て、戦略的なキャリア関係の維持のための成文化された専門知識。15年以上の経験を持つ輸送マネージャーに情報。スコアカーディングフレームワーク、RFPプロセス、市場情報、コンプライアンス調査を含みます。キャリアの管理、料金交渉、キャリアパフォーマンスの評価、または運賃戦略の構築を行うときに使用します。
Partner and Affiliate Programs
tech-leads-club/agent-skills
Designs partner, affiliate and integration programs, from recruiting the first partners to tuning commissions, for founders and go-to-market leads.
Ljg Relationship
lijigang/ljg-skills
Relationship analyst combining structural diagnostics (5-layer framework) with psychoanalytic depth (transference, unconscious patterns, resistance).
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Relationship Check In
What does Relationship Check In 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. Relationship Check In is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Relationship Check In?
Relationship Check In fits situations like: asked how to check in with my partner; we need to talk about our relationship; set up a relationship check-in; improve communication with my partner.
How do I install Relationship Check In in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a claude-code`. Or copy the skill folder (skills/relationship-check-in in mohitagw15856/pm-claude-skills) into .claude/skills/relationship-check-in in your project. Claude Code loads it when a task matches its description.
How do I install Relationship Check In in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a codex`. Or copy the skill folder (skills/relationship-check-in in mohitagw15856/pm-claude-skills) into .agents/skills/relationship-check-in in your project. Codex loads it when a task matches its description.
Can I use Relationship Check In in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill relationship-check-in -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/relationship-check-in, .gemini/skills/relationship-check-in, .github/skills/relationship-check-in and .opencode/skills/relationship-check-in in your project.
What does Relationship Check In need to run?
SKILL.md names no scripts, command-line tools or credentials: Relationship Check In is instructions for the agent only.
Does Relationship Check In access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Relationship Check In safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Relationship Check In use?
Relationship Check In is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Relationship Check In use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Relationship Check In?
Skills that share tags, products or a category with Relationship Check In: Carrier Relationship Management (sickn33/agentic-awesome-skills, 47k stars), Carrier Relationship Management (affaan-m/ECC, 277k stars), Carrier Relationship Management (affaan-m/ECC, 277k stars) and Carrier Relationship Management (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Relationship Check In?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.