alirezarezvani/claude-skills / marketing/linkedin/skills/linkedin-profile
linkedin-profile
VerifiedUse when auditing or rewriting a LinkedIn profile (headline, About, experience, Featured). Scores the headline with headline_scorer.py, audits completeness with profile_completeness_auditor.py and drafts About with about_section_builder.py.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.7 KB |
| assets/example_profile.json | config | 1.5 KB |
| assets/profile_worksheet.md | markdown | 1.9 KB |
| references/headline_and_positioning.md | markdown | 5.6 KB |
| references/profile_architecture.md | markdown | 5.8 KB |
| scripts/about_section_builder.py | script | 12.5 KB |
| scripts/headline_scorer.py | script | 15.4 KB |
| scripts/profile_completeness_auditor.py | script | 13.9 KB |
assets/profile_worksheet.md
View on GitHub# Profile Worksheet
Fill this in before any rewriting. The auditor and the About builder both read from it.
---
## Presence
- [ ] Photo: face, well lit, recognisable at 48px? ______
- [ ] Banner: custom, or still the default gradient? ______
- [ ] Custom URL set? ______
- [ ] Contact info reachable? ______
- [ ] Open To / Services block set? ______
- [ ] Days since your last post: ______
## Headline (220 characters)
Current: ______________________________________________
- Who is it for (specifically enough to exclude someone)? ______
- What changes because of you? ______
- One piece of proof (number / ex-company / credential)? ______
- Which conventional role or skill term keeps it searchable? ______
First 60 characters — is the strongest segment there? ______
## About (fold at ~265-300 characters)
1. **Hook** — the tension your audience recognises, in their words:
2. **Audience** — who you are for:
3. **Proof** — two or three real results, with numbers:
4. **Approach** — how you work; the part that is yours, not your title's:
5. **CTA** — who should reach out, and what they get:
6. **Keywords** you want to be findable for (work them into real sentences, not a list):
## Current role
Title: ______
Rewrite each bullet as an outcome, not a duty:
| Duty (what it says now) | Outcome (what actually changed) |
|---|---|
| | |
| | |
## Featured
- What is pinned now? ______
- Last updated? ______
- What could a stranger evaluate in 60 seconds? ______
## Recommendations
- Received: ______
- Two people to ask, and the specific project to ask them about:
1. ______
2. ______
---
**Then run:**
```bash
python3 ../scripts/profile_completeness_auditor.py --input profile.json --output human
python3 ../scripts/headline_scorer.py --headline "..." --output human
python3 ../scripts/about_section_builder.py --input about.json --output human
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |