What is Skyy Moore still doing on the Kansas City Chiefs roster?

The Kansas City Chiefs thoroughly dismantled the New Orleans 26-13 on Monday Night Football to remain undefeated in a game where several wide receivers stepped up in the wake of a season-ending injury to standout wide receiver Rashee Rice.

Thanks to the heroics of veteran wide receiver JuJu Smith-Schuster sprinkled with some contributions from Mecole Hardman and rookie Xavier Worthy, the Chiefs' offense finally looked like it was starting to fire on all cylinders as Patrick Mahomes threw for over 300 yards for the first time this NFL season.

Despite the win, one player who continues to underperform is third-year wide receiver Skyy Moore. Moore is already coming off an extremely disappointing sophomore season in which he was expected to take on a much larger role. One could've reasonably expected Moore to step up in the absence of Hollywood Brown and Rashee Rice. With only five wide receivers healthy on the active roster, Kansas City needed Moore to show something to give us confidence that they have enough while down their top two receivers.

Instead, Moore has yet to record a catch this season and his only memorable moment in Kansas City's win on Monday night was a fumbled kick return that nearly ended in disaster. This comes just a week after Moore was targeted on a crucial third down against the Los Angeles Chargers only to drop a pass that hit him right in the hands.

All of this begs the question: If Skyy Moore isn't a useful player as a receiver or even a special-teamer, even with all of the injuries, why is he still on the roster?

The rationalizations for a player like Moore ever making the roster in the first place were, "He's cheap and on a rookie deal" or You spent a second-round pick on him" or "He's WR6, he'll never play anyway". However, we're reaching the point where those excuses no longer justify Moore sticking around and his lack of production has raised concerns that he can actually have a spot on a team with aspirations for a third straight Super Bowl.

First, regardless of where Moore falls on the depth chart, he should at least be playable. Every player on the depth chart should be expected to perform to some degree if needed. That's the lowest possible expectation for a player on an NFL roster and yet Moore can't seem to meet that. Moore is not playable nor good depth even as a WR6.

The issue with assuming that one will "never play" because of how low they are in the pecking order is ignorant and irresponsible especially given what we witnessed last year from this wide receiver group when Kansas City was rotating every single receiver in and out, trying to find answers. This year we're seeing Moore on the field out of necessity due to injuries, once again debunking the "Who cares? he's WR6 and will never see the field" rationalization. There's always a scenario where that player will be called upon.

The other part of this issue is that Moore, of course, brings absolutely nothing to the table. He hasn't even played much this year, but in the little time he has, he's managed to be a net negative on the field for Kansas City. This isn't just a situation where Moore is underperforming relative to his draft status, or struggles with consistency. This is a situation where he quite literally isn't doing anything to help the team. Again, with all of the injuries that have occurred, it should be a minimum expectation that Moore can fill snaps and catch a couple of passes, but he's not doing that, and it's starting to make us wonder why he's still here if he can't contribute a little to an extremely weakened position group in which he's taking up a roster spot.

Labeling Moore as "good depth" simply because he's young and cheap seemingly ignores the fact he cannot play. Situations like the Chargers game in which Moore dropped a wide-open pass in his lone target this season only further emphasize the notion that Moore shouldn't be on the team even as a reserve player because you need players to come through in those situations where injuries have taken a toll. These roster spots should not be treated as a throwaway because general manager Brett Veach wants to squeeze as much juice as possible out of his high draft pick.

Nonetheless, Brett Veach also is apparently fed up with Moore's lack of production in year three and his constant knack for finding a way to negatively impact the game in such little opportunities.

Following that up Moore's most recent blunder on Monday Night Football against the New Orleans Saints combined with Kansas City's clear need for an impact wide receiver given the injury situation, it seems as if the sun might be setting on Moore's time in Kansas City. In a game where others rose to the occasion, Moore's absence from key moments and poor performance only solidifies the belief he doesn't have a future in Kansas City.