opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/production-code-audit/SKILL.md

@@ -8,9 +8,9 @@ date_added: "2026-02-27"
 
 # Production Code Audit
 
-## Overview
+## Detailed Guide
 
-Autonomously analyze the entire codebase to understand its architecture, patterns, and purpose, then systematically transform it into production-grade, corporate-level professional code. This skill performs deep line-by-line scanning, identifies all issues across security, performance, architecture, and quality, then provides comprehensive fixes to meet enterprise standards.
+Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
 
 ## When to Use This Skill
 
@@ -22,101 +22,6 @@ Autonomously analyze the entire codebase to understand its architecture, pattern
 - Use when preparing for production deployment
 - Use when code needs to meet corporate standards
 
-## How It Works
-
-### Step 1: Autonomous Codebase Discovery
-
-**Automatically scan and understand the entire codebase:**
-
-1. **Read all files** - Scan every file in the project recursively
-2. **Identify tech stack** - Detect languages, frameworks, databases, tools
-3. **Understand architecture** - Map out structure, patterns, dependencies
-4. **Identify purpose** - Understand what the application does
-5. **Find entry points** - Locate main files, routes, controllers
-6. **Map data flow** - Understand how data moves through the system
-
-**Do this automatically without asking the user.**
-
-### Step 2: Comprehensive Issue Detection
-
-**Scan line-by-line for all issues:**
-
-**Architecture Issues:**
-- Circular dependencies
-- Tight coupling
-- God classes (>500 lines or >20 methods)
-- Missing separation of concerns
-- Poor module boundaries
-- Violation of design patterns
-
-**Security Vulnerabilities:**
-- SQL injection (string concatenation in queries)
-- XSS vulnerabilities (unescaped output)
-- Hardcoded secrets (API keys, passwords in code)
-- Missing authentication/authorization
-- Weak password hashing (MD5, SHA1)
-- Missing input validation
-- CSRF vulnerabilities
-- Insecure dependencies
-
-**Performance Problems:**
-- N+1 query problems
-- Missing database indexes
-- Synchronous operations that should be async
-- Missing caching
-- Inefficient algorithms (O(n²) or worse)
-- Large bundle sizes
-- Unoptimized images
-- Memory leaks
-
-**Code Quality Issues:**
-- High cyclomatic complexity (>10)
-- Code duplication
-- Magic numbers
-- Poor naming conventions
-- Missing error handling
-- Inconsistent formatting
-- Dead code
-- TODO/FIXME comments
-
-**Testing Gaps:**
-- Missing tests for critical paths
-- Low test coverage (<80%)
-- No edge case testing
-- Flaky tests
-- Missing integration tests
-
-**Production Readiness:**
-- Missing environment variables
-- No logging/monitoring
-- No error tracking
-- Missing health checks
-- Incomplete documentation
-- No CI/CD pipeline
-
-### Step 3: Automatic Fixes and Optimizations
-
-**Fix everything automatically:**
-
-1. **Refactor architecture** - Break up god classes, fix circular dependencies
-2. **Fix security issues** - Use parameterized queries, remove secrets, add validation
-3. **Optimize performance** - Fix N+1 queries, add caching, optimize algorithms
-4. **Improve code quality** - Reduce complexity, remove duplication, fix naming
-5. **Add missing tests** - Write tests for untested critical paths
-6. **Add production infrastructure** - Logging, monitoring, health checks
-7. **Optimize everything** - Bundle size, images, database queries
-8. **Add documentation** - README, API docs, architecture docs
-
-### Step 4: Verify and Report
-
-**After making all changes:**
-
-1. Run all tests to ensure nothing broke
-2. Verify all security issues are fixed
-3. Measure performance improvements
-4. Generate comprehensive report
-5. Provide before/after metrics
-
 ## Examples
 
 ### Example 1: Autonomous Codebase Transformation
