professional-profile

name

professional-profile

description

Create, revise, or audit a public professional profile such as LinkedIn, a developer portfolio, GitHub profile README, personal bio, headline, About section, experience entry, Featured section, or project case study. Use when positioning verified experience for target roles, improving recruiter scan quality, selecting proof artifacts, or aligning public career materials; do not use for ATS resume formatting or end-to-end job application strategy.

Professional Profile

Purpose

Make a candidate's public profile easy to find, understand, and trust by connecting a clear role direction to specific evidence rather than generic personal branding.

Inputs

• Target roles, seniority, industries, geography, and preferred working language.
• Verified experience, projects, education, skills, interests, and differentiators.
• Existing LinkedIn, portfolio, GitHub, bio, or profile content.
• Public proof artifacts: repositories, demos, case studies, papers, talks, certifications, or shipped work.

Scope Boundary

Use resume-and-ats for resume document structure and job-description tailoring. Use job-search-and-applications for role selection, outreach, application packages, and tracking. This skill may recommend profile edits but must not publish them or message people without explicit authorization.

Process

1. Define the audience and target role family. Identify the few capabilities and domains the profile should make obvious within a short scan.
2. Inventory verified claims and public proof. Remove or flag contradictions with the resume, portfolio, repositories, dates, titles, or current availability.
3. Write a headline that combines credible role direction, strongest relevant capability, and optional domain context. Avoid empty labels such as "passionate professional" or an exhaustive keyword chain.
4. Build the About section in reader order: current direction, strongest evidence, representative work, working style or domain interest, and a proportionate next-step signal.
5. Rewrite experience and project entries around ownership, decisions, constraints, delivered behavior, and outcomes. Use metrics only when verified.
6. Select Featured and portfolio items that prove the target capabilities quickly. For each item, make the problem, contribution, artifact, result, and limitations inspectable. Load references/profile-and-proof.md for a full audit.
7. Normalize skills and keywords around actual role vocabulary without claiming expertise unsupported by work. Keep the same factual core across LinkedIn, GitHub, portfolio, and resume.
8. Return ready-to-use copy, recommended ordering, proof gaps, and any statements that require candidate confirmation. Do not promise search ranking, engagement, or recruiter response.

Constraints

• Do not invent titles, employment, clients, metrics, endorsements, publications, credentials, or project adoption.
• Do not describe a learning project as production experience or team work as solely owned work.
• Do not use engagement bait, inflated superlatives, or stale claims about a platform's algorithm.
• Do not repeat the resume verbatim when a profile can add context, proof, and narrative.
• Do not expose private client details, confidential repositories, contact data, or sensitive employer information.
• Do not publish, connect, follow, endorse, or message without explicit authorization.

Verification

• The target role and strongest evidence are clear from the headline and opening lines.
• Every claim is consistent with the candidate's verified history and linked artifact.
• Featured work demonstrates capabilities through inspectable proof, not only assertions.
• Role terminology is natural, relevant, and not a keyword dump.
• Public links work when they can be checked, and private or unavailable artifacts are not presented as inspectable proof.
• Copy contains no placeholders, unsupported metrics, fake social proof, or algorithm guarantees.

Failure Modes

• Writing a broad headline that could describe thousands of unrelated candidates.
• Listing tools without showing decisions or artifacts that used them.
• Turning the About section into a chronological resume duplicate.
• Featuring polished screenshots that do not reveal the candidate's contribution.
• Optimizing for posting frequency or engagement folklore instead of credible positioning.

Examples

LinkedIn refresh: create a backend-focused headline and About section from verified internship and project evidence, then select two repositories that demonstrate API design and reliability work.

Portfolio proof: restructure a project page so a reviewer can see the problem, constraints, personal contribution, implementation evidence, result, and honest limitations in under two minutes.

Sources

See ../../sources/professional-profile.sources.md.

Load references/profile-and-proof.md for a complete LinkedIn or portfolio audit.