Loading...
Loading...
Found 57 Skills
Check or verify whether a Skill complies with best practice specifications, covering naming conventions, directory structure, metadata integrity, temporary file cleanup, and dependency format validation. It provides detailed checklists, automatic repair suggestions, and report templates, and also supports integrity checks and automatic repair of skill library documentation. It is suitable for quality verification after creating or modifying a Skill
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
Diagnose and fix oh-my-claudecode installation issues
Salesforce debugging and troubleshooting skill with log analysis, governor limit detection, and agentic fix suggestions. Parse debug logs, identify performance bottlenecks, analyze stack traces, and automatically suggest fixes.
[DevOps & Infra] Run linters and fix issues for backend or frontend
Novel Logic/Plot Review, applicable to user requests such as "Help me check if there are bugs in my novel", "Check if there are timeline contradictions", "Check if characters are OOC", "Find plot conflicts between different parts", "Sort out whether foreshadowings are resolved", "Check the rationality of novel plots", "Check if there are plot loopholes", "Character behaviors are inconsistent with their personalities", "Check if the timeline is correct", "Find contradictions in the novel", "Help me sort out all foreshadowings", "Novel plot bug check", "Logical loophole troubleshooting", etc. It detects issues such as timeline conflicts, logical loopholes, character OOC, and missing foreshadowings. **Performs word count checks to ensure chapter word counts meet standards**, **generates a detailed issue list and automatically fixes all issues, with the fixed results directly modifying the chapters/ directory and automatically backing up the original files to .sumeru/write/original/ before modification**, **uses sub-Agents for parallel processing during batch review, with each Agent responsible for a maximum of 3 chapters**
System health check (MOT) for skills, agents, hooks, and memory
Review InboxMate demos waiting for QA. Finds CRM opportunities at SCREENING with demoStatus=PENDING_REVIEW, opens each demo link, checks quality, and flags as OK_TO_SEND or NEEDS_FIX with a note explaining why.
Validate Business Requirements Documents (BRD) against Layer 1 MVP schema standards
Diagnose and fix oh-my-codex installation issues
Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. TRIGGER when: user says 'scan my code', 'check for security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). DO NOT TRIGGER when: user wants to fix code without scanning, or asks about installation/configuration.
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.