Commit 4283545a4232

@@ -1,5 +1,5 @@
 ---
-name: BacklogTriage
+name: backlog-triage
 description: "Deep LLM-powered Jira backlog triage against upstream repositories. USE WHEN user says 'triage backlog', 'backlog analysis', 'clean backlog', 'analyze jira backlog', or wants to assess relevance of Jira issues against upstream git/GitHub activity."
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Brainstorming
+name: brainstorming
 description: Interactive design refinement through collaborative dialogue before implementation. USE WHEN user wants to design a feature OR plan architecture OR explore approaches OR needs help thinking through implementation before coding OR asks "how should I" build something. Asks questions one at a time, proposes alternatives, validates incrementally.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: CodeReview
+name: code-review
 description: Multi-focus code review using specialized subagents. USE WHEN user wants code review, security audit, performance review, Nix review, or says "review" with a focus area.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: CORE
+name: core
 description: Personal AI Infrastructure core principles and operating system. AUTO-LOADS at session start. USE WHEN any session begins OR user asks about identity, response patterns, workflow preferences, or core principles.
 ---
 

@@ -13,27 +13,27 @@ Ask the user:
 
 ### 2. Choose the Name
 
-- Use TitleCase (PascalCase)
-- Examples: `Docker`, `Kubernetes`, `WebDev`, `DataAnalysis`
-- Never use: `docker`, `web-dev`, `data_analysis`
+- Use lowercase-with-hyphens (kebab-case)
+- Examples: `docker`, `kubernetes`, `web-dev`, `data-analysis`
+- Never use: `Docker`, `WebDev`, `data_analysis`
 
 ### 3. Create Directory Structure
 
 ```bash
-mkdir -p ~/.config/claude/skills/[SkillName]/{workflows,tools}
+mkdir -p ~/.config/claude/skills/[skill-name]/{workflows,tools}
 ```
 
 ### 4. Create SKILL.md
 
-Create `~/.config/claude/skills/[SkillName]/SKILL.md` with:
+Create `~/.config/claude/skills/[skill-name]/SKILL.md` with:
 
 ```yaml
 ---
-name: SkillName
+name: skill-name
 description: Brief description. USE WHEN user mentions [trigger1], [trigger2], or needs [specific capability].
 ---
 
-# SkillName
+# Skill Name
 
 Brief overview of what this skill provides.
 
@@ -55,13 +55,14 @@ User: "[trigger phrase]"
 
 ### 5. Create Initial Workflow
 
-If the user wants workflows, create them in `workflows/` directory using TitleCase naming.
+If the user wants workflows, create them in `workflows/` directory using TitleCase naming for workflow files.
 
 ### 6. Verify Structure
 
 Check:
-- ✓ Directory name is TitleCase
+- ✓ Directory name is lowercase-with-hyphens
 - ✓ SKILL.md has valid YAML frontmatter
+- ✓ `name` field matches directory name
 - ✓ Description is ONE LINE with USE WHEN triggers
 - ✓ Workflow files use TitleCase.md naming
 - ✓ At least one example is provided
@@ -73,10 +74,10 @@ Show the created structure and ask for confirmation or adjustments.
 ## Output Format
 
 ```
-Created skill: [SkillName]
+Created skill: [skill-name]
 
 Structure:
-~/.config/claude/skills/[SkillName]/
+~/.config/claude/skills/[skill-name]/
 ├── SKILL.md
 ├── workflows/
 │   └── [WorkflowName].md

@@ -6,11 +6,11 @@ Validate a skill's structure, naming, and compliance with conventions.
 
 ### 1. Read the Skill File
 
-Read `~/.config/claude/skills/[SkillName]/SKILL.md`
+Read `~/.config/claude/skills/[skill-name]/SKILL.md`
 
 ### 2. Check Directory Naming
 
-- ✓ Directory name is TitleCase (e.g., `Golang`, not `golang`)
+- ✓ Directory name is lowercase-with-hyphens (e.g., `golang`, not `Golang`)
 - ✓ Directory name matches YAML `name` field
 
 ### 3. Validate YAML Frontmatter
@@ -18,13 +18,13 @@ Read `~/.config/claude/skills/[SkillName]/SKILL.md`
 Required fields:
 ```yaml
 ---
-name: SkillName          # Must be TitleCase
+name: skill-name          # Must be lowercase-with-hyphens, matching directory
 description: [What it does]. USE WHEN [intent triggers using OR]. [Additional capabilities].
 ---
 ```
 
 Check:
