You installed a skill. The README looks fine. The demo in the docs worked on the first try. Should you keep it? You can’t tell from the README. You have to run the skill on your own work and look at what comes out. This post walks through doing that. We start with the simplest […]
Read More →Ranking repos by stars favors visibility over fit. That can be a fair first filter—stars are cheap and usually mean someone noticed the project—but treating the count as proof of quality, maintenance, or production readiness is the common mistake. What follows is what stars actually measure, where they mislead, and what to check on the […]
Read More →The ecosystem of “AI skills” — modular instruction packs that extend an LLM with task-specific know-how, whether they’re called Skills, plugins, agents, MCP servers, system-prompt templates, or tool bundles — has exploded fast enough that “which one should I use?” has become the dominant question. The answer is rarely obvious from a README, and almost […]
Read More →The most underrated trick I have landed on is treating Claude Code as a coach for using Claude Code. The tooling already sees how you work: sessions, prompts, tools, and where time goes. The part most people skip is closing the loop: turn that signal into habits, not just a pretty chart. The workflow You can punt […]
Read More →Specs and change proposals live in the repo; Jira still owns Epics, Stories, and the board. You can do both without maintaining two truths: tie one OpenSpec change folder to one Story, leave tasks.md out of Sub-tasks, and link every ticket to openspec/changes/…. Most organizations will not retire Jira; this split is how you get SDD anyway without […]
Read More →