Tag: skills
All the articles with the tag "skills".
-
Memories Fade. Skills Persist.
When an agent makes a mistake, you have two choices: write it down or encode it. One survives the next session. One doesn't.
-
The Name Is the First Lesson
When you name a skill thesis-generator, you've already decided the user is a consumer not a practitioner. The name is the first design decision.
-
Methodology Is Infrastructure
Every AI session starts fresh. If your methodology lives only in your head, it resets too. The fix is treating it like code.
-
Skills as Institutional Memory — Why Individual Craft Doesn't Compound Without Distribution
You built a workflow that saves four hours a week. It lives on your laptop. Nobody else benefits. That's not a knowledge management problem — it's a distribution architecture problem.
-
What Is a Skill — Why Methodology Resets Every Session Without One
Every agent session starts from zero. The model is brilliant. The tools are connected. And still — you spend the first ten minutes re-explaining how you work. Skills are the fix.
-
From Failure Mode to Skill Chain
When an agent leaked a Slack channel ID by bypassing the scrub-and-publish skill, the fix wasn't a memory — it was wiring three skills together so the chain self-enforces.
-
Your Agent's Behavior Is Code — Start Versioning It
AI agent behavior committed to a repo travels with the codebase — reviewable, diffable, available to every contributor on first checkout. Treating skills as code artifacts converts ad hoc agent use into an institutionalized team process.
-
The Skill Is the Teacher
We've been naming AI skills like tools. That's the wrong frame — and it's quietly limiting how much value teams get from them.