[Features] Import claude-skills and optimize MCP Loader

.scout/skills/claude-skills-imported/CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at:
+
+**Email:** Available through [alirezarezvani.com](https://alirezarezvani.com)
+**Website:** [alirezarezvani.com](https://alirezarezvani.com)
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

.scout/skills/claude-skills-imported/CONTRIBUTING.md

@@ -0,0 +1,244 @@
+# Contributing to Claude Code Skills
+
+Thank you for your interest in contributing! This repository is the largest open-source Claude Code skills & agent plugins library (6,800+ stars, 205 production-ready skills).
+
+**Before you start:** Read [CONVENTIONS.md](CONVENTIONS.md) — it contains the mandatory technical rules that every contribution must follow. PRs that violate conventions will be closed.
+
+---
+
+## Target Branch: `dev`
+
+**All PRs must target the `dev` branch.** PRs targeting `main` will be closed automatically.
+
+```bash
+git clone https://github.com/YOUR_USERNAME/claude-skills.git
+cd claude-skills
+git remote add upstream https://github.com/alirezarezvani/claude-skills.git
+git fetch upstream dev
+git checkout -b feature/my-skill upstream/dev
+```
+
+---
+
+## What We Accept
+
+### New Skills
+
+Add domain expertise that doesn't already exist in the repo:
+
+- Engineering tools and workflows
+- Marketing, sales, customer success patterns
+- Product management frameworks
+- Regulatory and compliance (ISO, SOC, GDPR, FDA)
+- Business functions (finance, HR, operations)
+
+**Before building:** Check existing skills to avoid overlap. Open an issue to discuss if unsure.
+
+### Improvements to Existing Skills
+
+- Better workflows and actionable patterns
+- Additional Python automation scripts
+- New reference material
+- More code examples and cross-references
+- Bug fixes in scripts or documentation
+
+### Bug Fixes
+
+- Python scripts that fail `--help`
+- Broken cross-references between skills
+- Incorrect information in reference docs
+
+---
+
+## What We Do NOT Accept
+
+| Type                                                    | Reason                              |
+| ------------------------------------------------------- | ----------------------------------- |
+| Links to external repos/tools in README                 | No 3rd party promotion              |
+| Skills requiring paid API keys                          | Must work without external services |
+| Scripts with pip dependencies                           | stdlib-only Python                  |
+| PRs that change the skill count (205)                   | Curated number                      |
+| PRs modifying `.codex/`, `.gemini/`, `marketplace.json` | Auto-generated files                |
+| Bloated diffs with fork merge history                   | Rebase on `dev` first               |
+| Generic advice without actionable frameworks            | Must be executable by an AI agent   |
+
+---
+
+## Skill Creation Guide
+
+### 1. Create the directory
+
+```bash
+# Example: new engineering skill
+mkdir -p engineering/my-new-skill/scripts
+mkdir -p engineering/my-new-skill/references
+```
+
+### 2. Write SKILL.md
+
+**Frontmatter — only `name` and `description`:**
+
+```yaml
+---
+name: 'my-new-skill'
+description: 'Use when the user asks to [specific trigger]. Covers [key capabilities].'
+---
+```
+
+> **Important:** Do NOT add `license`, `metadata`, `triggers`, `version`, `author`, or any other fields. See [CONVENTIONS.md](CONVENTIONS.md) for the full specification.
+
+**Content must be:**
+
+- Under 500 lines (move detailed content to `references/`)
+- Opinionated (recommend specific approaches)
+- Actionable (agent can execute, not just advise)
+- Include anti-patterns and cross-references sections
+
+### 3. Write Python scripts (optional but valuable)
+
+```python
+#!/usr/bin/env python3
+"""Tool Name — brief description."""
+
+import argparse
+import json
+import sys
+
+def main():
+    parser = argparse.ArgumentParser(description="Tool description")
+    parser.add_argument("input", help="Input file or value")
+    parser.add_argument("--json", action="store_true", help="Output as JSON")
+    parser.add_argument("--verbose", action="store_true", help="Verbose output")
+    args = parser.parse_args()
+
+    # Your logic here
+    result = {"status": "ok"}
+
+    if args.json:
+        print(json.dumps(result, indent=2))
+    else:
+        print(f"Result: {result['status']}")
+
+if __name__ == "__main__":
+    main()
+```
+
+**Script rules:** stdlib-only, argparse, `--help`, `--json`, proper exit codes (0/1/2). See [CONVENTIONS.md](CONVENTIONS.md) for full requirements.
+
+### 4. Add reference docs (optional)
+
+Place detailed material in `references/`:
+
+```
+my-new-skill/references/
+├── patterns.md          # Detailed patterns and examples
+├── best-practices.md    # Best practices guide
+└── decision-matrix.md   # Comparison tables
+```
+
+Reference them from SKILL.md:
+
+```markdown
+> See [references/patterns.md](references/patterns.md) for detailed patterns.
+```
+
+### 5. Validate before submitting
+
+```bash
+# Structure validation
+python3 engineering/skill-tester/scripts/skill_validator.py <your-skill-path>
+
+# Script testing
+python3 engineering/skill-tester/scripts/script_tester.py <your-skill-path> --verbose
+
+# Security audit
+python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py <your-skill-path> --strict
+```
+
+---
+
+## PR Checklist
+
+Before submitting your PR, verify:
+
+- [ ] **Targets `dev` branch** (not `main`)
+- [ ] **SKILL.md frontmatter** has only `name` + `description`
+- [ ] **SKILL.md under 500 lines** (detailed content in `references/`)
+- [ ] **All scripts pass** `python3 script.py --help`
+- [ ] **Scripts use stdlib only** (no pip dependencies)
+- [ ] **Scripts support `--json` output**
+- [ ] **Anti-patterns section** included in SKILL.md
+- [ ] **Cross-references** to related skills included
+- [ ] **No modifications** to `.codex/`, `.gemini/`, `marketplace.json`, or index files
+- [ ] **No 3rd party links** added to README
+- [ ] **Clean diff** — rebased on `dev`, no merge commit history
+- [ ] **Security audit passes** with zero CRITICAL/HIGH findings
+
+---
+
+## Commit Messages
+
+[Conventional Commits](https://www.conventionalcommits.org/) format:
+
+```
+feat(engineering): add browser-automation skill
+fix(self-improving-agent): use absolute path for hooks
+improve(tdd-guide): add per-language examples
+docs: update CONTRIBUTING.md
+```
+
+---
+
+## PR Description Template
+
+```markdown
+## Summary
+
+- What: [What does this add/change/fix?]
+- Why: [Why is this valuable?]
+
+## Checklist
+
+- [x] Targets dev branch
+- [x] SKILL.md frontmatter: name + description only
+- [x] Under 500 lines
+- [x] Scripts pass --help
+- [x] Security audit: 0 critical/high findings
+```
+
+---
+
+## After Your PR is Merged
+
+Maintainers will handle:
+
+1. Running sync scripts (Codex, Gemini, integrations)
+2. Generating docs pages
+3. Updating mkdocs.yml navigation
+4. Updating domain plugin.json counts
+5. Updating marketplace.json
+6. Merging dev → main for deployment
+
+You do NOT need to do any of these steps in your PR.
+
+---
+
+## Recognition
+
+Contributors are credited via:
+
+- `Co-Authored-By:` in commit messages
+- PR merge messages and changelogs
+- Attribution in SKILL.md when skills are improved from community submissions
+
+---
+
+## Questions?
+
+- **General:** Open a [discussion](https://github.com/alirezarezvani/claude-skills/discussions)
+- **Bugs:** Use the [issue tracker](https://github.com/alirezarezvani/claude-skills/issues)
+- **Contact:** [alirezarezvani.com](https://alirezarezvani.com)
+
+---
+
+**Full technical conventions:** [CONVENTIONS.md](CONVENTIONS.md)