# LinkedIn skill assessment answers, and the December 2023 notice at the top

> This repository is a table of contents: one directory per technology, one markdown file of questions and answers, translations in five languages, and a status column that marks which topics still need updating. The thing it was built to help you pass no longer exists, and the README says so in its first line.

**Ebazhanov/linkedin-skill-assessments-quizzes** — Full reference of LinkedIn answers 2024 for skill assessments (aws-lambda, rest-api, javascript, react, git, html, jquery, mongodb, java, Go, python, machine-learning, power-point) linkedin excel test lösungen, linkedin machine learning test LinkedIn test questions and answers 

- Repository: https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes
- Website: https://ebazhanov.github.io/linkedin-skill-assessments-quizzes/
- Stars: 28,844 · Forks: 12,876
- Language: Python
- License: AGPL-3.0
- Published: 2026-09-21 · Updated: 2026-09-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/ebazhanov-linkedin-skill-assessments-quizzes

## The first line of the README is a notice about December 2023

The most important sentence in this repository is at the top of the README, not at the bottom: as of December 2023, skill assessments are no longer available on LinkedIn, and you can still master your knowledge here. Everything else in the repository is downstream of that.

It changes what the thing is. It was built as an answer key for a test people could take, and the repository description still says full reference of LinkedIn answers 2024 for skill assessments, listing aws-lambda, rest-api, javascript, react, git, html, jquery, mongodb, java, Go, python, machine-learning and power-point among others. That framing is now a study collection with a competitive origin.

So judge it as a question bank. Does the topic you need exist, are the answers there in full, and who checked them? Those are answerable from the repository. Whether a given item matches what LinkedIn once asked is not, because nothing here records the original item sets. The repository is honest about the first thing and silent about the second.

## One directory per topic, and a status column that admits what is stale

The layout is flat and obvious. The top level is a long list of topic directories, accounting/, adobe-photoshop/, aws-lambda/, bash/, c++/, css/, cybersecurity/, django/, git/, go/, html/, java/, javascript/, jquery/, json/, kotlin/ among the visible ones, each holding a quiz markdown file. There is no application, no service and no build; the content is the repository.

The README table is the index, and its columns are the useful part. Each row has the quiz file, a Passed/Failed status, a Translation column, a question count, an answer count, and the people to contact about that row. The counts are checkable: Accounting shows 75 questions and 75 answers, Adobe-Acrobat 48 and 48, Adobe-AI 50 and 50, Adobe-Illustrator 93 and 93.

The status column is the honest part. Accounting, Adobe-Illustrator and Adobe-InDesign all carry a needs updating marker while their question and answer counts still match. That is a repository telling you which topics it does not stand behind, which is worth more to a reader than a completeness badge, and it is the first thing to check before you spend an evening on a topic.

## The source code, the web apps and the terminal quiz live in another repository

The contribution instructions do not say pull request against this repository. They say to click through to a different one, linkedin-faq, for the source code. The same split shows up in the playground links: MD2Practice and Skill Assessments Quizzes as web apps, and LinkedIn Quizzed with Kodyfire as a terminal tool, all hosted under the linkedin-faq organisation rather than here.

So this repository is the published content and the other one holds the code that serves and presents it. Two consequences follow. A fork of this repository gets markdown files and no tooling, so the web apps and the terminal quiz are not something you can rebuild from what is here. And two repositories that are edited by overlapping contributors can drift, which matters when the questions in the markdown and the questions the web app serves are supposed to be the same set.

For an organisation that wants to host these quizzes internally, that means planning around two clones. The Discord and the Telegram channel are where the project asks people to bring quiz problems, so that is also where the drift tends to surface first.

## package.json says MIT, the repository licence says AGPL-3.0

The repository carries a LICENSE file and the licence recorded for the project is AGPL-3.0. The manifest in the same tree says something different:

```json
  "name": "linkedin-quiz-skill-assessments",
  "version": "2.0.0",
  "main": "index.cjs",
  "license": "MIT",
```

The rest of the manifest explains what it is for. There is exactly one script, a format script that runs prettier over the markdown files, and one dev dependency, prettier. The main field points at index.cjs, which is not among the top-level entries. The repository is also tagged as Python as its primary language, which fits neither the manifest nor a tree of markdown files.

Read together, the manifest is a formatting harness for a documentation repository rather than a package. Nothing here is installable, and the licence field inside it should not be the basis for a reuse decision when the LICENSE file says something else. If you plan to republish the questions, that is the first file to settle.

## One release from 2021 in a repository that changed in August 2026

The release list has a single entry, version 1.0.4, published on 2021-02-03. The last push to the repository was on 2026-08-29, and it is not archived.

