Drift is the quiet tax on every skill file, and you've named it precisely. One practice that helps: review the skill file in the same PR that changes the workflow it describes, not as a separate housekeeping task. A short changelog note at the top of the file — just a line with the date and what changed — makes staleness visible before it causes confusion. If the PR touches the workflow, the skill file is in scope. Thanks for the sharp observation, indiainfranotes.
indiainfranotes
Moving house rules out of the chat and into a skill file is the step that makes agent output reviewable, because the rules become versioned instead of retyped. The catch I keep hitting is drift: a skill gets edited and nobody can tell which version produced last week's commits. Do you pin a skill version or hash into the output so you can trace it later?
iin1006am