Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Gnet Close The Loop

ASecurity

Gives you Close the Loop Note Points for telling the person who introduced or referred you what happened, covering the call, the advice and the outcome so far, a thank-you and one thing to share back. Use for "run gnet-close-the-loop", "update the person who introduced me", "tell my referrer what happened", "follow up with someone who helped me", "thank you for the introduction update", "close the loop with a contact", "I never told them how it went", part of the Claude Graduate Networking Gu...

2 stars
0 votes
0 copies
0 views
Added 10/5/2026
ai-agentsgo

Works with

cli

Security Analysis

A100/100

Scanned 10/5/2026

$npx -y skills add polar-bear-org/claude-skills --skill gnet-close-the-loop --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gnet Close The Loop?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Gnet Close The Loop
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-gnet-close-the-loop/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-gnet-close-the-loop)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: gnet-close-the-loop
description: Gives you Close the Loop Note Points for telling the person who introduced or referred you what happened, covering the call, the advice and the outcome so far, a thank-you and one thing to share back. Use for "run gnet-close-the-loop", "update the person who introduced me", "tell my referrer what happened", "follow up with someone who helped me", "thank you for the introduction update", "close the loop with a contact", "I never told them how it went", part of the Claude Graduate Networking Guide Pack by Polar Bear.
---

# Close the Loop Note

## When To Use
Someone introduced you or referred you, the conversation happened or the application went in, and they have heard nothing since. They opened a door and are now wondering whether it was worth it. This gives you points for telling them what happened, thanking them and sharing something back.

## When Not To Use
If you want to thank the person you actually spoke to, use Thank-You Note: that is a different message to a different person. If nothing has happened yet because the introduction is still pending, wait; a nudge is Follow-Up Nudge.

## Inputs
- Who helped and what they did (an introduction, a referral, a helper brief passed on)
- What happened since: the call, the advice, the application, any outcome
- Your Chat Debrief notes, if you have them
If you have none of this, I start from who helped and what happened, in a sentence each, and mark the output as a first draft.

## Approach
UK university careers guidance says to thank people and share outcomes with those who helped. The judgment is that an introducer's only reward is knowing it went somewhere. The failure it prevents: the referrer hearing from the hiring team, months later, that you got the job, and wondering why you never said. A short, honest note, even "no news yet", keeps the door open.

## Workflow
1. Ask up to three questions: who helped and how, what happened, and what you are doing next.
2. Draft the point on what happened: the call was held, the advice you got, the outcome so far. State it as it is, including "no news yet" or "I did not get it".
3. Draft the point on thanks: name the specific thing they did and why it mattered to you.
4. Draft the point on something to share back: an article, a link, a result of their advice, or an offer to help someone they know later.
5. Check what you pass on about the third person: their advice in general terms is fine; anything they said in confidence or about their own life stays out.
6. Check the points: 2 or 3 points, each 3 or 4 sentences, short, no new ask unless it is tiny. You write the note and send it.

## Output Format
```markdown
# Close the Loop Note Points
**To:** [helper's first name] · **What they did:** [introduction / referral / passed on brief] · **Date:** [date]
## Points to make
1. **What happened:** [3 or 4 sentences: call held, advice received, outcome so far, stated as it is]
2. **Thanks:** [3 or 4 sentences naming what they did]
3. **Something back:** [3 or 4 sentences: a link, a result, an offer]
## Left out on purpose
- [anything private about the person you spoke to]
## Decision
You decide the wording and send it by [date]; you log it in your Networking Log the same day.
```

## Done When
- The outcome is stated as it really is, including "no news yet"
- Thanks name the specific thing the helper did
- Nothing private about the third person is in the points
- At most one tiny ask, or none

## Quality Bar
- Points, not a finished message; if asked to write it, offer Grammar Check on your draft instead
- Never inflate an outcome to make the helper feel better
- Never pass on anything said in confidence
- Short beats complete; the helper wants the headline
- You report what really happened in your own words.

## Next
Run gnet-networking-log (Networking Log) to record it.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).

Attribution

polar-bear-orgpolar-bear-org
View sourceSee grades on GitHubMore from polar-bear-org →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →