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

Net Introduction Ask

ASecurity

Prepares your Introduction Ask, when to ask, one specific introduction tied to your brief, the easy way to say no, what you offer in return and what not to say, as prompts you put in your own words. Use for "run net-introduction-ask", "how do I ask for an introduction", "asking for introductions feels needy", "who do you know who", "ask a client for an introduction", "let me know if you hear of anyone never works", part of the Claude for Networking on LinkedIn Pack by Polar Bear.

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 net-introduction-ask --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Net Introduction Ask?

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

Security grade badge for Net Introduction Ask
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-net-introduction-ask/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-net-introduction-ask)

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: net-introduction-ask
description: Prepares your Introduction Ask, when to ask, one specific introduction tied to your brief, the easy way to say no, what you offer in return and what not to say, as prompts you put in your own words. Use for "run net-introduction-ask", "how do I ask for an introduction", "asking for introductions feels needy", "who do you know who", "ask a client for an introduction", "let me know if you hear of anyone never works", part of the Claude for Networking on LinkedIn Pack by Polar Bear.
---

# Introduction Ask

## When To Use
Asking for introductions feels needy, and "let me know if you hear of anyone" has never produced a single name. Use this when a client or contact has just had a good experience of your work and you want to ask for one introduction without making it awkward. It answers: what exactly do you ask for, when, and how do you make no an easy answer?

## When Not To Use
If someone has already said yes to introducing you, run the Forwardable Intro Blurb instead. If the relationship is strained, a project just went badly or you have not spoken in a long time, do not ask: run the Client Check-In or the Reason to Write Picker first.

## Inputs
- Your Networking Brief (who you help, what you want help with now, who you would like to meet)
- The person you want to ask, the moment (a good review, a thank-you, a delivered result) and your own notes on what they said
- Your Five-Minute Favor List, and any Client Relationship Map for this client
If you have none of this, I start from the brief's "who you would like to meet" field and mark the output as a first draft.

## Approach
Research from the Hinge Research Institute (S5 in resources) found that only a small share of people who recommend a firm do so because they were asked, and that people make introductions to help the buyer, not the vendor. So the vague ask is out; what is left is one specific introduction that clearly serves the person introduced, asked at the right moment (a practitioner practice, described generically). The failure it prevents: the end-of-call "if you hear of anyone", which costs the client nothing to agree to and produces nothing.

## Workflow
1. Ask three questions: who are you asking, what just happened between you, and what one introduction would help most right now?
2. Check the moment. Good: after a good review, a thank-you or a delivered result. Not now: after a bad week, a missed deadline, an open complaint or an unpaid invoice. If the moment is wrong, the output says "wait" and names what would make it right.
3. Build one specific ask from the brief: "Who do you know who [situation] and [role]?", or a named person the client mentioned themselves. Never "anyone". If you have two asks, pick one; the second waits for another time.
4. Write why it serves the person introduced: what they might gain from one conversation, from their side. If you cannot say it without mentioning your need, the ask is not ready.
5. Prompt the easy no: you write one line that makes declining comfortable ("no is a fine answer"). The ask must survive a no with the relationship intact.
6. Pick what you offer in return from your favor list, with no condition. No fee by default; a standing arrangement belongs in the Partner Agreement.
7. List what not to say: pressure, scarcity, "I need work", praise used to set up the ask, a follow-up chase if they do not come back with a name.

## Output Format
```markdown
# Introduction Ask
**Person asked:** [name] · **Moment:** [what just happened] · **Ready:** [yes / wait until [ ]]
## The ask
- Who you would like to meet: [situation] and [role], from your brief
- Your words: [your words: "Who do you know who..."]
- Why it serves them: [from their side, in your words]
## The easy no
- [your words: one line that makes declining comfortable]
## What you offer
- [favor from your list, no condition]
## What not to say
- [pressure / scarcity / "I need work" / praise as set-up / chasing]
## Decision
You decide whether to ask [name] and say it in your own words by [date]; if they say yes, prepare the Forwardable Intro Blurb.
```

## Done When
- There is exactly one ask, specific to a situation and role or a named person
- The moment check is done and says ready or wait
- The easy no and the give back are in your words
- Nothing in the output is a finished message to paste

## Quality Bar
- One introduction per ask; "anyone" never appears as the ask
- Why it serves the person introduced is written before anything about you
- Nothing assesses how likely the person is to introduce you; Claude never rates the person asked
- No fee is offered by default
- One specific ask, easy to decline, in your own words; you say or send it yourself.

## Next
Run net-forwardable-blurb (Forwardable Intro Blurb) to make the introduction easy once they say yes.

## 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 →