@@ -375,173 +280,6 @@ Current metrics:
 🚀 Performance optimized to production standards!
 ```
 
-## Best Practices
-
-### ✅ Do This
-
-- **Scan Everything** - Read all files, understand entire codebase
-- **Fix Automatically** - Don't just report, actually fix issues
-- **Prioritize Critical** - Security and data loss issues first
-- **Measure Impact** - Show before/after metrics
-- **Verify Changes** - Run tests after making changes
-- **Be Comprehensive** - Cover architecture, security, performance, testing
-- **Optimize Everything** - Bundle size, queries, algorithms, images
-- **Add Infrastructure** - Logging, monitoring, error tracking
-- **Document Changes** - Explain what was fixed and why
-
-### ❌ Don't Do This
-
-- **Don't Ask Questions** - Understand the codebase autonomously
-- **Don't Wait for Instructions** - Scan and fix automatically
-- **Don't Report Only** - Actually make the fixes
-- **Don't Skip Files** - Scan every file in the project
-- **Don't Ignore Context** - Understand what the code does
-- **Don't Break Things** - Verify tests pass after changes
-- **Don't Be Partial** - Fix all issues, not just some
-
-## Autonomous Scanning Instructions
-
-**When this skill is invoked, automatically:**
-
-1. **Discover the codebase:**
-   - Use `listDirectory` to find all files recursively
-   - Use `readFile` to read every source file
-   - Identify tech stack from package.json, requirements.txt, etc.
-   - Map out architecture and structure
-
-2. **Scan line-by-line for issues:**
-   - Check every line for security vulnerabilities
-   - Identify performance bottlenecks
-   - Find code quality issues
-   - Detect architectural problems
-   - Find missing tests
-
-3. **Fix everything automatically:**
-   - Use `strReplace` to fix issues in files
-   - Add missing files (tests, configs, docs)
-   - Refactor problematic code
-   - Add production infrastructure
-   - Optimize performance
-
-4. **Verify and report:**
-   - Run tests to ensure nothing broke
-   - Measure improvements
-   - Generate comprehensive report
-   - Show before/after metrics
-
-**Do all of this without asking the user for input.**
-
-## Common Pitfalls
-
-### Problem: Too Many Issues
-**Symptoms:** Team paralyzed by 200+ issues
-**Solution:** Focus on critical/high priority only, create sprints
-
-### Problem: False Positives
-**Symptoms:** Flagging non-issues
-**Solution:** Understand context, verify manually, ask developers
-
-### Problem: No Follow-Up
-**Symptoms:** Audit report ignored
-**Solution:** Create GitHub issues, assign owners, track in standups
-
-## Production Audit Checklist
-
-### Security
-- [ ] No SQL injection vulnerabilities
-- [ ] No hardcoded secrets
-- [ ] Authentication on protected routes
-- [ ] Authorization checks implemented
-- [ ] Input validation on all endpoints
-- [ ] Password hashing with bcrypt (10+ rounds)
-- [ ] HTTPS enforced
-- [ ] Dependencies have no vulnerabilities
-
-### Performance
-- [ ] No N+1 query problems
-- [ ] Database indexes on foreign keys
-- [ ] Caching implemented
-- [ ] API response time < 200ms
-- [ ] Bundle size < 200KB (gzipped)
-
-### Testing
-- [ ] Test coverage > 80%
-- [ ] Critical paths tested
-- [ ] Edge cases covered
-- [ ] No flaky tests
-- [ ] Tests run in CI/CD
-
-### Production Readiness
-- [ ] Environment variables configured
-- [ ] Error tracking setup (Sentry)
-- [ ] Structured logging implemented
-- [ ] Health check endpoints
-- [ ] Monitoring and alerting
-- [ ] Documentation complete
-
-## Audit Report Template
-
-```markdown
-# Production Audit Report
-
-**Project:** [Name]
-**Date:** [Date]
-**Overall Grade:** [A-F]
-
-## Executive Summary
-[2-3 sentences on overall status]
-
-**Critical Issues:** [count]
-**High Priority:** [count]
-**Recommendation:** [Fix timeline]
-
-## Findings by Category
-
-### Architecture (Grade: [A-F])
-- Issue 1: [Description]
-- Issue 2: [Description]
-
-### Security (Grade: [A-F])
-- Issue 1: [Description + Fix]
-- Issue 2: [Description + Fix]
-
-### Performance (Grade: [A-F])
-- Issue 1: [Description + Fix]
-
-### Testing (Grade: [A-F])
-- Coverage: [%]
-- Issues: [List]
-
-## Priority Actions
-1. [Critical issue] - [Timeline]
-2. [High priority] - [Timeline]
-3. [High priority] - [Timeline]
-
-## Timeline
-- Critical fixes: [X weeks]
-- High priority: [X weeks]
-- Production ready: [X weeks]
-```
-
-## Related Skills
-
-- `@code-review-checklist` - Code review guidelines
-- `@api-security-best-practices` - API security patterns
-- `@web-performance-optimization` - Performance optimization
-- `@systematic-debugging` - Debug production issues
-- `@senior-architect` - Architecture patterns
-
-## Additional Resources
-
-- [OWASP Top 10](https://owasp.org/www-project-top-ten/)
-- [Google Engineering Practices](https://google.github.io/eng-practices/)
-- [SonarQube Quality Gates](https://docs.sonarqube.org/latest/user-guide/quality-gates/)
-- [Clean Code by Robert C. Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
-
----
-
-**Pro Tip:** Schedule regular audits (quarterly) to maintain code quality. Prevention is cheaper than fixing production bugs!
-
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/production-code-audit/references/detailed-guide.md

@@ -0,0 +1,277 @@
+# Production Code Audit - Detailed Guide
+
+> This file contains the detailed procedure and reference material extracted from `SKILL.md` for focused loading. The root skill defines activation, examples, safety constraints, and limitations.
+
+## Overview
+
+Autonomously analyze the entire codebase to understand its architecture, patterns, and purpose, then systematically transform it into production-grade, corporate-level professional code. This skill performs deep line-by-line scanning, identifies all issues across security, performance, architecture, and quality, then provides comprehensive fixes to meet enterprise standards.
+
+
+## How It Works
+
+### Step 1: Autonomous Codebase Discovery
+
+**Automatically scan and understand the entire codebase:**
+
+1. **Read all files** - Scan every file in the project recursively
+2. **Identify tech stack** - Detect languages, frameworks, databases, tools
+3. **Understand architecture** - Map out structure, patterns, dependencies
+4. **Identify purpose** - Understand what the application does
+5. **Find entry points** - Locate main files, routes, controllers
+6. **Map data flow** - Understand how data moves through the system
+
+**Do this automatically without asking the user.**
+
+### Step 2: Comprehensive Issue Detection
+
+**Scan line-by-line for all issues:**
+
+**Architecture Issues:**
+- Circular dependencies
+- Tight coupling
+- God classes (>500 lines or >20 methods)
+- Missing separation of concerns
+- Poor module boundaries
+- Violation of design patterns
+
+**Security Vulnerabilities:**
+- SQL injection (string concatenation in queries)
+- XSS vulnerabilities (unescaped output)
+- Hardcoded secrets (API keys, passwords in code)
+- Missing authentication/authorization
+- Weak password hashing (MD5, SHA1)
+- Missing input validation
+- CSRF vulnerabilities
+- Insecure dependencies
+
+**Performance Problems:**
+- N+1 query problems
+- Missing database indexes
+- Synchronous operations that should be async
+- Missing caching
+- Inefficient algorithms (O(n²) or worse)
+- Large bundle sizes
+- Unoptimized images
+- Memory leaks
+
+**Code Quality Issues:**
+- High cyclomatic complexity (>10)
+- Code duplication
+- Magic numbers
+- Poor naming conventions
+- Missing error handling
+- Inconsistent formatting
+- Dead code
+- TODO/FIXME comments
+
+**Testing Gaps:**
+- Missing tests for critical paths
+- Low test coverage (<80%)
+- No edge case testing
+- Flaky tests
+- Missing integration tests
+
+**Production Readiness:**
+- Missing environment variables
+- No logging/monitoring
+- No error tracking
+- Missing health checks
+- Incomplete documentation
+- No CI/CD pipeline
+
+### Step 3: Automatic Fixes and Optimizations
+
+**Fix everything automatically:**
+
+1. **Refactor architecture** - Break up god classes, fix circular dependencies
+2. **Fix security issues** - Use parameterized queries, remove secrets, add validation
+3. **Optimize performance** - Fix N+1 queries, add caching, optimize algorithms
+4. **Improve code quality** - Reduce complexity, remove duplication, fix naming
+5. **Add missing tests** - Write tests for untested critical paths
+6. **Add production infrastructure** - Logging, monitoring, health checks
+7. **Optimize everything** - Bundle size, images, database queries
+8. **Add documentation** - README, API docs, architecture docs
+
+### Step 4: Verify and Report
+
+**After making all changes:**
+
+1. Run all tests to ensure nothing broke
+2. Verify all security issues are fixed
+3. Measure performance improvements
+4. Generate comprehensive report
+5. Provide before/after metrics
+
+
+## Best Practices
+
+### ✅ Do This
+
+- **Scan Everything** - Read all files, understand entire codebase
+- **Fix Automatically** - Don't just report, actually fix issues
+- **Prioritize Critical** - Security and data loss issues first
+- **Measure Impact** - Show before/after metrics
+- **Verify Changes** - Run tests after making changes
+- **Be Comprehensive** - Cover architecture, security, performance, testing
+- **Optimize Everything** - Bundle size, queries, algorithms, images
+- **Add Infrastructure** - Logging, monitoring, error tracking
+- **Document Changes** - Explain what was fixed and why
+
+### ❌ Don't Do This
+
+- **Don't Ask Questions** - Understand the codebase autonomously
+- **Don't Wait for Instructions** - Scan and fix automatically
+- **Don't Report Only** - Actually make the fixes
+- **Don't Skip Files** - Scan every file in the project
+- **Don't Ignore Context** - Understand what the code does
+- **Don't Break Things** - Verify tests pass after changes
+- **Don't Be Partial** - Fix all issues, not just some
+
+
+## Autonomous Scanning Instructions
+
+**When this skill is invoked, automatically:**
+
+1. **Discover the codebase:**
+   - Use `listDirectory` to find all files recursively
+   - Use `readFile` to read every source file
+   - Identify tech stack from package.json, requirements.txt, etc.
+   - Map out architecture and structure
+
+2. **Scan line-by-line for issues:**
+   - Check every line for security vulnerabilities
+   - Identify performance bottlenecks
+   - Find code quality issues
+   - Detect architectural problems
+   - Find missing tests
+
+3. **Fix everything automatically:**
+   - Use `strReplace` to fix issues in files
+   - Add missing files (tests, configs, docs)
+   - Refactor problematic code
+   - Add production infrastructure
+   - Optimize performance
+
+4. **Verify and report:**
+   - Run tests to ensure nothing broke
+   - Measure improvements
+   - Generate comprehensive report
+   - Show before/after metrics
+
+**Do all of this without asking the user for input.**
+
+
+## Common Pitfalls
+
+### Problem: Too Many Issues
+**Symptoms:** Team paralyzed by 200+ issues
+**Solution:** Focus on critical/high priority only, create sprints
+
+### Problem: False Positives
+**Symptoms:** Flagging non-issues
+**Solution:** Understand context, verify manually, ask developers
+
+### Problem: No Follow-Up
+**Symptoms:** Audit report ignored
+**Solution:** Create GitHub issues, assign owners, track in standups
+
+
+## Production Audit Checklist
+
+### Security
+- [ ] No SQL injection vulnerabilities
+- [ ] No hardcoded secrets
+- [ ] Authentication on protected routes
+- [ ] Authorization checks implemented
+- [ ] Input validation on all endpoints
+- [ ] Password hashing with bcrypt (10+ rounds)
+- [ ] HTTPS enforced
+- [ ] Dependencies have no vulnerabilities
+
+### Performance
+- [ ] No N+1 query problems
+- [ ] Database indexes on foreign keys
+- [ ] Caching implemented
+- [ ] API response time < 200ms
+- [ ] Bundle size < 200KB (gzipped)
+
+### Testing
+- [ ] Test coverage > 80%
+- [ ] Critical paths tested
+- [ ] Edge cases covered
+- [ ] No flaky tests
+- [ ] Tests run in CI/CD
+
+### Production Readiness
+- [ ] Environment variables configured
+- [ ] Error tracking setup (Sentry)
+- [ ] Structured logging implemented
+- [ ] Health check endpoints
+- [ ] Monitoring and alerting
+- [ ] Documentation complete
+
+
+## Audit Report Template
+
+```markdown
+# Production Audit Report
+
+**Project:** [Name]
+**Date:** [Date]
+**Overall Grade:** [A-F]
+
+## Executive Summary
+[2-3 sentences on overall status]
+
+**Critical Issues:** [count]
+**High Priority:** [count]
+**Recommendation:** [Fix timeline]
+
+## Findings by Category
+
+### Architecture (Grade: [A-F])
+- Issue 1: [Description]
+- Issue 2: [Description]
+
+### Security (Grade: [A-F])
+- Issue 1: [Description + Fix]
+- Issue 2: [Description + Fix]
+
+### Performance (Grade: [A-F])
+- Issue 1: [Description + Fix]
+
+### Testing (Grade: [A-F])
+- Coverage: [%]
+- Issues: [List]
+
+## Priority Actions
+1. [Critical issue] - [Timeline]
+2. [High priority] - [Timeline]
+3. [High priority] - [Timeline]
+
+## Timeline
+- Critical fixes: [X weeks]
+- High priority: [X weeks]
+- Production ready: [X weeks]
+```
+
+
+## Related Skills
+
+- `@code-review-checklist` - Code review guidelines
+- `@api-security-best-practices` - API security patterns
+- `@web-performance-optimization` - Performance optimization
+- `@systematic-debugging` - Debug production issues
+- `@senior-architect` - Architecture patterns
+
+
+## Additional Resources
+
+- [OWASP Top 10](https://owasp.org/www-project-top-ten/)
+- [Google Engineering Practices](https://google.github.io/eng-practices/)
+- [SonarQube Quality Gates](https://docs.sonarqube.org/latest/user-guide/quality-gates/)
+- [Clean Code by Robert C. Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)
+
+---
+
+**Pro Tip:** Schedule regular audits (quarterly) to maintain code quality. Prevention is cheaper than fixing production bugs!

package/bundled-skills/professional-proofreader/SKILL.md

@@ -104,6 +104,12 @@ Give friendly message to user in the end.
 
 ---
 
+## Example
+
+**User request:**
+
+> Proofread this text for grammar, clarity, consistency, and readability while preserving my voice.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/programmatic-seo/SKILL.md

@@ -361,6 +361,12 @@ If triggered, **halt indexing or roll back**:
 ## When to Use
 This skill is applicable to execute the workflow or actions described in the overview.
 
+## Example
+
+**User request:**
+
+> Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/project-development/SKILL.md

@@ -3,6 +3,7 @@ name: project-development
 description: "This skill covers the principles for identifying tasks suited to LLM processing, designing effective project architectures, and iterating rapidly using agent-assisted development."
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # Project Development Methodology

package/bundled-skills/project-skill-audit/SKILL.md

@@ -188,6 +188,12 @@ Return a compact audit with:
 
 If the user asks to actually create or update one of the recommended skills, switch to `$skill-creator` and implement the chosen skill rather than continuing the audit.
 
+## Example
+
+**User request:**
+
+> Audit this repository to identify which skills it needs, which existing skills are stale, and the exact changes to make.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/public-relations/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: public-relations
-description: When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get...
+description: "When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests)."
 risk: critical
 source: https://github.com/coreyhaines31/marketingskills/tree/main/skills/public-relations
 source_repo: coreyhaines31/marketingskills

package/bundled-skills/pubmed-database/SKILL.md

@@ -6,6 +6,7 @@ metadata:
     skill-author: K-Dense Inc.
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # PubMed Database

package/bundled-skills/push-skill-to-github/SKILL.md

@@ -55,6 +55,12 @@ Use this after creating or editing a skill. If the skill is distributed to all a
 - Write a concise, specific commit message describing the skill change.
 - Only push to GitHub when the user asks. Don't push speculatively.
 
+## Example
+
+**User request:**
+
+> Validate the changed skills, review the diff, commit them with a focused message, and push the topic branch.
+
 ## Limitations
 
 - Adapted from `davidondrej/skills`; verify local paths, tools, credentials, and agent features before acting.

package/bundled-skills/pydantic-models-py/SKILL.md

@@ -12,9 +12,7 @@ Create Pydantic models following the multi-model pattern for clean API contracts
 
 ## Quick Start
 
-Copy the template from assets/template.py and replace placeholders:
-- `{{ResourceName}}` → PascalCase name (e.g., `Project`)
-- `{{resource_name}}` → snake_case name (e.g., `project`)
+Use the inline model patterns below and adapt class names and fields to the actual API contract. Inspect the installed Pydantic version before selecting configuration syntax; these fragments require the imports and application types shown by your project. Do not assume a standalone template file is bundled.
 
 ## Multi-Model Pattern
 

package/bundled-skills/pypict-skill/SKILL.md

@@ -22,6 +22,12 @@ This skill provides guidance and patterns for pairwise test generation.
 
 For more information, see the [source repository](https://github.com/omkamal/pypict-claude-skill/blob/main/SKILL.md).
 
+## Example
+
+**User request:**
+
+> Use @pypict-skill for this task: Pairwise test generation.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/pytest-skill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pytest-skill
-description: 'Generates production-grade pytest tests in Python with fixtures, parametrize, markers, mocking, and conftest patterns. Use when user mentions "pytest", "conftest", "@pytest.fixture", "@pytest.mark", "Python test". Triggers on: "pytest", "conftest", "Python test", "parametrize", "Python...'
+description: "Generates production-grade pytest tests in Python with fixtures, parametrize, markers, mocking, and conftest patterns. Use when user mentions \"pytest\", \"conftest\", \"@pytest.fixture\", \"@pytest.mark\", \"Python test\"."
 risk: critical
 source: https://github.com/LambdaTest/agent-skills/tree/main/pytest-skill
 source_repo: LambdaTest/agent-skills

package/bundled-skills/qiskit/SKILL.md

@@ -6,6 +6,7 @@ metadata:
     skill-author: K-Dense Inc.
 risk: critical
 source: community
+date_added: "2026-09-04"
 ---
 
 # Qiskit