Repository Maintenance Protocol

To ensure consistency and quality, the following steps MUST be performed for every single change involving skills or documentation.

1. Skill Creation & Modification

Check Duplicates: Before adding a skill, check skills_index.json or ls skills/ to ensure it doesn't exist.
Folder Structure: Each skill must have its own folder in skills/<skill-name>.
SKILL.md: Every skill directory MUST contain a SKILL.md file with valid frontmatter:
```
---
name: Skill Name
description: Brief description.
---
```

Running the scripts is MANDATORY after any change to skills/.

Validate Skills: Run the validation script to check for formatting errors.
```
python3 scripts/validate_skills.py
```
Generate Index: Update skills_index.json. This is the source of truth for the agent.
```
python3 scripts/generate_index.py
```

The README.md does not auto-update. You must manually sync it with the index.

About / Introduction: Update the total count in the opening paragraph and blockquote.
- > **The Ultimate Collection of [X]+ Agentic Skills...
- ...library of **[X] high-performance skills**...
Features & Categories Table: If the new skill fits a category, update the table in # Features & Categories.
Full Skill Registry Table: Add the new skill to the main table.
- Format: | **[Name]** | [Description] | [Path] |
- Verify alphabetical order.
Credits & Sources: If the skill was imported from a community repo, add a credit link in # Credits & Sources.
- Example: - **[repo-name](url)**: Source for [skill-name].

Check Status: git status to see what changed.
Add All Files: Ensure new skill folders are added (git add skills/).
Commit: Use a descriptive Conventional Commit message (e.g., feat: add new security skills, docs: update readme count).
Push: git push to origin. NEVER FORGET THIS.

Walkthrough: Update walkthrough.md in the brain/artifact directory to reflect the session's achievements.