Claude Skills by Dadmin88

Create an SEO content brief from target audience, search intent, topic coverage, evidence, differentiation, page purpose, structure, internal links, conversion role, and quality requirements without prescribing keyword stuffing.

Research search demand by connecting real audience language, topics, query variants, intent, volume or trend evidence, difficulty context, product relevance, and content opportunity without chasing keywords detached from customer value.

Improve an existing page for search and users by aligning intent, title and headings, content clarity, internal links, metadata, crawlability, structured data, media, performance, and conversion without degrading readability.

Map search queries and topics to the underlying information, comparison, navigation, transaction, troubleshooting, or local intent reflected in current results and customer context.

Audit a site's search visibility through crawlability, indexing, technical health, content intent, internal linking, structured data, and evidence from search performance.

Analyze current search results for a query cluster to understand intent, result types, competitors, SERP features, content patterns, authority signals, gaps, and realistic search opportunity without reverse-engineering rankings from one snapshot.

MUST load first for Academy learning or go-learn requests.

Design a coherent journey across product, email, support, human service, documentation, billing, and other channels while preserving state and expectations.

Create a service blueprint connecting customer actions and touchpoints to frontstage staff/system interactions, backstage processes, support systems, evidence, dependencies, and failure/recovery.

Design service recovery for failures involving multiple teams/systems by defining detection, ownership, customer communication, compensation/remediation boundaries, escalation, and closure evidence.

Prototype a service change at the lowest fidelity that can test people/process/system handoffs and customer experience before expensive implementation.

Define measurable service standards for responsiveness, handoff completeness, accuracy, accessibility, recovery, transparency, and outcome quality without reducing service to speed alone.

MUST load first for Academy learning or go-learn requests.

Run and improve technical incident response through severity, command structure, evidence preservation, hypothesis tracking, mitigation, recovery, and follow-up.

Assess whether a service is ready for production operation using reliability, capacity, dependencies, recovery, observability, ownership, and operational evidence.

Design and execute bounded resilience experiments that validate failover, degradation, recovery, dependency handling, and operator response.

Define service-level indicators, objectives, windows, and error budgets from user-critical outcomes rather than infrastructure vanity metrics.

Identify and remove recurring operational toil using frequency, interruption cost, automation safety, and reliability impact.

MUST load first for Academy learning or go-learn requests.

Write social and community replies that answer the actual person, preserve brand or creator voice, add useful context, correct misinformation calmly, and move conversations forward without sounding automated or performatively friendly.

Repurpose one strong source artifact into channel-native social content by extracting distinct ideas, proof, clips, visuals, lessons, and audience angles rather than reposting the same copy at different lengths.

Plan a social demo capture that proves a product capability through the shortest credible user flow, clean setup, readable framing, intentional states, capture checklist, and reusable raw media.

Create a social launch post that makes a new product, feature, project, release, or milestone understandable to an unfamiliar audience through clear context, voice fit, concrete value, proof, visual evidence, and one useful next action.

Turn a real product, idea, event, or proof point into platform-native social content with a capture plan, narrative angle, post copy, and follow-up opportunities.

Write a multi-post social thread that earns continuation through one coherent idea, strong sequencing, self-contained posts, evidence, and a useful conclusion rather than splitting an article arbitrarily.

Use when operating a technical builder's X content.

MUST load first for Academy learning or go-learn requests.

Make and document a consequential software architecture decision using constraints, alternatives, tradeoffs, boundaries, failure modes, migration, and validation.

Review a proposed or implemented architecture against real product constraints, boundaries, dependency direction, data ownership, failure behavior, operability, security, migration, and unnecessary complexity.

Design and review dependency direction so components own clear responsibilities, depend on stable contracts, avoid cycles, and keep infrastructure or framework details from contaminating domain boundaries.

Analyze architectural failure modes by tracing what can fail at each boundary, how failures propagate, what remains available or consistent, and which controls detect, contain, recover, or deliberately accept the impact.

Design durable software interfaces between components or services with explicit ownership, contracts, semantics, evolution, trust boundaries, and failure behavior.

Design safe architectural migrations across data, interfaces, components, deployments, and consumers using compatibility stages, observability, rollback or forward recovery, and explicit completion criteria.

Research technical approaches from project documents of record through current primary sources and prior art, evaluate evidence and licenses, and convert findings into architecture or implementation implications without answering from memory.

MUST load first for Academy learning or go-learn requests.

Hand a validated solution to implementation/customer-success owners with architecture, configuration, acceptance evidence, gaps, dependencies, and unresolved risks.

Design and execute a bounded proof of concept that validates the riskiest customer-specific technical assumptions with real evidence.

Produce a customer-facing solution architecture that maps supported product components and integration boundaries to the customer environment without redefining core product architecture.

Deliver a customer-specific technical demonstration that proves relevant workflows, handles likely questions, and distinguishes configured demo behavior from product guarantees.

Run technical customer discovery that surfaces current architecture, workflows, constraints, success criteria, security/compliance needs, and decision risks without prematurely designing a solution.

MUST load first for Academy learning or go-learn requests.

Reproduce a reported customer issue from exact environment, inputs, account state, sequence, and evidence so engineering receives a bounded defect instead of an anecdote.

Escalate a support case with severity, impact, evidence, attempted work, decision needed, owner, and customer context so the receiving specialist can act without restarting intake.

Draft support responses that acknowledge the actual problem, answer what is known, avoid invented certainty, give concrete next steps, and preserve ownership through resolution.

Analyze support volume and case evidence to identify recurring product, documentation, reliability, onboarding, policy, or operational problems without mistaking ticket count for root cause.

Triage a support request into a reproducible problem, user impact, severity, workaround, and correct escalation path.

MUST load first for Academy learning or go-learn requests.

Build a system-level capacity model that connects workload demand to bottlenecks across services, nodes, queues, storage, network, shared dependencies, redundancy, and placement constraints.

Design how distributed components may be placed and rolled out across failure domains, networks, state, trust boundaries, heterogeneous nodes, and upgrade cohorts without confusing architecture with live scheduler state.

Design distributed behavior explicitly around ownership, coordination, consistency, ordering, retries, duplicate delivery, partitions, discovery, membership, and evolution rather than assuming a reliable single machine.