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 Practice Conversation

ASecurity

Runs a Practice Conversation where Claude plays a stand-in for the contact from your prep sheet, so you rehearse the opening, questions and close, then gives Practice Conversation Notes on what went well and what to change. Use for "run gnet-practice-conversation", "rehearse my coffee chat", "practise an informational interview", "role-play the call", "I am nervous about my first chat", "mock networking call", "pretend to be the alumnus", "practise ending on time", part of the Claude Graduate...

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-practice-conversation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gnet Practice Conversation?

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

Security grade badge for Gnet Practice Conversation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-gnet-practice-conversation/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-gnet-practice-conversation)

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-practice-conversation
description: Runs a Practice Conversation where Claude plays a stand-in for the contact from your prep sheet, so you rehearse the opening, questions and close, then gives Practice Conversation Notes on what went well and what to change. Use for "run gnet-practice-conversation", "rehearse my coffee chat", "practise an informational interview", "role-play the call", "I am nervous about my first chat", "mock networking call", "pretend to be the alumnus", "practise ending on time", part of the Claude Graduate Networking Guide Pack by Polar Bear.
---

# Practice Conversation

## When To Use
You are nervous about your first informational interview. You have a prep sheet and questions, and you want to say them out loud once, to someone who answers back, before the real call.

## When Not To Use
If your opening line is the problem, fix it first with Elevator Pitch. If you have no prep sheet yet, run Coffee Chat Prep Sheet; rehearsing without a plan only practises rambling. Never use this during the real call.

## Inputs
- Your Coffee Chat Prep Sheet and your question list.
- The contact's stage (recent graduate, manager or senior, recruiter or employer).
- One difficulty you want to practise: short answers, they run over time, or they ask "so what do you want?".
If you have none of this, I start from their role title and your one goal and mark the output as a first draft.

## Approach
This is rehearsal role-play, the same idea as a careers service mock conversation, described generically. The judgment is that Claude plays a typical person at that stage, not the real contact: it uses only the sourced facts on your sheet and never invents opinions to put in their mouth. The failure it prevents is the first question coming out as a four-sentence apology, which is far better heard in practice than on the call.

## Workflow
1. Ask up to three questions: the contact's stage, the difficulty you want, and whether you want feedback after each round or only at the end.
2. Set the stand-in: a generic person at that stage, built only from the sourced facts on your sheet. I say clearly that it is a stand-in, not the real person.
3. Round one, opening: you greet, thank them for their time and give your 10-second pitch. I respond as the stand-in, including your chosen difficulty.
4. Round two, questions: you ask your five. I answer briefly and plausibly for the stage, and never claim the real person holds those views.
5. Round three, close: I signal the time is nearly up. You end on time and ask who else to talk to.
6. Feedback on your practice only: what went well, what to change, one sharper version of your weakest question. No scores or ratings.
7. End with the reminder: practice only; hold the real call yourself, without Claude.

## Output Format
```markdown
# Practice Conversation Notes
**Stand-in for:** [stage] at [employer] (not the real person) · **Difficulty:** [chosen]
## Round by round
| Round | What went well | What to change |
|---|---|---|
| Opening and pitch | [note] | [note] |
| Questions | [note] | [note] |
| Close on time | [note] | [note] |
## Sharper question
[Your original] -> [a shorter, more open version]
## Reminder
Practice only. You hold the real conversation yourself.
## Decision
[You decide whether to change your pitch or questions, and update the prep sheet before the call.]
```

## Done When
- All three rounds ran, including the close at the time limit.
- Feedback names specific lines you said, not general advice.
- The notes say the stand-in is not the real person and end with the reminder.

## Quality Bar
- The stand-in never gets invented opinions, details or quotes attributed to the real contact.
- Feedback is on your practice, never a grade of you.
- One round at a time; you can stop or repeat any round.
- Keep it short enough to run the night before.
- Practice only: you hold the real conversation yourself and Claude is never used during it.

## Next
Run gnet-chat-debrief (Chat Debrief) straight after the real call, to capture what you learned before it fades.

## 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', ...

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