docs: modernize README and add SKILL_CHAINS navigation

[teekoo5]

README.md:

• Wrap badges in

  for better visual grouping

• Add role-based navigation table with emojis
• Convert "Why Skill Chains?" to include intro paragraph and ROI callout
• Implement expandable
  Details

  sections for "What's Included"
• Restructure Quick Start with numbered steps
• Convert CLI commands to table format
• Organize documentation into Strategy vs Technical sections
• Consolidate Community & Support section
• Remove redundant sections (verbose troubleshooting, "What's a Skill Chain?" example)
• Add centered footer with heart emoji

docs/SKILL_CHAINS.md:

• Add comprehensive Quick Navigation section
• Group 28 recipes by domain (Sales, Customer Success, Growth, Product, Brand, Operations)
• Add jump links and brief descriptions for each recipe

.pre-commit-config.yaml:

• Update Black formatter to use python3.11 (was python3.10)
• Remove baseline requirement from detect-secrets (file doesn't exist)
• Fixes pre-commit hook compatibility

All metrics remain accurate (765 skills, 383 executable, 382 context, 28 recipes).

Pull Request

Description

Type of Change

• 🎯 New skill
• ✨ Feature enhancement
• 🐛 Bug fix
• 📚 Documentation update
• 🔧 Build/tooling improvement
• ♻️ Refactoring (no functional changes)
• 🧪 Test addition/improvement
• 🔒 Security fix

Related Issues

Closes #
Related to #

Changes Made

Testing

Test Coverage

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Test coverage ≥60% for new code
• All existing tests pass

Test Plan

# Commands used for testing
pytest tests/unit/test_my_feature.py
pytest tests/integration/

Test Results:

Security Review

Risk Assessment

• Low Risk - Read-only operations, no sensitive data
• Medium Risk - Data modifications, moderate impact
• High Risk - System changes, significant impact
• Critical Risk - High-privilege operations, security implications

Security Checklist

• Input validation implemented
• No hardcoded credentials or secrets
• Proper error handling (no information leakage)
• Rate limiting considered (if applicable)
• Authentication/authorization reviewed
• Dependencies scanned for vulnerabilities
• Reviewed against SECURITY_POLICY.md

Security Considerations

Skill-Specific Information

Skill Details

• Skill Name: skill-name
• Domain: domain-name
• Risk Level: Low/Medium/High/Critical

Skill Schema

• Schema follows standard format
• All parameters documented
• Examples provided
• Validation rules defined

Eval Harness Results

# Command used
python scripts/batch_eval_skills.py --skill-name skill-name

# Results

Breaking Changes

• No breaking changes
• Breaking changes (describe below)

Breaking Changes:

Migration Guide:

Code Quality

• Code follows project style guidelines
• Linting passes (black, flake8, eslint)
• Pre-commit hooks pass
• No new warnings introduced
• Documentation updated (if needed)

Performance Impact

• No significant performance impact
• Performance improvement (describe below)
• Performance degradation (describe below, provide justification)

Performance Notes:

Documentation

• README.md updated (if needed)
• CHANGELOG.md updated
• Inline code comments added
• API documentation updated
• Examples/tutorials updated

Checklist

• I have read CONTRIBUTING.md
• My code follows the project's code style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Additional Context

Screenshots/Recordings

---

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT License.