Chiefs proved on Monday night that there's nothing left to do with failed second-round draft pick

One of the most disappointing recent draft picks for the Kansas City Chiefs has been wide receiver Skyy Moore.

Kansas City selected Moore in the second round of the 2022 NFL Draft. Many believed that he could develop into a quality slot receiver in the NFL with the strong hands and crips route running ability that he displayed during his college days. Unfortunately for both Moore and the Chiefs, that has not been the case.

During Moore's rookie season the Chiefs tried to break him in as the team's top return specialist, but he lost three fumbles on punt returns. In 2023 Moore was projected to be a starting receiving, and while he did start a handful of games, he just simply couldn't produce.

Despite playing 182 more snaps than he did as a rookie, he caught one less pass on the season. Entering 2024 Moore's spot on the roster wasn't guaranteed, but he managed to snag the final wide receiver spot on the depth chart. In 35 total games played, Moore has just 43 catches for 494 yards and one touchdown.

It now appears that K.C. has basically given up on him altogether. Despite being depleted by injuries within their wide receiving corps, Moore wasn't on the field for a single one of quarterback Patrick Mahomes' 44 drop backs during Monday night's win over the New Orleans Saints (H/T Adam Levitan of Establish The Run).

The last two times Moore has gotten his hands on a football during a game, he dropped a pass against the Los Angeles Chargers and muffed a punt against the Saints. This begs the question, why is Moore still taking up a roster spot at this point? The Chiefs clearly have lost all faith in him, even with the dire situation they have at WR.

Fortunately for K.C., pass catchers such as JuJu Smith-Schuster and Mecole Hardman stepped up on Monday night. The Chiefs also have some talent at WR on the practice squad that deserves a shot to show what they can do. It's clear that Moore isn't going to contribute in K.C. and he deserves the chance to get a fresh start somewhere else, and its' time the Chiefs admit their mistake and move on.

Related: Chiefs' Week 5 snap counts: What does the Kansas City offense look like without WR Rashee Rice?