mirror of
https://github.com/alirezarezvani/claude-skills.git
synced 2026-08-28 04:24:58 +00:00
Compare commits
No commits in common. "main" and "v2.0.0" have entirely different histories.
5512 changed files with 42779 additions and 583813 deletions
File diff suppressed because it is too large
Load diff
|
|
@ -1,10 +0,0 @@
|
|||
[2026-05-02T19:56:41Z] Hook fired. Input bytes: 1694
|
||||
[2026-05-02T19:56:41Z] ERR trap at line 67; failing open
|
||||
[2026-05-02T20:01:48Z] Hook fired. Input bytes: 1323
|
||||
[2026-05-02T20:01:48Z] ERR trap at line 67; failing open
|
||||
[2026-05-02T20:14:49Z] Hook fired. Input bytes: 1638
|
||||
[2026-05-02T20:14:49Z] ERR trap at line 67; failing open
|
||||
[2026-05-02T20:33:10Z] Hook fired. Input bytes: 11247
|
||||
[2026-05-02T20:33:10Z] ERR trap at line 67; failing open
|
||||
[2026-05-02T20:34:42Z] Hook fired. Input bytes: 1846
|
||||
[2026-05-02T20:34:42Z] ERR trap at line 67; failing open
|
||||
|
|
@ -12,7 +12,6 @@
|
|||
/git:cm → Stage and commit (no push)
|
||||
/git:cp → Stage, commit, and push
|
||||
/git:pr → Create pull request
|
||||
/git:clean → Delete merged branches (local + remote)
|
||||
```
|
||||
|
||||
### Quality Gates
|
||||
|
|
@ -20,7 +19,6 @@
|
|||
```
|
||||
/review → Run local quality checks
|
||||
/security-scan → Run security validation
|
||||
/update-docs → Post-creation sync (CLI platforms, marketplace, docs, GitHub Pages)
|
||||
```
|
||||
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,17 +0,0 @@
|
|||
---
|
||||
description: "Deep-dive feature repair — systematically fix an entire feature/module. Usage: /focused-fix <feature-path>"
|
||||
---
|
||||
|
||||
Systematically repair the feature/module at `$ARGUMENTS` using the focused-fix 5-phase protocol.
|
||||
|
||||
If `$ARGUMENTS` is empty, ask which feature/module to fix.
|
||||
|
||||
Read `engineering/focused-fix/SKILL.md` and execute ALL 5 phases IN ORDER:
|
||||
|
||||
1. **SCOPE** — Map the feature boundary (all files, entry points, internal files)
|
||||
2. **TRACE** — Map inbound + outbound dependencies across the entire codebase
|
||||
3. **DIAGNOSE** — Check code, runtime, tests, logs, config. Assign risk labels (HIGH/MED/LOW). Confirm root causes with evidence.
|
||||
4. **FIX** — Repair in order: deps → types → logic → tests → integration. One fix at a time, test after each. 3-strike escalation if fixes cascade.
|
||||
5. **VERIFY** — Run all feature tests + consumer tests. Summarize changes.
|
||||
|
||||
**Iron Law:** No fixes before completing Phase 3. No exceptions.
|
||||
|
|
@ -1,59 +0,0 @@
|
|||
---
|
||||
description: Clean up merged branches locally and on remote, keeping only main, dev, and gh-pages.
|
||||
---
|
||||
|
||||
Clean up stale branches that have been merged or are no longer needed.
|
||||
|
||||
## Steps
|
||||
|
||||
1. **List local branches** to delete (excluding `main`, `dev`, `gh-pages`):
|
||||
|
||||
```bash
|
||||
git branch | grep -v -E '^\*|main$|dev$|gh-pages$'
|
||||
```
|
||||
|
||||
Report what will be deleted. If no branches found, say "No local branches to clean" and skip to step 3.
|
||||
|
||||
2. **Delete local branches** that are fully merged:
|
||||
|
||||
```bash
|
||||
git branch -d <branch-name>
|
||||
```
|
||||
|
||||
If a branch is not fully merged, report it to the user and ask whether to force-delete. Do NOT force-delete without confirmation.
|
||||
|
||||
3. **List remote branches** to delete (excluding `main`, `dev`, `gh-pages`, `HEAD`):
|
||||
|
||||
```bash
|
||||
git branch -r | grep -v -E 'origin/main$|origin/dev$|origin/gh-pages$|origin/HEAD'
|
||||
```
|
||||
|
||||
Report what will be deleted. If no branches found, say "No remote branches to clean" and skip to step 5.
|
||||
|
||||
4. **Confirm with the user** before deleting remote branches. Show the full list and wait for approval. Then delete:
|
||||
|
||||
```bash
|
||||
git push origin --delete <branch-names>
|
||||
```
|
||||
|
||||
5. **Prune stale remote refs**:
|
||||
|
||||
```bash
|
||||
git remote prune origin
|
||||
```
|
||||
|
||||
6. **Report final state**:
|
||||
|
||||
```bash
|
||||
git branch # local
|
||||
git branch -r # remote
|
||||
```
|
||||
|
||||
Present a summary:
|
||||
|
||||
| Item | Count |
|
||||
|------|-------|
|
||||
| Local branches deleted | N |
|
||||
| Remote branches deleted | N |
|
||||
| Remaining local | main, dev |
|
||||
| Remaining remote | origin/main, origin/dev, origin/gh-pages |
|
||||
|
|
@ -1,153 +0,0 @@
|
|||
---
|
||||
description: Run the full 8-phase plugin audit pipeline on a skill directory.
|
||||
---
|
||||
|
||||
Run the comprehensive plugin audit pipeline on the skill at `$ARGUMENTS`. If no argument provided, ask the user for the skill path.
|
||||
|
||||
Execute all 8 phases sequentially. Auto-fix non-critical issues. Only prompt the user for critical decisions (external dependencies, security findings, breaking changes).
|
||||
|
||||
## Phase 1: Discovery
|
||||
|
||||
1. Verify `$ARGUMENTS` exists and contains `SKILL.md`. If not, error and stop.
|
||||
2. Read `SKILL.md` frontmatter — extract `name`, `description`, `Category`, `Tier`.
|
||||
3. Detect components:
|
||||
- `scripts/*.py` → Python tools (count them)
|
||||
- `references/*.md` → reference docs (count them)
|
||||
- `assets/` → templates/samples
|
||||
- `expected_outputs/` → test fixtures
|
||||
- `agents/*.md` → embedded agents
|
||||
- `skills/*/SKILL.md` → sub-skills (compound skill)
|
||||
- `.claude-plugin/plugin.json` → standalone plugin
|
||||
- `settings.json` → command registrations
|
||||
4. Detect domain from path (`engineering/`, `product-team/`, `marketing-skill/`, etc.)
|
||||
5. Search `commands/` for a `.md` file matching the skill name.
|
||||
6. Display discovery summary.
|
||||
|
||||
## Phase 2: Structure Validation
|
||||
|
||||
Run:
|
||||
```bash
|
||||
python3 engineering/skill-tester/scripts/skill_validator.py $ARGUMENTS --json
|
||||
```
|
||||
|
||||
Parse JSON. If score < 75:
|
||||
- Auto-fix missing frontmatter fields, missing section headings, missing directories.
|
||||
- Re-run. If still < 75, mark as FAIL but continue collecting results.
|
||||
|
||||
## Phase 3: Quality Scoring
|
||||
|
||||
Run:
|
||||
```bash
|
||||
python3 engineering/skill-tester/scripts/quality_scorer.py $ARGUMENTS --detailed --json
|
||||
```
|
||||
|
||||
Parse JSON. If score < 60, report improvement roadmap items.
|
||||
|
||||
## Phase 4: Script Testing
|
||||
|
||||
If `$ARGUMENTS/scripts/` contains `.py` files, run:
|
||||
```bash
|
||||
python3 engineering/skill-tester/scripts/script_tester.py $ARGUMENTS --json --verbose
|
||||
```
|
||||
|
||||
All scripts must PASS. If any script uses external imports, **ask the user** whether the dependency is acceptable.
|
||||
|
||||
## Phase 5: Security Audit
|
||||
|
||||
Run:
|
||||
```bash
|
||||
python3 engineering/skill-security-auditor/scripts/skill_security_auditor.py $ARGUMENTS --strict --json
|
||||
```
|
||||
|
||||
Zero CRITICAL or HIGH findings required. **Do NOT auto-fix security issues** — report them to the user with file, line, pattern, and recommended fix.
|
||||
|
||||
## Phase 6: Marketplace & Plugin Compliance
|
||||
|
||||
### 6a. plugin.json
|
||||
If `$ARGUMENTS/.claude-plugin/plugin.json` exists:
|
||||
- Must be valid JSON
|
||||
- Only allowed fields: `name`, `description`, `version`, `author`, `homepage`, `repository`, `license`, `skills`
|
||||
- Version must be `2.1.2`
|
||||
- Auto-fix version mismatches and remove extra fields.
|
||||
|
||||
### 6b. settings.json
|
||||
If `$ARGUMENTS/settings.json` exists:
|
||||
- Must be valid JSON
|
||||
- Version must match repo version
|
||||
- Each command in `commands` field must have a matching `commands/*.md` file
|
||||
|
||||
### 6c. Marketplace entry
|
||||
Check `.claude-plugin/marketplace.json` for an entry with `source` matching `./$ARGUMENTS`. Verify version and name match.
|
||||
|
||||
### 6d. Domain plugin.json
|
||||
Check the parent domain's `.claude-plugin/plugin.json` — verify skill count in description matches actual count. Auto-fix stale counts.
|
||||
|
||||
## Phase 7: Ecosystem Integration
|
||||
|
||||
### 7a. Cross-platform sync
|
||||
Verify skill appears in `.codex/skills-index.json` and `.gemini/skills-index.json`. If missing:
|
||||
```bash
|
||||
python3 scripts/sync-codex-skills.py --verbose
|
||||
python3 scripts/sync-gemini-skills.py --verbose
|
||||
```
|
||||
|
||||
### 7b. Command integration
|
||||
If the skill has associated commands, verify:
|
||||
- Command `.md` has valid frontmatter
|
||||
- Command references the correct skill
|
||||
- Command is in `mkdocs.yml` nav
|
||||
Auto-fix missing nav entries.
|
||||
|
||||
### 7c. Agent integration
|
||||
Check for embedded agents in `$ARGUMENTS/agents/`. Search `agents/` for cs-* agents that reference this skill. Verify references resolve.
|
||||
|
||||
### 7d. Cross-skill dependencies
|
||||
Read SKILL.md for references to other skills (`../` paths, "Related Skills" sections). Verify each referenced skill exists.
|
||||
|
||||
## Phase 8: Domain Code Review
|
||||
|
||||
Based on the domain, apply the appropriate agent's review criteria:
|
||||
|
||||
| Domain | Agent | Focus |
|
||||
|--------|-------|-------|
|
||||
| `engineering/` or `engineering-team/` | cs-senior-engineer | Architecture, code quality, CI/CD |
|
||||
| `product-team/` | cs-product-manager | PRD quality, user stories, RICE |
|
||||
| `marketing-skill/` | cs-content-creator | Content quality, SEO, brand voice |
|
||||
| `ra-qm-team/` | cs-quality-regulatory | Compliance, audit trail, regulatory |
|
||||
| `business-growth/` | cs-growth-strategist | Growth metrics, revenue impact |
|
||||
| `finance/` | cs-financial-analyst | Model accuracy, metric definitions |
|
||||
| Other | cs-senior-engineer | General code review |
|
||||
|
||||
Read the agent's `.md` file for review criteria. Apply those criteria to the skill's SKILL.md, scripts, and references. Check:
|
||||
- Workflows are actionable and complete
|
||||
- Scripts solve the stated problem
|
||||
- References contain accurate domain knowledge
|
||||
- No broken internal links
|
||||
- Attribution present where required
|
||||
|
||||
## Final Report
|
||||
|
||||
Present all results in a structured summary:
|
||||
|
||||
```
|
||||
╔══════════════════════════════════════════════════════════════╗
|
||||
║ PLUGIN AUDIT REPORT: {skill_name} ║
|
||||
╠══════════════════════════════════════════════════════════════╣
|
||||
║ Phase 1 — Discovery ✅ {type}, {domain} ║
|
||||
║ Phase 2 — Structure ✅ {score}/100 ({level}) ║
|
||||
║ Phase 3 — Quality ✅ {score}/100 ({grade}) ║
|
||||
║ Phase 4 — Scripts ✅ {n}/{n} PASS ║
|
||||
║ Phase 5 — Security ✅ PASS (0 critical, 0 high) ║
|
||||
║ Phase 6 — Marketplace ✅ plugin.json valid ║
|
||||
║ Phase 7 — Ecosystem ✅ synced ║
|
||||
║ Phase 8 — Code Review ✅ passed ║
|
||||
║ ║
|
||||
║ VERDICT: ✅ PASS ║
|
||||
║ Auto-fixes: {n} | Warnings: {n} | Action items: {n} ║
|
||||
╚══════════════════════════════════════════════════════════════╝
|
||||
```
|
||||
|
||||
**Verdict rules:**
|
||||
- All phases pass → **PASS**
|
||||
- Only warnings → **PASS WITH WARNINGS**
|
||||
- Any blocker (structure <75, quality <60, script FAIL, security CRITICAL/HIGH, invalid plugin.json) → **FAIL**
|
||||
|
|
@ -1,97 +0,0 @@
|
|||
---
|
||||
description: Scan and optimize docs for SEO — meta tags, readability, keywords, broken links, sitemap.
|
||||
---
|
||||
|
||||
Run the SEO auditor on documentation files. Target path: `$ARGUMENTS` (default: all docs/ and root README.md).
|
||||
|
||||
If `$ARGUMENTS` is `--report-only`, scan without making changes.
|
||||
|
||||
Execute all 7 phases. Auto-fix non-destructive issues. Never change URLs. Preserve content on high-ranking pages.
|
||||
|
||||
## Phase 1: Discovery
|
||||
|
||||
Find all target markdown files:
|
||||
- `docs/**/*.md` — all documentation pages
|
||||
- `README.md` files in domain root directories
|
||||
- If `$ARGUMENTS` specifies a path, scope to that path only
|
||||
|
||||
For each file, extract current state: `title:` frontmatter, `description:` frontmatter, H1, H2s, word count, link count. Store as baseline for the report.
|
||||
|
||||
Identify recently changed files: `git log --oneline -2 --name-only -- docs/ README.md`
|
||||
|
||||
## Phase 2: Meta Tags
|
||||
|
||||
For each file with YAML frontmatter:
|
||||
|
||||
**Title** (`title:` field):
|
||||
- Must be 50-60 characters
|
||||
- Must contain a primary keyword
|
||||
- Must be unique across all pages
|
||||
- Auto-fix generic titles using domain context
|
||||
|
||||
**Description** (`description:` field):
|
||||
- Must be 120-160 characters
|
||||
- Must contain primary keyword
|
||||
- Must be unique — no duplicates
|
||||
- Auto-fix from SKILL.md frontmatter or first paragraph
|
||||
|
||||
Run SEO checker on built HTML pages:
|
||||
```bash
|
||||
python3 marketing-skill/skills/seo-audit/scripts/seo_checker.py --file site/{path}/index.html
|
||||
```
|
||||
|
||||
## Phase 3: Content Quality
|
||||
|
||||
**Heading structure:** One H1 per page, no skipped levels, keywords in headings.
|
||||
|
||||
**Readability:** Run content scorer:
|
||||
```bash
|
||||
python3 marketing-skill/skills/content-production/scripts/content_scorer.py {file}
|
||||
```
|
||||
Target: readability ≥ 70, structure ≥ 60.
|
||||
|
||||
**AI detection** (on non-generated files only):
|
||||
```bash
|
||||
python3 marketing-skill/skills/content-humanizer/scripts/humanizer_scorer.py {file}
|
||||
```
|
||||
Flag pages < 50. Fix AI clichés: "delve", "leverage", "it's important to note", "comprehensive".
|
||||
|
||||
**Do NOT rewrite** pages ranking well — only fix critical issues on those.
|
||||
|
||||
## Phase 4: Keywords
|
||||
|
||||
Check each page has its primary keyword in: title, description, H1, first paragraph, at least one H2.
|
||||
|
||||
Keyword density: 1-2% for primary. Flag and reduce if > 3%.
|
||||
|
||||
**Never change existing URLs.** Only optimize content and meta tags.
|
||||
|
||||
## Phase 5: Links
|
||||
|
||||
**Internal links:** Verify all `[text](url)` targets exist. Fix broken links.
|
||||
|
||||
**Duplicate content:**
|
||||
```bash
|
||||
grep -rh '^description:' docs/**/*.md | sort | uniq -d
|
||||
```
|
||||
Make each duplicate unique.
|
||||
|
||||
**Orphan pages:** Find pages not in `mkdocs.yml` nav. Add them.
|
||||
|
||||
## Phase 6: Sitemap
|
||||
|
||||
Rebuild the site to regenerate sitemap:
|
||||
```bash
|
||||
mkdocs build
|
||||
```
|
||||
|
||||
Analyze the sitemap:
|
||||
```bash
|
||||
python3 marketing-skill/skills/site-architecture/scripts/sitemap_analyzer.py site/sitemap.xml
|
||||
```
|
||||
|
||||
Verify all pages appear, no duplicates, no broken URLs.
|
||||
|
||||
## Phase 7: Report
|
||||
|
||||
Present a summary showing: pages scanned, issues found, auto-fixes applied, manual review items, broken links fixed, orphans resolved, sitemap URL count. List preserved pages that were not modified.
|
||||
|
|
@ -1,228 +0,0 @@
|
|||
---
|
||||
description: Update all the documentation related files.
|
||||
---
|
||||
|
||||
After completing any skill creation, agent creation, or command creation in this repository, run the full post-creation sync pipeline below. Execute every step — never skip a task. If something is unclear or a step fails, ask the user for guidance before continuing.
|
||||
|
||||
---
|
||||
|
||||
## Step 1: Inventory what changed
|
||||
|
||||
Scan the working tree to identify what was added, modified, or deleted:
|
||||
|
||||
```bash
|
||||
git status --short
|
||||
```
|
||||
|
||||
Classify each change:
|
||||
- **New skill** — a new folder containing `SKILL.md` under a domain directory
|
||||
- **New agent** — a new `.md` file under `agents/`
|
||||
- **New command** — a new `.md` file under `commands/`
|
||||
- **Modified skill/agent/command** — updated existing files
|
||||
- **Deleted skill/agent/command** — removed files
|
||||
|
||||
Report the inventory to the user before proceeding.
|
||||
|
||||
---
|
||||
|
||||
## Step 2: Cross-platform CLI sync
|
||||
|
||||
Ensure all platforms have compatible versions of every skill, agent, and command.
|
||||
|
||||
### 2a. Codex CLI
|
||||
|
||||
Run the Codex sync script to regenerate symlinks and the skills index:
|
||||
|
||||
```bash
|
||||
python3 scripts/sync-codex-skills.py --verbose
|
||||
```
|
||||
|
||||
Verify the output: check `.codex/skills-index.json` for correct `total_skills` count and that new skills appear in the index.
|
||||
|
||||
### 2b. Gemini CLI
|
||||
|
||||
Run the Gemini sync script:
|
||||
|
||||
```bash
|
||||
python3 scripts/sync-gemini-skills.py --verbose
|
||||
```
|
||||
|
||||
Verify: check `.gemini/skills-index.json` for correct total count. New skills, agents, and commands should all have corresponding entries and symlinks under `.gemini/skills/`.
|
||||
|
||||
### 2c. OpenClaw
|
||||
|
||||
Verify that `scripts/openclaw-install.sh` will pick up the new skills. The install script uses the same directory structure, so no separate sync is needed — but confirm the new skill directories are not excluded by any filter in the script.
|
||||
|
||||
Report sync results (skill counts per platform) to the user.
|
||||
|
||||
---
|
||||
|
||||
## Step 3: Claude Code plugin marketplace
|
||||
|
||||
### 3a. Domain-level plugin.json
|
||||
|
||||
For each domain that had changes, update the domain's `.claude-plugin/plugin.json`:
|
||||
- Update `description` with accurate skill/tool/reference counts
|
||||
- Update `version` if needed
|
||||
- Verify `source` paths are correct
|
||||
|
||||
Domain plugin.json locations:
|
||||
- `marketing-skill/.claude-plugin/plugin.json`
|
||||
- `engineering-team/.claude-plugin/plugin.json`
|
||||
- `engineering/.claude-plugin/plugin.json`
|
||||
- `product-team/.claude-plugin/plugin.json`
|
||||
- `c-level-advisor/.claude-plugin/plugin.json`
|
||||
- `project-management/.claude-plugin/plugin.json`
|
||||
- `ra-qm-team/.claude-plugin/plugin.json`
|
||||
- `business-growth/.claude-plugin/plugin.json`
|
||||
- `finance/.claude-plugin/plugin.json`
|
||||
|
||||
### 3b. Root marketplace.json
|
||||
|
||||
Update `.claude-plugin/marketplace.json`:
|
||||
- Update the top-level `metadata.description` with accurate total counts (skills, tools, references, agents, commands)
|
||||
- If a new individual skill plugin entry is needed (for standalone install), add it to the `plugins` array following the existing pattern
|
||||
- Update `keywords` arrays if new domains or capabilities were added
|
||||
- Verify all `source` paths point to valid directories
|
||||
|
||||
---
|
||||
|
||||
## Step 4: Update documentation files
|
||||
|
||||
### 4a. Root CLAUDE.md
|
||||
|
||||
Update `/CLAUDE.md` (the root project instructions):
|
||||
- **Current Scope** line: update skill, tool, reference, agent, and command counts
|
||||
- **Repository Structure** comment counts (agents, commands, skills per domain)
|
||||
- **Navigation Map** table: verify all domain entries are current
|
||||
- **Current Version** section: add a bullet if significant changes were made
|
||||
- **Roadmap** section: update counts if needed
|
||||
|
||||
### 4b. Domain-level CLAUDE.md files
|
||||
|
||||
For each domain that had changes, update its `CLAUDE.md`:
|
||||
- Skill count and list
|
||||
- Script/tool count
|
||||
- Agent references
|
||||
- Command references
|
||||
- Any new cross-domain integrations
|
||||
|
||||
Domain CLAUDE.md locations:
|
||||
- `agents/CLAUDE.md`
|
||||
- `marketing-skill/CLAUDE.md`
|
||||
- `product-team/CLAUDE.md`
|
||||
- `engineering-team/CLAUDE.md`
|
||||
- `c-level-advisor/CLAUDE.md`
|
||||
- `project-management/CLAUDE.md`
|
||||
- `ra-qm-team/CLAUDE.md`
|
||||
- `business-growth/CLAUDE.md`
|
||||
- `finance/CLAUDE.md`
|
||||
- `standards/CLAUDE.md`
|
||||
- `templates/CLAUDE.md`
|
||||
|
||||
### 4c. Root README.md
|
||||
|
||||
Update `/README.md`:
|
||||
- Badge counts (Skills, Agents, Commands)
|
||||
- Tagline/intro paragraph skill count
|
||||
- Skills Overview table (domain rows with correct counts)
|
||||
- Quick Install section (install commands, skill counts in comments)
|
||||
- Python Analysis Tools section (tool count, add examples for new tools)
|
||||
- FAQ section (update any counts mentioned)
|
||||
|
||||
### 4d. docs/index.md (GitHub Pages homepage)
|
||||
|
||||
Update `docs/index.md`:
|
||||
- `description` meta tag
|
||||
- Hero subtitle skill count
|
||||
- Grid cards (skills, tools, agents, commands counts)
|
||||
- Domain cards (skill counts per domain, links)
|
||||
|
||||
### 4e. docs/getting-started.md
|
||||
|
||||
Update `docs/getting-started.md`:
|
||||
- `description` meta tag
|
||||
- Available Bundles table (skill counts per bundle)
|
||||
- Python Tools section (tool count)
|
||||
- FAQ answers (any count references)
|
||||
|
||||
---
|
||||
|
||||
## Step 5: Regenerate GitHub Pages
|
||||
|
||||
Run the docs generation script to create/update all MkDocs pages:
|
||||
|
||||
```bash
|
||||
python3 scripts/generate-docs.py
|
||||
```
|
||||
|
||||
This generates pages for:
|
||||
- Every skill (from SKILL.md files)
|
||||
- Every agent (from agents/*.md)
|
||||
- Every command (from commands/*.md)
|
||||
- Index pages for skills, agents, and commands sections
|
||||
|
||||
### 5a. Update mkdocs.yml navigation
|
||||
|
||||
Open `mkdocs.yml` and update the `nav:` section:
|
||||
- Add new skill pages under the correct domain section
|
||||
- Add new agent pages under the Agents section
|
||||
- Add new command pages under the Commands section
|
||||
- Update `site_description` with current counts
|
||||
|
||||
### 5b. Verify the build
|
||||
|
||||
```bash
|
||||
python3 -m mkdocs build 2>&1 | tail -5
|
||||
```
|
||||
|
||||
The build should complete without errors. Warnings about relative links in SKILL.md files are expected and can be ignored (they reference skill-internal paths like `references/` and `scripts/`).
|
||||
|
||||
Report the build result and page count to the user.
|
||||
|
||||
---
|
||||
|
||||
## Step 6: Consistency verification
|
||||
|
||||
Run a final consistency check across all updated files:
|
||||
|
||||
1. **Count consistency** — Verify the same skill/agent/command/tool counts appear in:
|
||||
- Root CLAUDE.md
|
||||
- Root README.md
|
||||
- docs/index.md
|
||||
- docs/getting-started.md
|
||||
- .claude-plugin/marketplace.json
|
||||
|
||||
2. **Path validation** — Verify all `source` paths in marketplace.json point to existing directories
|
||||
|
||||
3. **New script verification** — If new Python scripts were added, verify they run:
|
||||
```bash
|
||||
python3 path/to/new/script.py --help
|
||||
```
|
||||
|
||||
4. **Frontmatter check** — Verify all new SKILL.md, agent, and command files have valid YAML frontmatter with at minimum `name` and `description` fields
|
||||
|
||||
Report any inconsistencies found and fix them before finishing.
|
||||
|
||||
---
|
||||
|
||||
## Step 7: Summary report
|
||||
|
||||
Present a summary to the user:
|
||||
|
||||
| Item | Status |
|
||||
|------|--------|
|
||||
| New skills added | [list] |
|
||||
| New agents added | [list] |
|
||||
| New commands added | [list] |
|
||||
| Codex CLI sync | count |
|
||||
| Gemini CLI sync | count |
|
||||
| OpenClaw compatible | yes/no |
|
||||
| Marketplace updated | yes/no |
|
||||
| CLAUDE.md files updated | [count]/[total] |
|
||||
| README.md updated | yes/no |
|
||||
| GitHub Pages regenerated | [page count] pages |
|
||||
| MkDocs build | pass/fail |
|
||||
| Consistency check | pass/fail |
|
||||
|
||||
Ask the user if they want to commit and push the changes.
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
{
|
||||
"$schema": "https://json.schemastore.org/claude-code-settings.json",
|
||||
"extraKnownMarketplaces": {
|
||||
"ecc": {
|
||||
"source": {
|
||||
"source": "github",
|
||||
"repo": "affaan-m/ECC"
|
||||
}
|
||||
}
|
||||
},
|
||||
"enabledPlugins": {
|
||||
"ecc@ecc": true
|
||||
}
|
||||
}
|
||||
|
|
@ -1,47 +0,0 @@
|
|||
{
|
||||
"name": "claude-code-skills",
|
||||
"version": "2.12.0",
|
||||
"description": "388 production-ready skills across 20 domains — engineering, marketing, product, compliance, C-level advisory, research, business operations, and more. 727 Python tools, 842 reference guides, 118 agents (cs-* + personas), 150 slash commands, 99 marketplace plugins. The largest open-source skills library for AI coding agents.",
|
||||
"author": {
|
||||
"name": "Alireza Rezvani",
|
||||
"url": "https://alirezarezvani.com"
|
||||
},
|
||||
"homepage": "https://alirezarezvani.github.io/claude-skills/",
|
||||
"repository": "https://github.com/alirezarezvani/claude-skills",
|
||||
"license": "MIT",
|
||||
"keywords": [
|
||||
"openai-codex",
|
||||
"codex-plugin",
|
||||
"claude-code",
|
||||
"agent-skills",
|
||||
"engineering",
|
||||
"marketing",
|
||||
"product",
|
||||
"compliance",
|
||||
"devops",
|
||||
"security",
|
||||
"ai-agents"
|
||||
],
|
||||
"skills": "./.codex/skills/",
|
||||
"interface": {
|
||||
"type": "cli",
|
||||
"composerIcon": "./assets/icon.png",
|
||||
"displayName": "Claude Code Skills",
|
||||
"shortDescription": "388 production-ready skills for AI coding agents across 20 domains",
|
||||
"longDescription": "The largest open-source skills library for AI coding agents. 388 skills covering engineering (architecture, DevOps, security, AI/ML, agent tooling), marketing (SEO, AEO, CRO, content), product management, C-level advisory, regulatory compliance (ISO 13485, SOC 2, GDPR), project management, research and research operations, business operations, commercial, finance, and personal productivity. Includes 727 stdlib-only Python CLI tools, 842 reference guides, 118 orchestration agents, and 150 slash commands. Works with Codex, Claude Code, Gemini CLI, Cursor, Hermes Agent, Mistral Vibe, and 7 more tools.",
|
||||
"developerName": "Alireza Rezvani",
|
||||
"category": "Coding",
|
||||
"capabilities": [
|
||||
"Read",
|
||||
"Write"
|
||||
],
|
||||
"websiteURL": "https://alirezarezvani.github.io/claude-skills/",
|
||||
"defaultPrompt": [
|
||||
"Design an AWS architecture for my project",
|
||||
"Run a security pen test on this codebase",
|
||||
"Create a product requirements document",
|
||||
"Audit this page for accessibility (WCAG 2.2)"
|
||||
],
|
||||
"brandColor": "#0969da"
|
||||
}
|
||||
}
|
||||
File diff suppressed because it is too large
Load diff
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/a11y-audit/skills/a11y-audit
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/ab-test-setup
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/ad-creative
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/skills/adversarial-reviewer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/aeo
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../ra-qm-team/skills/agent-decision-receipts
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/agent-designer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/agent-harness/skills/agent-harness
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../agent-launcher/skills/agent-launcher-orchestrator
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/agent-memory/skills/agent-memory
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/agent-protocol
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/agent-workflow-designer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/agenthub/skills/agenthub
|
||||
|
|
@ -1 +1 @@
|
|||
../../product-team/agile-product-owner/skills/agile-product-owner
|
||||
../../product-team/agile-product-owner
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../compliance-os/skills/ai-act-readiness
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/skills/ai-security
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../compliance-os/skills/aims-audit
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/analytics-tracking
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../productivity/andreessen/skills/andreessen
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/api-design-reviewer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/api-test-suite-builder
|
||||
|
|
@ -1 +1 @@
|
|||
../../marketing-skill/skills/app-store-optimization
|
||||
../../marketing-skill/app-store-optimization
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../product-team/apple-hig-expert/skills/apple-hig-expert
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/autoresearch-agent/skills/ar-resume
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/autoresearch-agent/skills/ar-status
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/arquiteto-de-empresa/skills/arquiteto-de-empresa
|
||||
|
|
@ -1 +1 @@
|
|||
../../project-management/skills/atlassian-admin
|
||||
../../project-management/atlassian-admin
|
||||
|
|
@ -1 +1 @@
|
|||
../../project-management/skills/atlassian-templates
|
||||
../../project-management/atlassian-templates
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/autoresearch-agent/skills/autoresearch-agent
|
||||
|
|
@ -1 +1 @@
|
|||
../../engineering-team/skills/aws-solution-architect
|
||||
../../engineering-team/aws-solution-architect
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/skills/azure-cloud-architect
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/behuman/skills/behuman
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/agenthub/skills/board
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/board-deck-builder
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/board-meeting
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/executive-mentor/skills/board-prep
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/boardroom
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/book-to-skill/skills/book-to-skill
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/boost-asio-pro
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/brand-guidelines
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/brief
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/browser-automation
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/playwright-pro/skills/browserstack
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../business-growth/skills/business-growth-skills
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../finance/business-investment-advisor/skills/business-investment-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/business-name-fit
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../business-operations/skills/business-operations-skills
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/c-level-agents
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/c-level-skills
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/caio-review
|
||||
|
|
@ -1 +1 @@
|
|||
../../marketing-skill/skills/campaign-analytics
|
||||
../../marketing-skill/campaign-analytics
|
||||
|
|
@ -1 +1 @@
|
|||
../../ra-qm-team/skills/capa-officer
|
||||
../../ra-qm-team/capa-officer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../business-operations/skills/capacity-planner
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../productivity/capture/skills/capture
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/caveman/skills/caveman
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/cco-review
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/cdo-review
|
||||
|
|
@ -1 +1 @@
|
|||
../../c-level-advisor/skills/ceo-advisor
|
||||
../../c-level-advisor/ceo-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/cfo-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/cfo-review
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/executive-mentor/skills/challenge
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/change-management
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/changelog-generator
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../commercial/skills/channel-economics
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/chaos-engineering/skills/chaos-engineering
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/chief-ai-officer-advisor/skills/chief-ai-officer-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/chief-customer-officer-advisor/skills/chief-customer-officer-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/chief-data-officer-advisor/skills/chief-data-officer-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/chief-of-staff
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/chro-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/churn-prevention
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/ci-cd-pipeline-builder
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/ciso-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/ciso-review
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/claude-coach/skills/claude-coach
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../research-ops/skills/clinical-research
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering-team/skills/cloud-security
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/cmo-advisor
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-agents/skills/cmo-review
|
||||
|
|
@ -1 +1 @@
|
|||
../../engineering-team/skills/code-reviewer
|
||||
../../engineering-team/code-reviewer
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../product-team/code-to-prd/skills/code-to-prd
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/code-tour/skills/code-tour
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/skills/codebase-onboarding
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../marketing-skill/skills/cold-email
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../engineering/collab-proof/skills/collab-proof
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../commercial/skills/commercial-forecaster
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../commercial/skills/commercial-policy
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../commercial/skills/commercial-skills
|
||||
|
|
@ -1 +0,0 @@
|
|||
../../c-level-advisor/skills/company-os
|
||||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Add table
Reference in a new issue