-- ✓ `name` field exists and is TitleCase
+- ✓ `name` field exists and is lowercase-with-hyphens
 - ✓ `description` field exists and is single line
 - ✓ Description includes "USE WHEN" or clear triggers
 - ✓ No syntax errors in YAML
@@ -40,14 +40,14 @@ Required structure:
 ### 5. Check Workflow Files
 
 For each file in `workflows/`:
-- ✓ Uses TitleCase.md naming (e.g., `Create.md`, not `create.md`)
+- ✓ Uses TitleCase.md naming (e.g., `Create.md`)
 - ✓ Listed in Workflow Routing table
 - ✓ Has clear structure
 
 ### 6. Check Tool Files
 
 For each file in `tools/`:
-- ✓ Uses TitleCase naming (e.g., `GenerateTool.ts`)
+- ✓ Uses kebab-case naming (e.g., `generate-tool.sh`)
 - ✓ Is executable (if shell script)
 
 ### 7. Generate Compliance Report
@@ -58,12 +58,12 @@ For each file in `tools/`:
 Validating skill: [SkillName]
 
 ✓ Directory Structure
-  ✓ Name is TitleCase: [SkillName]
+  ✓ Name is lowercase-with-hyphens: [skill-name]
   ✓ workflows/ directory exists
   ✓ tools/ directory exists
 
 ✓ SKILL.md Frontmatter
-  ✓ name: [SkillName] (TitleCase)
+  ✓ name: [skill-name] (lowercase-with-hyphens)
   ✓ description: Single line with triggers
 
 ✓ SKILL.md Body
@@ -73,7 +73,7 @@ Validating skill: [SkillName]
   ✓ Has Examples section
 
 ✓ Workflows
-  ✓ All workflows use TitleCase.md
+  ✓ All workflow files use TitleCase.md
   ✓ All listed in routing table
 
 Compliance: PASSED
@@ -91,6 +91,6 @@ Recommendations:
 ## Failure Handling
 
 If validation fails, suggest fixes:
-- Naming issues: Provide correct TitleCase names
+- Naming issues: Provide correct lowercase-with-hyphens names
 - Structure issues: Show required structure
 - Missing sections: Provide templates

@@ -1,9 +1,9 @@
 ---
-name: Createskill
+name: create-skill
 description: Skill creation framework for creating, validating, updating, or canonicalizing skills. USE WHEN user wants to create a new skill, validate skill structure, update existing skill, or fix skill compliance.
 ---
 
-# Createskill
+# Create Skill
 
 Systematic skill creation framework for building consistent, well-structured Claude Code skills.
 
@@ -16,27 +16,27 @@ Systematic skill creation framework for building consistent, well-structured Cla
 - User is working in `/home/vincent/.config/claude/skills/` directory
 - User asks about skill creation best practices or framework
 
-## TitleCase Naming Convention
+## Naming Convention
 
-**All naming must use TitleCase (PascalCase).**
+**All naming must use lowercase-with-hyphens (kebab-case).**
 
 | Component | Format | Example |
 |-----------|--------|---------|
-| Skill directory | TitleCase | `Golang`, `Homelab`, `Createskill` |
+| Skill directory | lowercase-with-hyphens | `golang`, `homelab`, `create-skill` |
 | Workflow files | TitleCase.md | `Create.md`, `UpdateInfo.md` |
 | Reference docs | TitleCase.md | `Guide.md`, `Reference.md` |
-| Tool files | TitleCase.sh | `ManageTool.sh` |
+| Tool files | kebab-case.sh | `manage-tool.sh` |
 
 **Wrong (NEVER use):**
-- `createskill`, `create-skill`, `CREATE_SKILL`
-- `create.md`, `update-info.md`, `SYNC_REPO.md`
+- `Createskill`, `CREATE_SKILL`, `CreateSkill`
+- `SYNC_REPO.md`
 
 ## Workflow Routing
 
 **When executing a workflow, output this notification directly:**
 
 ```
-Running the **WorkflowName** workflow from the **Createskill** skill...
+Running the **WorkflowName** workflow from the **create-skill** skill...
 ```
 
 | Workflow | Trigger | File |
@@ -64,13 +64,13 @@ Every skill must have:
 
 ```yaml
 ---
-name: SkillName
+name: create-skill
 description: Single-line description. USE WHEN triggers go here.
 ---
 ```
 
 **Critical Rules:**
-- `name` must be TitleCase
+- `name` must be lowercase-with-hyphens, matching the directory name
 - `description` must be ONE LINE (no newlines)
 - Include "USE WHEN" triggers in description
 
