3 Chiefs Who Will Be Traded by the End of October

2. Skyy Moore, wide receiver

When it comes to the case of former second-round pick Skyy Moore, the writing has been on the wall for quite some time. It feels like Moore was on the roster chopping block dating back to training camp and the Chiefs have done just about everything they possibly can to replace him.

But they haven't let him go yet. Why?

Why does Moore still have a spot on this roster. Our good friends over at Arrowhead Addict recently had some strong words regarding the attachment Kansas City Chiefs GM Brett Veach has to his former second-round pick:

"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."

- Arrowhead Addict

There are fair points being made in there regarding the fact that the Chiefs don't just have the luxury of a bunch of roster spots being handed to players who aren't making substantial contributions, especially with the quality of players that have already landed on IR early this season.

Skyy Moore has done nothing to prove himself worthy of a roster spot on the Chiefs at this point. He's not contributing as a receiver or returner, and he might just need a change of scenery at this point. Luckily for him, he's still very young and the ink is probably still drying on his scouting reports for some teams out there who loved his upside a couple of years ago.