Skip to content

ValentinNikolaev/agent-skills / agent-plugins/skills/linkedin-profile-optimizer

linkedin-profile-optimizer

Verified

Audit or rewrite LinkedIn profiles and role keywords from verified evidence; not CVs, letters, feed posts, or asset files.

references/section-playbook.md

View on GitHub
# Section playbook

| Surface | Inspect when supplied | Useful revision |
| --- | --- | --- |
| Photo | Recognizability, crop, image quality, intended audience | Give a concrete crop or replacement brief; do not infer age or professionalism from protected traits |
| Banner | Legibility, device crops, overlap with avatar, main idea | One evidence-backed theme; verify current dimensions before exporting |
| Headline | Searchable identity, specialism, clarity, support | Lead with the role family; add a distinctive evidenced contribution without filling a character quota |
| About | Opening, narrative, proof, readability, invitation | First person; enough context for a human or parser to understand contribution |
| Featured | Complementary proof, clear titles, access, relevance | Choose strong assets and a goal-specific next action |
| Experience | Dates, exact titles, scope, individual action, impact | Short readable role narrative or bullets; attach verified proof where supported |
| Skills | Relevant evidence, exact labels, role associations | Prioritize the strongest relevant capabilities and mark unverified taxonomy |
| Public URL | Accessibility, consistency, existing uses | Suggest a readable URL if useful; consider old links before changing it |
| Recommendations | Specificity, firsthand knowledge, relevant work | Suggest who could attest to a real contribution; do not invent endorsements |

An optional About scaffold is: current work, recurring problem, personal approach,
one proof story, complementary expertise, desired next work, invitation. Merge or
omit pieces that add no substance. Do not force seven paragraphs or repeat the
headline. A compact opening should make sense before expansion, but preview size
depends on the actual surface.

For technical Experience, explain a decision and its consequence when supported:
problem → personal action/decision → observed result → relevant technology.
An incident mitigation, safer release process, maintainable API, or explicit
tradeoff can demonstrate judgment without a numerical metric. Preserve an earlier
role's chronology when selectively shortening it; do not rewrite historical job
titles as the target title.

For external machine readability, use ordinary text, explicit role/project names,
clear dates, conventional technology names, and useful link labels. Avoid Unicode
styled alphabets and unexplained acronyms. Keep important proof in prose as well
as images. This improves accessibility and interpretability; it does not guarantee
that a recruiter AI can access, parse, rank, or shortlist the profile.

For each proposed skill, record its evidence, relevance, scope/recency, proposed
role association, exact observed picker label if any, and placement priority.
Do not add a technology after seeing it only in the target vacancy. A relevant
older skill need not be deleted solely because it was last used years ago.

For a recommendation request, identify a shared project, one or two contributions,
and the recipient's direct perspective. Invite them to use their own words and
correct the recollection. Keep examples as prompts for truthful recollection,
never as a fabricated finished testimonial. Follow the current personal voice.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall