How to write a skills section that actually says something

The skills section is often the most skimmed and least considered part of a resume or portfolio. People paste in a long list of words, add "team player" and "hard-working," and move on. A well-written skills section does more: it helps a reader see quickly what you can do, and it backs up the rest of your page.

This guide shows how to group your skills, make each one specific, handle proficiency levels honestly, tailor the list to a job, and deal with soft skills without empty labels.

What a skills section is for

A skills section has two readers. The first is a person scanning your page for a few seconds to decide whether to keep reading. The second, on some job sites, is software that matches words in your application to words in the job post.

Both readers want the same thing: a clear, organised list of capabilities that relate to the work. Neither benefits from a wall of thirty unsorted terms. The aim is not to list everything you've ever touched, but to list what you'd be comfortable being asked about in an interview.

Tip: A useful test for every skill you list: could you talk about a specific time you used it for five minutes? If not, it probably doesn't belong.

Group your skills into categories

Grouping makes a long list readable and shows that you understand how your skills fit together. Choose three to five categories that make sense for your field.

Here's an unsorted list from a hypothetical marketing coordinator:

• Before: Canva, SEO, copywriting, Google Analytics, email marketing, teamwork, Excel, social media, Mailchimp, communication, content calendars, A/B testing, Spanish.

And the same skills grouped:

• Content: copywriting, blog and newsletter writing, content calendars
• Channels: email marketing, organic social media, search engine optimisation
• Analysis: web analytics, A/B testing, spreadsheet reporting
• Tools: Canva, Mailchimp, Excel
• Languages: English (native), Spanish (conversational)

Notice that "teamwork" and "communication" have disappeared. We'll come back to them.

Category ideas by field

• Software developers: languages, frameworks, databases, infrastructure, practices (testing, code review)
• Designers: research, interaction design, visual design, prototyping, tools
• Teachers: subjects and levels, curriculum design, assessment, classroom technology
• Data analysts: analysis methods, programming, visualisation, data tools
• Writers: formats, subject areas, editing, research

Be specific

Vague skills tell a reader very little. Specific skills give them something to picture and something to ask you about.

A few before/after rewrites:

• "Microsoft Office" becomes "Excel (pivot tables, lookups, charts), PowerPoint"
• "Social media" becomes "Instagram and LinkedIn content planning and scheduling"
• "Programming" becomes "Python, JavaScript, SQL"
• "Design" becomes "Logo design, brand guidelines, social graphics"
• "Customer service" becomes "Phone and live chat support, complaint resolution, refund processing"
• "Research" becomes "User interviews, survey design, competitor reviews"

Specific doesn't mean longer. "Python, SQL" is shorter than "various programming languages" and far more useful.

Drop the obvious

Some skills are so basic for your field that listing them looks odd. A software developer doesn't need to list "email" or "typing." An experienced designer doesn't need "attention to detail." Including them takes space away from skills that would set you apart.

Handle proficiency levels carefully

It's tempting to show how good you are at each skill with stars, bars or percentages. These visuals have problems. "Four out of five stars in Python" means nothing objective, and a bar at 60 percent invites the question of what you can't do. Different readers interpret them in completely different ways.

Plain words work better. You can group skills by level:

• Advanced: Python, SQL, data cleaning
• Working knowledge: R, Tableau
• Learning: cloud data warehouses

Or attach context to specific skills:

• "Spanish: conversational, used daily with customers for two years"
• "Figma: daily use for three years, including building component libraries"
• "Excel: build monthly reports and forecasting models for a team of 12"

Context like years of use, how often you use it or what you built with it is more believable than a self-rating. For languages, standard frameworks of proficiency levels exist and are widely understood, so use one if you've been assessed.

Be honest. Calling yourself "advanced" in something you used once in a course will catch up with you in an interview or in the first week of a job.

Match skills to the job you want

A skills section should change depending on what you're applying for. You don't need to rewrite it every time, but you should review it.

A simple process:

1. Read the job post carefully. Highlight every skill, tool and qualification mentioned.
2. Mark what you genuinely have. Be honest; only the skills you could discuss with examples.
3. Use their words where accurate. If the post says "stakeholder management" and you've written "working with clients," and they mean the same thing in context, use their phrasing.
4. Reorder. Put the most relevant categories and skills first.
5. Remove clutter. Take out skills that are unrelated to this role if the list is getting long.

Never add a skill just because it's in the post. Matching words is only helpful if it's true; otherwise you're setting yourself up for an uncomfortable conversation.

If you're keeping one portfolio for several kinds of roles, organise your skills around the direction you want to go, and keep a longer master list in a document you can draw from when you tailor applications.

Show soft skills, don't tell them

Words like "communication," "leadership," "problem-solving" and "teamwork" appear on so many resumes that readers barely register them. Anyone can type them. What makes them believable is evidence.

Instead of listing soft skills, show them in your experience and projects:

• Instead of "Strong communication skills"
• Write "Wrote the weekly project update read by 40 people across three departments"

• Instead of "Leadership"
• Write "Trained and supervised four new team members during the busy season"

• Instead of "Problem-solving"
• Write "Found the cause of repeated delivery errors and changed the packing checklist, which ended the complaints"

• Instead of "Adaptable"
• Write "Moved the class to remote teaching within a week, including new materials for 28 students"

These statements belong in your experience bullets, project descriptions or bio, not in the skills list. The skills section can then focus on concrete, nameable abilities. The guide on quantifying your achievements has many more examples of turning duties into evidence.

Where the skills section goes on a portfolio

On a portfolio website, skills usually work best after your headline, bio and best work, not before. Visitors want to see what you've done first; the skills list then confirms and summarises it.

Link skills to proof where you can. If you list "data visualisation," make sure at least one project shows a chart you made. If you list "user research," one of your case studies should involve interviews or testing. A skill that's backed up somewhere else on the page is far more convincing than one that only appears in a list. For more on what goes where, see what to include on a portfolio website.

A quick checklist

Before you publish, check that your skills section:

• Has three to five clear categories
• Uses specific names for tools, methods and subjects
• Avoids star ratings and percentage bars
• Lists only skills you could discuss with examples
• Puts the most relevant skills first for the work you want
• Leaves generic soft skills out of the list
• Connects to evidence elsewhere on your page

Putting it together

A good skills section is short, sorted and specific. Group related skills, replace vague terms with precise ones, describe proficiency in plain words with context, and reorder for the work you're targeting. Leave the soft skills to your stories and results, where they're actually believable. Done this way, your skills section stops being filler and becomes a quick, trustworthy summary of what you can do.