Claude Skills by Doddy70

Use when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.

Use when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.

Use when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

Use when the workflow needs to self-correct, improve over time, or establish feedback loops and evaluation cycles.

Use when the user asks to "analyze backlinks" or "外链分析"; profiles external referring domains, anchor-text distribution, toxic links, and competitor link gaps. Not for internal links — use internal-linking-optimizer. 外链分析/反向链接

Use when starting a new project, adding a new agent to an existing system, or setting up workflow infrastructure from scratch.

Quick summary of the last session — commands run, files changed, and what to do next.

Use when the workflow works but needs polish, or as the final step in a diagnose → fix → refine cycle before shipping.

Analyze command history to identify which skills work, which fail, and where to improve.

Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages. This skill explains *why* SEO works, not how to execute specific optimizations.

Use when the user wants to tailor a workflow for a specific industry, domain, or vertical with specialized expertise, terminology, and guardrails.

Use when the workflow feels too complex, has accumulated cruft, or has redundant steps and overlapping tools that need consolidation.

Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.

Use when the workflow feels over-engineered, has premature optimizations, unnecessary abstraction layers, or complexity beyond actual requirements.

Use when the user wants to push past conventional workflow limits with advanced performance techniques like parallel orchestration, streaming pipelines, or adaptive routing.

Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.