Resumes and cover letters skills: first principles

The skills section is the least read and most padded part of a resume. It is usually a list of nouns with no evidence attached, and a reader who has seen four hundred of them treats it as noise. It can be made to do real work, and doing so requires giving up most of the list. A cover letter handles the same claims differently: it connects a relevant skill to a concrete example instead of repeating the list.

What to take away

Why the ordinary skills list fails

It fails for a simple reason: it is unfalsifiable as written and trivially falsifiable in conversation. "Excellent communication" survives no contact with a follow-up question. A named system with no context invites a test you may not be expecting.

It also competes with itself. A list of eighteen items tells the reader you are claiming everything, which is read as claiming nothing. Six items with evidence outrank eighteen without.

The right column is longer. It belongs in the experience section, not a list.

That is the real conclusion: move most skills list items into evidence, and shrink the list.

How skills work in a cover letter

A cover letter should not repeat the skills list. Choose a requirement that matters to the role and show it through a brief, relevant example: what you did, how you used the skill, and the result. Name a system only when it matters to the example.

A useful structure is: “In [role or project], I used [skill or tool] to [action], which led to [verifiable result].” Replace the brackets with a truthful example and connect it to the employer’s stated need. If you cannot support a claim with an example, leave it out of the letter as well as the resume.

What the list is genuinely for

Two things. The first is naming testable, specific abilities that a reader is scanning for: systems such as Excel, Salesforce, SAP, SQL, or Python; certifications such as the Project Management Professional (PMP) credential from the Project Management Institute (PMI); languages such as Spanish, with a truthful proficiency description; and regulated qualifications such as a current registered nurse (RN) license issued by the relevant state board of nursing. Include only items you hold or can demonstrate, and use the posting's terms when accurate. The second is naming the things a parser needs to find, since something usually reads the document into fields before a person sees it. A mandatory salary field on an application is separate: a skill or credential does not establish a salary or guarantee a pay premium, so use the employer's stated compensation rather than assuming a wage effect.

Qualities belong in the experience section, attached to an event. Employers with careful processes name the qualities they assess in advance.

The U.S. Office of Personnel Management (OPM) describes competency-based assessment in its competencies material: a defined quality has a name, a description, and behaviors that count as evidence. For federal applications, compare those behaviors with the competency language in the vacancy announcement on USAJOBS. Writing your experience to match one of those definitions is far more effective than putting the word in a list.

Where the requirements come from

Before a job is advertised, someone establishes what the work needs, usually by asking the people doing it. That output becomes the posting, the screening criteria and the interview questions, and the U.S. Office of Personnel Management's (OPM) job analysis guidance describes the process. Two things follow for a candidate.

First, borrow the posting's vocabulary. That is the vocabulary screening will use.

Second, the requirement list and the work description often diverge. The description is usually more honest. The requirement list comes from whoever owns the process; the description often comes from the person who will manage you.

The proficiency problem

"Advanced" is not a measurement. Two candidates use the word for capabilities that differ by an order of magnitude, and readers know this, which is why they discount it.

Replace the adjective with the artifact. What did you build, maintain, fix, or teach with it? If none apply, say you used it. That costs less than a claim that collapses in an interview.

Because every line invites a question, prepare a short example for each skill you keep: what you did, what you can explain, and how it relates to the role. For broader practice, see the interviews guide.

A short procedure

Step four is where most of the improvement comes from, and it usually shortens the page. For each application, match the resume's truthful skill claims to the posting. In the cover letter, develop the strongest relevant claim as an evidence-backed example.

Common questions

Should I include a proficiency scale with bars or stars?

No. It converts an unmeasured claim into a picture of an unmeasured claim, and it wastes space a reader could have spent on evidence.

What about soft skills? Employers ask for them constantly.

They do, and they assess them through examples rather than through lists. Put the example in the experience section and let the reader name the quality.

Do I need to list every system in the posting to get past a parser?

Include the ones that are true. Padding a list with systems you have not used solves a screening problem by creating an interview problem.

How long should the section be?

Short enough to read in one glance. If it runs past a few lines, most of it belongs elsewhere or nowhere.

Where do languages and certifications go?

In the list, with the level or the awarding body and the date. For example, name the Project Management Professional (PMP) certification and its issuer, PMI; list Spanish only at a proficiency level you can demonstrate; and include a current license only when relevant to the role. A credential is worth considering when the posting requires or prefers it, or when it provides verifiable, role-relevant training; weigh its fee and time against that value rather than assuming it guarantees higher pay. Whether a certification is worth having in the first place is a separate question, treated in the page on judging a credential.