# An Honest Skills Section — Resume & GitHub Portfolio

Source: https://www.skillbyai.com/en/resume-portfolio/s-skills

> Grouped, relevant and defensible.

## List what you can actually discuss

A skills section is a quick index, not proof; your bullets and projects provide the proof. Group skills into a few categories such as **Languages**, **Frameworks**, **Data**, **Tools and Cloud**. List only skills you could answer reasonable interview questions about, and consider separating **proficient** from **familiar** if your list mixes depth levels. Avoid **keyword stuffing**: long lists of every technology you have touched, hidden text, or copying a job description's keywords you do not have. These can mislead reviewers and tend to fall apart in interviews. Skip ratings like stars or percentages; they are subjective and say little.

## Before and after

From a keyword dump to an honest, grouped list.

```text
Before:
  Skills: Java, Python, C, C++, C#, Go, Rust, Kotlin, Swift, React, Angular,
  Vue, Svelte, Node, Django, Flask, Spring, AWS, GCP, Azure, Docker, Kubernetes,
  Terraform, Kafka, Spark, ML, AI, Blockchain, MS Office ...

After:
  Languages:     Java, TypeScript, SQL (proficient); Python (familiar)
  Frameworks:    Spring Boot, React
  Data:          PostgreSQL, Redis
  Tools / Cloud: Git, Docker, GitHub Actions, basic AWS (EC2, S3)
```

## Every skill is an interview question

Before listing a skill, ask yourself: could I explain a project where I used it and answer a follow-up question? If not, leave it off or mark it as familiar.

**Quiz:** What is the main risk of keyword stuffing a skills section?

- [ ] It forces you to use two columns
- [ ] It makes the resume too short
- [ ] It hides your contact details
- [x] It misrepresents your abilities and can fall apart in interviews

*Answer:* It misrepresents your abilities and can fall apart in interviews. Only list skills you can defend.