Auto-Retiring Skills You No Longer Use: Weekly Skill Lifecycle Management with l

<p>Back when I was a college student earning ¥100,000 a month, one finished article meant my week was over. Today launchd stocks one every morning at 8:00, and the series that

<p>This is a follow-up to my <a href="https://zenn.dev/bokuwalily/articles/claude-autopilot" rel="noopener noreferrer">previous post</a> on getting Claude Code to improve itself

<p>This is a continuation of my "Claude Code environment" series. After <a href="https://zenn.dev/bokuwalily/articles/claude-config-git-backup" rel="noopener noreferrer">the

<ul> <li><p>Skills enable Claude to retain expertise across sessions via slash commands, eliminating repetitive explanations of workflows and preferences.</p></li> <li><p>A skill

<p>Nobody notices their dev environment rotting. It happens one broken MCP server at a time, and by the time you feel it, you have no idea which week it started. My fix was to

<p>If you read my earlier post on the <a href="https://dev.to/pponali/how-i-cut-claude-code-token-consumption-by-96-with-the-skill-vault-pattern-9d1">Skill Vault pattern</a>, you