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 Speculative Approach

ASecurity

Plans a speculative application email with a named recipient check, points for the subject line, opening, fit to their work with sources, the ask and your availability, and a follow-up date. Use for "run gnet-speculative-approach", "speculative application", "speculative email", "how to ask for a job that is not advertised", "cold email an employer", "email a company that is not hiring", "unadvertised graduate jobs", "who do I send my CV to", part of the Claude Graduate Networking Guide Pack ...

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-speculative-approach --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gnet Speculative Approach?

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

Security grade badge for Gnet Speculative Approach
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-gnet-speculative-approach/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-gnet-speculative-approach)

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-speculative-approach
description: Plans a speculative application email with a named recipient check, points for the subject line, opening, fit to their work with sources, the ask and your availability, and a follow-up date. Use for "run gnet-speculative-approach", "speculative application", "speculative email", "how to ask for a job that is not advertised", "cold email an employer", "email a company that is not hiring", "unadvertised graduate jobs", "who do I send my CV to", part of the Claude Graduate Networking Guide Pack by Polar Bear.
---

# Speculative Application Email

## When To Use
You want to work somewhere that is not advertising. This plans one speculative email to one named person: who it goes to, the points for each part, and when to follow up. You write it.

## When Not To Use
If the employer has an open vacancy, apply through its process instead. If you want advice from someone you know rather than work, use Message Points. If you cannot find a named person, stop here and run Alumni Search Plan or Employer Research Brief first.

## Inputs
- The employer and why you want to work there, with sources (an Employer Research Brief is ideal)
- The named recipient: their name and role, and the public source where you found them
- Your CV, and the kind of work and dates you are available for
If you have none of this, I start from the employer's name and your CV, and mark the output as a first draft with the recipient left open.

## Approach
The speculative application structure and follow-up from the Prospects guide (Jun 2025): a clear subject line, the recipient's name, a brief introduction and purpose, your skills matched to their goals, a closing that asks to discuss, a professional sign-off, and one follow-up after one to two weeks. UK university careers guidance adds: only approach a named person. The failure it prevents: "Dear Sir or Madam" to a generic inbox, a CV attached, and no follow-up, so nobody owns a reply.

## Workflow
1. Ask at most three questions: what work you are asking about, when you could start, and whether you want to attach your CV.
2. Named recipient check. The recipient must be a real person in a relevant role, found in a public source you name. If there is none, I stop and point you to Alumni Search Plan or Employer Research Brief.
3. Points per part. Subject line (what you are asking, plainly). Opening (who you are and why you are writing to them). Fit (two or three skills from your CV matched to their work, each with a source). The ask (a conversation about [work], not "any job"). Availability and sign-off.
4. Timing: avoid peak holidays when the inbox piles up, as the Prospects guide advises; you pick the send date.
5. Set one follow-up date, one to two weeks after sending. One follow-up only.
6. You write the email. Your CV goes only if you choose; I never add experience it does not show. Claude Docs (beta) is optional if you want the CV and email side by side.

## Output Format
```markdown
# Speculative Application Email Plan
Employer: [employer] · Recipient: [name], [role] (source: [public source, date])
## Recipient check
| Real named person | Relevant role | Public source | Result |
|---|---|---|---|
| [yes / no] | [yes / no] | [source] | [go / stop and find one] |
## Points per part
| Part | Your point | Source |
|---|---|---|
| Subject line | [what you are asking] | [none needed] |
| Opening | [who you are, why them] | [your notes] |
| Fit to their work | [skill matched to their goal] | [CV line; public source, date] |
| The ask | [a conversation about [work]] | [brief] |
| Availability and sign-off | [dates, CV attached or not] | [you] |
## Follow-up
Send date: [date] · Follow-up date: [one to two weeks later] · Then: [log as closed if no reply]
## Decision
[You write the email and send it to [name] by [date], and decide whether to attach your CV.]
```

## Done When
- A real named recipient with a public source is recorded, or the plan stops at the check
- Every part has a point, and every fit point has a source
- One follow-up date sits one to two weeks after the send date
- No ready-to-send email is written

## Quality Bar
- One employer, one person per email; never the same email to a list
- Fit points match their goals, not a list of your modules
- Recipient details come from public sources only, never a guessed email address
- No promises about outcomes; a reply is never assumed
- You write and send the email to one named person; nothing about you is invented.

## Next
Run gnet-grammar-check (Grammar Check) to clean the email you wrote.

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