mirror of
https://github.com/alirezarezvani/claude-skills.git
synced 2026-10-10 03:27:56 +00:00
Same root cause as #587/#591 — Claude Code's runtime loader rejects array-form skills paths like ["./content-production", "./ai-seo", ...] even when each entry is a valid subdirectory containing SKILL.md. `claude plugin validate` accepts them but the loader does not. The proven canonical layout (used by self-improving-agent in #536): <plugin>/ ├── .claude-plugin/plugin.json skills: "./skills" └── skills/ ├── <skill-1>/SKILL.md ├── <skill-2>/SKILL.md └── ... Restructured 9 multi-skill domain plugins: - business-growth (4 skills moved) - c-level-advisor (28) - engineering (36) - engineering-team (32) - finance (2) - marketing-skill (43) - product-team (12) - project-management (8) - ra-qm-team (13) Also fixed standalone plugins that had root SKILL.md + ./skills/ subdir (agenthub, autoresearch-agent, executive-mentor, playwright-pro). The loader rejected them despite skills="./skills" because of the conflicting root SKILL.md (compare self-improving-agent which works because PR #536 moved its root SKILL.md). Moved each root SKILL.md into ./skills/<name>/. Restored standalone plugin folders to their original paths after the multi-skill restructure swept them into parent skills/ directories (marketplace.json source paths require original locations). Removed 7 orphaned marketplace entries that pointed to skill folders without their own plugin.json (content-creator, demand-gen, fullstack-engineer, aws-architect, product-manager, scrum-master, skill-security-auditor) — these were already non-functional. Bumped patch versions on every changed plugin and synced marketplace.json. Marketplace now lists 29 working plugins (down from 36). After merge: users run `/plugin marketplace update claude-code-skills` followed by `/plugin update --all` to pick up the working layout.
60 lines
No EOL
2.6 KiB
Text
60 lines
No EOL
2.6 KiB
Text
DATABASE INDEX OPTIMIZATION REPORT
|
|
==================================================
|
|
|
|
ANALYSIS SUMMARY
|
|
----------------
|
|
Tables Analyzed: 6
|
|
Query Patterns: 15
|
|
Existing Indexes: 12
|
|
New Recommendations: 8
|
|
High Priority: 4
|
|
Redundancy Issues: 2
|
|
|
|
HIGH PRIORITY RECOMMENDATIONS (4)
|
|
----------------------------------
|
|
1. orders: Optimize multi-column WHERE conditions: user_id, status, created_at
|
|
Columns: user_id, status, created_at
|
|
Benefit: Very High
|
|
SQL: CREATE INDEX idx_orders_user_status_created ON orders (user_id, status, created_at);
|
|
|
|
2. products: Optimize WHERE category_id = AND is_active = queries
|
|
Columns: category_id, is_active
|
|
Benefit: High
|
|
SQL: CREATE INDEX idx_products_category_active ON products (category_id, is_active);
|
|
|
|
3. order_items: Optimize JOIN with products table on product_id
|
|
Columns: product_id
|
|
Benefit: High (frequent JOINs)
|
|
SQL: CREATE INDEX idx_order_items_product_join ON order_items (product_id);
|
|
|
|
4. product_reviews: Covering index for WHERE + ORDER BY optimization
|
|
Columns: product_id, created_at
|
|
Benefit: High (eliminates table lookups for SELECT)
|
|
SQL: CREATE INDEX idx_product_reviews_covering_product_created ON product_reviews (product_id, created_at) INCLUDE (rating, review_text);
|
|
|
|
REDUNDANCY ISSUES (2)
|
|
---------------------
|
|
• DUPLICATE: Indexes 'idx_users_email' and 'unique_users_email' are identical
|
|
Recommendation: Drop one of the duplicate indexes
|
|
SQL: DROP INDEX idx_users_email;
|
|
|
|
• OVERLAPPING: Index 'idx_products_category' overlaps 85% with 'idx_products_category_active'
|
|
Recommendation: Consider dropping 'idx_products_category' as it's largely covered by 'idx_products_category_active'
|
|
SQL: DROP INDEX idx_products_category;
|
|
|
|
PERFORMANCE IMPACT ANALYSIS
|
|
----------------------------
|
|
Queries to be optimized: 12
|
|
High impact optimizations: 6
|
|
Estimated insert overhead: 40%
|
|
|
|
RECOMMENDED CREATE INDEX STATEMENTS
|
|
------------------------------------
|
|
1. CREATE INDEX idx_orders_user_status_created ON orders (user_id, status, created_at);
|
|
2. CREATE INDEX idx_products_category_active ON products (category_id, is_active);
|
|
3. CREATE INDEX idx_order_items_product_join ON order_items (product_id);
|
|
4. CREATE INDEX idx_product_reviews_covering_product_created ON product_reviews (product_id, created_at) INCLUDE (rating, review_text);
|
|
5. CREATE INDEX idx_products_price_brand ON products (price, brand);
|
|
6. CREATE INDEX idx_orders_status_created ON orders (status, created_at);
|
|
7. CREATE INDEX idx_categories_parent_active ON categories (parent_id, is_active);
|
|
8. CREATE INDEX idx_product_reviews_user_created ON product_reviews (user_id, created_at); |