I make skills for «this is how I like to do things in this company / project». Query test database, git branch names, commit message style, which cloud things can be inspected like logs etc. I don’t see the point in trying to teach the models things that is in the documentation of git, python, what have you. They already know.

▲

stanmancan 2 hours ago | parent [-]

Isn’t that what the agents.md in your project is for?

	▲	jve 16 minutes ago \| parent \| next [-]
		Skills are evaluated by short description whether to read them into context. Skills itself may be lengthy so...
	▲	paool 2 hours ago \| parent \| prev \| next [-]
		I try to keep agents/Claude.md as tiny as possible. With high level "truths" that don't change. Stack used, invariants, file structure, and some scripts. Skills are more for things you do often. I run mutation tests, type check,linting,etc. I _could_ just prompt and copy/paste the same prompt each time I need to, or I can just run /tests. I also have skills for specialized tasks I need every once in a while, like a ux skill, a text skill optimized for xyz, etc.
	▲	jpalomaki 2 hours ago \| parent \| prev [-]
		Depends on how much information and details you have. The agents.md always goes into context. Detailed testing or process information might be excessive, when agent is working on UI. Skills are pulled when needed.