When should you turn a repeated Claude workflow into a 'skill' versus keeping it as a chat or project?

A member described reaching the end of a repeatable workflow (in their case, producing an executive summary of financials from chunked financial data) and asking Claude directly whether it should be made into a skill or a project. Claude recommended making it a skill and walked them through the process. Now, instead of re-writing the prompt each time, they paste in the financials and ask for the executive summary, and Claude produces the same consistent output every time by referencing the skill. The suggestion was that if you find yourself repeating a task or prompt structure often, it may be worth converting it into a Claude skill rather than reconstructing the prompt from scratch each time. Note: this same member said they had not yet tried Claude's 'co-work' feature, since it seemed too browser-intensive for their workflow.