@@ -89,7 +89,7 @@ Required sections in order:
 ```
 User: "Create a skill for managing my Docker containers"
 → Invokes CreateSkill workflow
-→ Creates skill directory with TitleCase naming
+→ Creates skill directory with kebab-case naming
 → Creates SKILL.md with proper frontmatter
 → Creates workflows/ and tools/ directories
 → Generates USE WHEN triggers based on purpose
@@ -100,7 +100,7 @@ User: "Create a skill for managing my Docker containers"
 User: "Validate the golang skill"
 → Invokes ValidateSkill workflow
 → Checks SKILL.md structure and naming
-→ Verifies TitleCase naming throughout
+→ Verifies kebab-case naming for directory and name field
 → Verifies USE WHEN triggers are clear
 → Reports any compliance issues
 ```
@@ -108,9 +108,9 @@ User: "Validate the golang skill"
 ## Best Practices
 
 ### Naming
-- Use TitleCase for all directories and files
+- Use lowercase-with-hyphens for skill directories and the YAML `name` field
 - Keep names descriptive but concise
-- Match skill directory name to YAML `name` field
+- The `name` field in frontmatter must match the directory name
 
 ### Description Field
 - Keep it to ONE LINE only
@@ -120,13 +120,13 @@ User: "Validate the golang skill"
 ### Workflows
 - Name workflows with clear action verbs (Create, Update, Validate)
 - Keep workflows focused on single tasks
-- Use TitleCase.md naming
+- Use TitleCase.md naming for workflow files
 
 ### Tools
 - **Prefer shell scripts** for tools (simplicity, portability)
 - **Use Python** only when complexity requires it (complex parsing, data structures)
 - **Avoid TypeScript** - not preferred for skill tools
-- Name tools with TitleCase.sh or TitleCase.py
+- Name tools with kebab-case.sh or kebab-case.py
 - Keep tools focused and single-purpose
 
 **Dependency Management:**

@@ -1,5 +1,5 @@
 ---
-name: DocCoauthoring
+name: doc-coauthoring
 description: Guide users through structured co-authoring of documentation, proposals, specs, and written artifacts. USE WHEN user wants to write a design doc, RFC, proposal, technical spec, KEP, enhancement proposal, or co-author documentation.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Docker
+name: docker
 description: Container management with Docker and Podman. USE WHEN building images, managing containers, working with compose files, debugging containers, managing networks/volumes, scanning for vulnerabilities, or optimizing images.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: DocsDriftReview
+name: docs-drift-review
 description: Analyze repository documentation for implementation drift, stale examples, missing coverage, and reorganization opportunities. USE WHEN user says 'review docs', 'docs drift', 'stale docs', 'doc audit', 'check docs', or wants to compare documentation against implementation.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: EmacsLisp
+name: emacs-lisp
 description: Emacs Lisp development with modern tooling and best practices. USE WHEN writing Emacs configuration, developing packages, testing, linting, publishing to MELPA/ELPA, or working with Emacs Lisp code.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Email
+name: email
 description: Maildir email management with mu indexing and mbsync synchronization. USE WHEN searching emails, analyzing mail patterns, working with Maildir folders, querying personal (icloud) or work (redhat) emails, extracting email information, or managing email workflows.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: GHFixCI
+name: gh-fix-ci
 description: Inspect and fix failing GitHub Actions checks on a pull request. USE WHEN user says 'fix ci', 'fix checks', 'why is CI failing', 'debug CI', 'ci is red', or wants to diagnose and fix PR check failures.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: GHReviewBotComments
+name: gh-review-bot-comments
 description: Triage unresolved automated PR review comments from bots, classify validity, implement fixes, and reply to threads. USE WHEN user says 'bot comments', 'review bot feedback', 'triage bot reviews', 'fix bot comments', or wants to handle automated review comments on a PR.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Git
+name: git
 description: Git version control best practices and workflows. USE WHEN working with git commands, commits, branches, rebasing, or version control operations. For GitHub PR management, see the GitHub skill.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: GitHub
+name: github
 description: GitHub repository and pull request management. USE WHEN working with GitHub PRs, checking CI/CD status, reviewing pull requests, managing issues, or using gh CLI commands.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: GitHubTriage
+name: github-triage
 description: "GitHub issue and PR triage across repos and orgs. Classifies, investigates, and drafts responses with approval gates. USE WHEN user says 'triage', 'triage issues', 'triage PRs', 'github triage', or wants to process open issues/PRs across GitHub repositories."
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Golang
+name: golang
 description: Go development best practices and patterns. USE WHEN writing Go code, designing Go projects, working with Go tools, testing, or Go package development.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: GoogleWorkspace
