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

Glink Learning Post

ASecurity

Drafts a Learning Post on one thing you learned from a module, an employer talk, a careers fair, an insight day or a course, in What? So what? Now what? order, with the first line inside the moment, 80 to 200 words in your voice and tags only with permission. Use for "run glink-learning-post", "post about the employer talk", "I finished a course and want to post", "what I learned at the careers fair", "write up my insight day", "post about a module", "something real about an event", part of t...

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

Works with

cli

Security Analysis

A100/100

Scanned 10/5/2026

$npx -y skills add polar-bear-org/claude-skills --skill glink-learning-post --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Glink Learning Post?

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

Security grade badge for Glink Learning Post
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-glink-learning-post/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-glink-learning-post)

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: glink-learning-post
description: Drafts a Learning Post on one thing you learned from a module, an employer talk, a careers fair, an insight day or a course, in What? So what? Now what? order, with the first line inside the moment, 80 to 200 words in your voice and tags only with permission. Use for "run glink-learning-post", "post about the employer talk", "I finished a course and want to post", "what I learned at the careers fair", "write up my insight day", "post about a module", "something real about an event", part of the Claude for LinkedIn Networking for Recent Graduates Pack by Polar Bear.
---

# Learning Post

## When To Use
You went to an employer talk, an insight day or a careers fair, or finished a course, and you want to say something real about it instead of "great to hear from [employer] today". This skill answers: what did I actually take away, and how do I say it in under 200 words without sounding like a press release?

## When Not To Use
If the post is about your own project, Project Post fits better; if it is news (an offer, a placement, a result), use Milestone Post. If you cannot yet name the one thing you learned, go back to Post Ideas Bank; a learning post with an invented "so what" reads as performance.

## Inputs
- What happened: the event, course or module, and when
- The one thing you learned, in your own rough words
- What you will do with it, even if small
- Optional: your Personal Voice Guide and the matching Post Ideas Bank row
If you have none of this, I start from a two-line voice note transcript of you describing the event and mark the post as a first draft.

## Approach
Rolfe's reflective model asks three questions in order, What? So what? Now what?, as set out in the University of Hull library guide to reflective writing. It suits a post because it forces a real moment first and a next step last. LinkedIn's help pages give posts up to 3,000 characters at the time of writing (check the counter); this post uses a fraction of that. The failure it prevents: a speaker "quoted" with words they never said, tagged without asking.

## Workflow
1. Ask at most three questions: what happened (one concrete moment, not the agenda), the one thing you learned, and what you will do differently because of it.
2. What?: open inside the moment, a specific thing seen or heard ("The second slide was a rota, not a strategy"). No "thrilled to", no "I recently attended". One or two sentences.
3. So what?: what it changed in your thinking, in your words. If it only confirmed what you knew, say that honestly; that is still a post.
4. Now what?: one action you will take, real and small (a module choice, a question for your next interview, a book you will finish). No promise you will not keep.
5. Speakers and people: paraphrase without quotation marks unless you are sure of the exact words. Tag a person or employer only if they said yes. Strip anything from an insight day or placement that was shared as internal.
6. Fit to 80 to 200 words, apply your voice guide, and strip the AI tells (negation frame, three-item lists, empty verbs, summary ending, rhetorical question, emoji bullets). Count the words.

## Output Format
```markdown
# Learning Post Draft
Source: [event / course / module] · Date: [date] · Idea row: [row]
## Post
[What? First line inside the moment]
[So what? What it changed in your thinking]
[Now what? The one thing you will do]
## Checks
| Check | Status |
|---|---|
| Word count (80 to 200) | [count] |
| Quotes exact or paraphrased | [exact, sure / paraphrased, no quotation marks] |
| Tags with permission | [names, yes recorded / none] |
| Confidential content removed | [yes / question for: person] |
## Decision
You decide by [date] whether to post it, after Voice Check; you post it yourself.
```

## Done When
- The first line sits inside a concrete moment, not an announcement.
- What? So what? Now what? appear in that order, each in your words.
- The post is 80 to 200 words.
- Every quote is exact or paraphrased without quotation marks, and every tag has a recorded yes.

## Quality Bar
- One thing learned per post; a second insight becomes a second idea in the bank.
- No flattery of the employer or speaker; the learning is the subject, not them.
- No hashtags you would not use yourself, and no "what do you think?" ending.
- No confidential slides, figures or names from insight days or placements.
- You write and post it yourself; no quote or tag without the person's yes.

## Next
Run glink-voice-check (Voice Check) to check the draft still sounds like you and says only what is true.

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