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 About Section

ASecurity

Drafts your LinkedIn About Section in one or two short paragraphs in your voice (what you study or did, what you are good at with one example, what you want next, how to reach you) plus a claim map tying every claim to an evidence row. Use for "run glink-about-section", "write my LinkedIn about section", "LinkedIn summary for a graduate", "fix my about section", "about section without buzzwords", "what to write in LinkedIn about as a student", "my about box is empty", part of the Claude for L...

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 glink-about-section --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Glink About Section?

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

Security grade badge for Glink About Section
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/polar-bear-org-glink-about-section/badge)](https://www.skillsdirectory.com/skills/polar-bear-org-glink-about-section)

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-about-section
description: Drafts your LinkedIn About Section in one or two short paragraphs in your voice (what you study or did, what you are good at with one example, what you want next, how to reach you) plus a claim map tying every claim to an evidence row. Use for "run glink-about-section", "write my LinkedIn about section", "LinkedIn summary for a graduate", "fix my about section", "about section without buzzwords", "what to write in LinkedIn about as a student", "my about box is empty", part of the Claude for LinkedIn Networking for Recent Graduates Pack by Polar Bear.
---

# LinkedIn About Section

## When To Use
The About box is empty, or full of "passionate, driven, motivated" that could belong to anyone. This skill answers: what do I say about myself in two paragraphs that sounds like me and that I could defend in an interview?

## When Not To Use
If you have no evidence rows yet, run Experience Inventory first; an About section written from nothing fills itself with adjectives. For per-role detail, run Experience Entries; About is not a list of every job.

## Inputs
- Your Experience Inventory and Target Role Brief
- Your Personal Voice Guide, or three short samples of your own writing
- Your current About text, if any, and what contact route you want public
If you have none of this, I start from your degree, one thing you did and the role you want, and mark the output as a first draft.

## Approach
LinkedIn Help (Create a good LinkedIn profile) suggests an About of one or two paragraphs on your motivation and skills. UK careers-service advice adds a simple test: no buzzword without the evidence behind it. The judgment is replacing every adjective about you with the example that shows it. The failure it prevents: a recruiter reads "hardworking team player with excellent communication skills" for the tenth time today and scrolls on.

## Workflow
1. Ask at most three questions: which target role leads, which single example best shows what you are good at, and whether you want an email or "message me here" as the contact line.
2. Write four moves in order: what you study or did; what you are good at, with one concrete example from a row; what you want next (from the brief); how to reach you (only what you choose to make public).
3. Run the buzzword test: each adjective about you (passionate, hardworking, driven) is replaced by the example that shows it, or cut.
4. Match your voice guide: its sentence length, its contractions or not, its UK spellings. First person. One or two paragraphs; bullets only if you prefer them.
5. Build the claim map: each claim and its row ID. A claim with no row becomes `[gap: no evidence yet]` or comes out.
6. Give one version and one alternative opening line only, so you edit rather than choose between five drafts.

## Output Format
```markdown
# LinkedIn About Section
## Draft
[Paragraph 1: what I study or did, and what I am good at, with one example]
[Paragraph 2: what I want next, and how to reach me]
## Alternative opening line
[one line]
## Claim map
| Claim | Evidence row | Status |
|---|---|---|
| [claim] | [row ID] | [shown / gap] |
## Buzzwords removed
- [word] : [replaced by example / cut]
## Decision
You rewrite the draft in your own words, decide what contact detail goes public and paste it into LinkedIn yourself, this week.
```

## Done When
- Four moves present, in order, in one or two paragraphs
- Every claim appears in the claim map with a row ID
- No adjective about you survives without its example
- The contact line holds only what you chose to share

## Quality Bar
- Sounds like your voice samples, not a cover letter
- One example, told specifically, beats three named skills
- No contact detail, location or personal data added by default
- Does not repeat the headline word for word or list every role
- No adjective about you without the example that shows it; you paste it yourself.

## Next
Run glink-experience-entries (Experience Entries) to write each role as evidence.

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