+name: google-workspace
 description: Access Google Workspace APIs (Drive, Docs, Calendar, Gmail, Sheets, Slides, People) via local helper scripts. Handles OAuth login and direct API calls. USE WHEN user wants to search Google Drive, check calendar, search Gmail, read Google Docs, or interact with any Google Workspace service.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Handoff
+name: handoff
 description: Write or update a handoff document so another agent or engineer can continue the work with fresh context. USE WHEN user says 'handoff', 'write handoff', 'create handoff', 'pass this off', or wants to capture context for cross-agent or cross-session continuity.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Homelab
+name: homelab
 description: NixOS homelab infrastructure management for the home repository. USE WHEN working with NixOS systems, home-manager configs, networking, services, or personal infrastructure.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Jira
+name: jira
 description: Jira issue management for Red Hat issues.redhat.com. USE WHEN user mentions jira, ticket, issue, epic, sprint OR references Jira issue keys (SRVKP-1234, SRVCOM-456) OR wants to manage issue workflows, assignments, tracking.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Kubernetes
+name: kubernetes
 description: Kubernetes development and operations best practices. USE WHEN working with kubectl commands, K8s manifests, deployments, debugging pods, managing resources, RBAC, or cluster operations.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Nix
+name: nix
 description: Expert guidance on Nix, NixOS, and home-manager best practices. USE WHEN working with Nix expressions, NixOS configuration, home-manager, flakes, or Nix package development.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Nixpkgs
+name: nixpkgs
 description: Contributing to NixOS/nixpkgs repository. USE WHEN in nixpkgs repository (git remote contains NixOS/nixpkgs OR path contains github.com/NixOS/nixpkgs), reviewing PRs, updating packages, or contributing to nixpkgs.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Org
+name: org
 description: Org-mode file manipulation tools. USE WHEN user needs programmatic org-mode operations OR the TODOs skill requires org-manager tool.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Python
+name: python
 description: Python development best practices and modern tooling with uv. USE WHEN writing Python code, managing dependencies, testing, type checking, or working with Python projects.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: QuarterlyReport
+name: quarterly-report
 description: Generate a polished quarterly achievement HTML report. USE WHEN user asks for quarterly report, Q1/Q2/Q3/Q4 achievements, performance review data, or wants to summarize a quarter's work for their manager.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Rust
+name: rust
 description: Rust development best practices and patterns. USE WHEN writing Rust code, designing Rust projects, working with Cargo, testing, or Rust package development.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Slack
+name: slack
 description: Read-only Slack workspace access. USE WHEN user asks about Slack messages OR channel activity OR thread discussions OR searching Slack OR wants to catch up on conversations OR references a Slack URL.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: SystematicDebugging
+name: systematic-debugging
 description: Evidence-based debugging methodology emphasizing observation over assumptions following the scientific method. USE WHEN user reports a bug OR system behavior is unexpected OR troubleshooting issues OR investigating errors OR debugging failures. Follows observe, hypothesize, test, verify cycle with disciplined evidence gathering.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: Tekton
+name: tekton
 description: Tekton Pipelines CI/CD best practices for Kubernetes-native workflows. USE WHEN working with Tekton tasks, pipelines, triggers, building container images, GitOps integration, or cloud-native CI/CD.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: TestDrivenDevelopment
+name: test-driven-development
 description: Disciplined TDD workflow enforcing red-green-refactor cycle and the "iron law" of no production code without failing tests first. USE WHEN user wants to write tests first OR implement new feature with TDD OR fix bugs with test coverage OR explicitly requests TDD approach. Enforces systematic test-first development with verification at each step.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: TODOs
+name: todos
 description: TODO list management using org-mode. USE WHEN user wants to view, add, update, or manage TODOs in their org-mode files.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: UsingGitWorktrees
+name: using-git-worktrees
 description: Creates isolated git worktrees in XDG data directory for parallel development. USE WHEN starting feature work that needs isolation from current workspace OR before executing implementation plans OR working on multiple branches simultaneously OR need clean test environment. Creates worktrees in ~/.local/share/worktrees/<org>/<repo>/<branch>.
 ---
 

@@ -1,5 +1,5 @@
 ---
-name: WritingPlans
+name: writing-plans
 description: Creates comprehensive implementation plans with bite-sized tasks before touching code. USE WHEN user wants detailed implementation plan OR has spec/requirements for multi-step task OR needs to break down complex feature OR before starting significant coding work. Documents file paths, code examples, testing, and verification steps assuming engineer has minimal codebase context.
 ---