That gap is the whole version story. The content is maintained continuously and released essentially never, so there is no tag to pin a fork to, no changelog entry describing what a question set changed between snapshots, and no way for a downstream copy to say which version of an answer it is holding. The commit log is the only history.

The same staleness shows up in the contribution hooks. The README points first-time contributors at the Hacktoberfest 2025 participation guidelines, a seasonal event that has passed, so the on-ramp it advertises is from a year earlier than the last commit. Neither of these makes the content wrong. Both make the repository harder to treat as a maintained dependency, which is the honest way to hold it: a snapshot of somebody's accumulated answers with contributors still arriving.

## Answers are expected to carry a reference, and each row names its reviewer

The contribution rules are more demanding than an answer key usually is. To add questions you go to the source repository. For answers you are asked to add an explanation or a reference link, and the reason given is that it helps anyone who does not already understand the concept. Spelling and grammar are checked with Grammarly. There is an issue template in the tree and a Discord for quiz problems and for questions about skills endorsement.

The per-row contact column is the part with teeth. The Accounting row names three people, and the instruction in the table header is to contact that person or add them to review your pull request. So review here is a named human attached to a topic rather than a maintainer queue, which means an answer about, say, Adobe InDesign goes to the people who look after that row.

There is also a disclaimer saying the owners are not liable for illegal use of the content, that it is provided for informational and educational purposes, and that users are responsible for their own actions, with a line stating the maintainers never contact anyone for money. For a repository of exam answers collected from a now-defunct test, that framing is a reasonable one to read before deciding how much weight to put on any single answer.

## It will not get you a badge, and it cannot tell you what LinkedIn asked

Three things this repository cannot do, stated plainly. It cannot get you a LinkedIn skill assessment result, because the README says those assessments have not been available since December 2023. It cannot tell you which questions any particular test contained, because the item sets are not recorded anywhere in the repository. And it cannot rate an answer as correct against a source of truth, because nothing describes a verification process beyond a named reviewer and a request for a reference link.

What it does give you is a large, organised, human-maintained set of questions and answers with translations, a completeness count per topic and a staleness marker where the maintainers know they are behind. That is a study aid. Treating it as a certification source is the mistake, and the December 2023 notice exists precisely to prevent that.

There is one more boundary worth naming. Timed mock tests, pass thresholds and scoring are not part of this repository. The terminal quiz and the two web apps are the closest thing to an exam, and they are maintained elsewhere. If your requirement is an offline practice test you can run in CI, this repository gives you the content and none of the harness.

## Conclusion

Use this repository to study, not to pass anything, because the README's first line says skill assessments have not been available on LinkedIn since December 2023. It works as a checklist: pick a topic directory, check that the Questions and Answers counts match, and skip the rows the table marks as needing updates, which currently include Accounting, Adobe Illustrator and Adobe InDesign. Treat every answer as community written, since the only quality control the project describes is a named reviewer per row and a request that contributions include a reference link. And read the LICENSE file rather than package.json when you reuse the content, because the two disagree on the licence.

## FAQ

### What are the answers to the LinkedIn quizzes?

They are in the repository, one markdown file per topic, with the README table listing the question and answer counts side by side: Accounting shows 75 and 75, Adobe-Acrobat 48 and 48, Adobe-Illustrator 93 and 93. Contributions are expected to add an explanation or a reference link, not just the answer.

### Where can I find a LinkedIn skill assessment test?

Not on LinkedIn, since the README states skill assessments have not been available there since December 2023. The repository points to practice apps instead, MD2Practice and Skill Assessments Quizzes as web apps and LinkedIn Quizzed with Kodyfire in the terminal, all hosted in the linkedin-faq repository rather than in this one.

### Can you do a quiz on LinkedIn?

Not through LinkedIn's skill assessments, which the README says have not been available since December 2023. The same questions and answers can be worked through in the practice web apps and the terminal quiz that the project links from its README, hosted in the linkedin-faq repository.

### Did LinkedIn remove skill assessment?

The first line of the README says that as of December 2023 skill assessments are no longer available on LinkedIn, and offers the repository as a way to master the knowledge instead. The project is not archived and the last push was on 2026-08-29.

## Sources

- [Ebazhanov/linkedin-skill-assessments-quizzes on GitHub](https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes)
- [License: AGPL-3.0](https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes/blob/main/LICENSE)
- [Project website](https://ebazhanov.github.io/linkedin-skill-assessments-quizzes/)
- [README](https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes/blob/main/README.md)
- [Releases](https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/ebazhanov-linkedin-skill-assessments-quizzes