https://k4i.top/tags/workflow/Recent content in Workflow on k4i's blogHugo -- gohugo.ioensky_io@outlook.com (K4i)sky_io@outlook.com (K4i)All content is subject to the license of <a rel="license noopener" href="https://creativecommons.org/licenses/by-nc-sa/4.0/" target="_blank">CC BY-NC-SA 4.0</a> .Sat, 23 May 2026 10:30:00 +0800https://k4i.top/posts/agent-skill-management/Sat, 23 May 2026 10:30:00 +0800sky_io@outlook.com (K4i)Sat, 30 May 2026 00:36:50 +0800https://k4i.top/posts/agent-skill-management/<h2 id="why-skills-matter">Why Skills Matter</h2> <p>After using coding agents for a while, I have found that the limiting factor is often not whether the model is clever enough today. It is whether the agent can reliably reuse experience.</p> <p>In a real repository, there are many implicit rules: which test command to run, which files should not be touched casually, where generated images belong, what must be checked before publishing, and whether a bug report should trigger root-cause analysis before patching. Humans handle these rules through memory and habit. An agent does not automatically know them at startup. Putting everything into one giant <code>AGENTS.md</code> is not ideal either: the context grows, trigger boundaries blur, and the result becomes &ldquo;everything is written down, but the important part may still not fire at the right time.&rdquo;</p>K4ifeatured imageagentcodexskillsworkflownotes