From ade375db8f2597dcd620d60c861f039a9d36c8c9 Mon Sep 17 00:00:00 2001
From: Amolith <amolith@secluded.site>
Date: Sun, 28 Dec 2025 08:51:20 -0700
Subject: [PATCH] docs: document skill naming conventions

Assisted-by: Claude Opus 4.5 via Crush <crush@charm.land>
---
 AGENTS.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index 96f753953f3c2a7da7b7679f4d880411a9892244..94b4e0ebb1aa81338708e2637f3a61a112df4bf4 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -18,6 +18,13 @@ skills/skill-name/
 
 The `skills/authoring-skills/` directory has the necessary info for, well, authoring skills.
 
+## Naming Convention
+
+Two categories of skills exist:
+
+- **Generic capability skills** (`resolving-secrets`, `formatting-commits`): Use specific tools to accomplish general tasks. Tool name omitted from skill name.
+- **Service workflow skills** (`deferring-work-through-lunatask`): Workflows for specific proprietary services. Service name included via `-through-{service}` suffix.
+
 ## Design Principles
 
 1. Progressive disclosure: Frontmatter loads at startup; SKILL.md body loads on activation; references/ load on-demand