--- name: li-profile description: >- Score a LinkedIn profile out of 100 against a 12-part rubric and rewrite the parts that lose points - headline, about, experience, featured, banner. Use when the user says "optimize my profile", "score my LinkedIn", "rewrite my headline", "fix my about section", or pastes their profile and asks how it reads. title: li-profile canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-profile last_updated: 2026-09-23T04:26:26.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [rubric.json](https://skilld.dev/api/skills-raw/jakeschincariol/linkedin-agent-skill/li-profile/rubric.json). > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-profile`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/li-profile`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/jakeschincariol/linkedin-agent-skill/li-profile) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/li-profile`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/li-profile --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-profile --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # li-profile A profile is not a resume. A resume answers "what have you done". A profile answers "should I message this person", and it answers it in about four seconds, from the headline and the first two lines of the about. ## Input Ask the user to paste: headline, about section, current role and the last two experience entries, plus whether they have a banner and featured section. A screenshot of the top card is enough for the first pass. Do not log into LinkedIn on their behalf. ## Score it Read `rubric.json` in this folder. Twelve items, 100 points, each with what full marks looks like. Score every item, show the table, and give the total. Be honest - most profiles land in the 30s and 40s on the first pass, and a generous score is useless. ``` PROFILE SCORE 41/100 headline 3/12 job title only, no outcome, no audience about first 2 lines 2/10 opens with "passionate about" about body 4/10 history, not offer featured 0/8 empty banner 0/6 default blue ... ``` ## Then rewrite, in this order Fix in descending order of points lost. Do not rewrite everything at once - the user has to actually paste each of these in. **1. Headline (220 characters).** The formula that works: `{what you do for whom} | {proof} | {how to start}`. Not your job title. Not "Helping X do Y" as the first three words, which every second profile now opens with. Give three options. **2. About, first two lines.** Everything after line 2 is behind "see more" on mobile, so those two lines are the whole about section for most readers. They must state who you help and what changes. No "passionate", no "results-driven", no third-person bio, no opening with your own name. **3. About body.** Written to one reader, in the second person. Structure: the problem they have, what you do about it, one piece of proof with a number, what to do next. Under 1,400 characters even though the limit is 2,600. **4. Featured.** Three items: the best post, the proof asset, the way to contact. An empty featured section is eight points and the only place on the profile you fully control. **5. Experience.** Each role gets one line of scope and two to three bullets that are outcomes with numbers, not duties. Cut anything older than ten years to a single line. **6. Banner.** One sentence of positioning and one way to reach you. The default blue gradient is the clearest signal on the page that nobody is home. ## Output Score table, then the rewrites as copy-ready blocks in fix-first order, each one already run through `/li-human`. Re-score at the end and show the delta honestly - if the rewrite gets to 88 and not 98, say 88, and say what the remaining points need (usually recommendations, a real banner and posting history, none of which a rewrite can create). Nothing is saved to LinkedIn by this skill. The user pastes each section in.