...
By Zach Pressnell
Contributing Sports Writer
0
Share
Newsweek is a Trust Project member
See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.
The Detroit Tigers could be looking to trade ace Tarik Skubal in the coming months if they can't get close to a massive contract extension. Skubal is entering the final year of his contract and could be looking for at least $300 million on his next contract.
As a result, the Tigers might be better off trading him if there's next to no chance of re-signing him.
Sportsnet's David Singh offered bold predictions for 2026, and he believes the Tigers will opt to trade Skubal to the Atlanta Braves in the coming months. A trade like this would change the entire outlook of the league.
Read More on MLB
...
"By midseason, the club will own the best record in the National League, ahead of the Dodgers and Phillies, and that will prompt general manager Alex Anthopoulos to go full 2015 trade deadline mode and shock the baseball world by acquiring Skubal in July," Singh wrote. "Skubal, a pending free agent, is a Scott Boras client and the left-hander is in line to receive the largest contract ever for a pitcher.
"The Tigers will be priced out, and that means a trade is imminent because even if the club is contending by July, it simply can’t afford to lose Skubal for nothing when he walks in free agency."
The Braves fell apart last season, but they are a piece or two away from contending for a World Series next year.
Adding Skubal would certainly put the Braves back on the map. He would fill a hole at the top of the team's rotation, which is only going to get more problematic as Chris Sale gets older.
Trading for Skubal is a long shot, but if there's a way for the Braves to do it, general manager Alex Anthopoulos will likely try to find it. It seems unlikely, but the Braves make a lot of sense as a trade fit for the star lefty.
More MLB: Cubs’ $427 Million Superstar Predicted To Bolt For Deal With AL Contender
View 0 Comments
Submit Correction
View Editorial & AI Guidelines