Claude Skills by paulasilvatech

Assess and migrate cross-cloud workloads to Azure with assessment reports and code conversion, supporting Lambda to Functions, Beanstalk, Heroku, and App Engine to App Service, and Fargate, Kubernetes, Cloud Run, or Spring Boot to Container Apps. Use when the user asks to migrate Lambda to Functions, move from AWS or GCP to Azure, migrate Beanstalk, Heroku, or App Engine, convert Cloud Run or Fargate workloads, move ECS, GKE, or EKS to Container Apps, or plan a cross-cloud migration.

Assess and upgrade Azure workloads between plans, tiers, or SKUs, and modernize Azure SDK dependencies in source code. Use when the user wants to upgrade Consumption to Flex Consumption, change an Azure Functions hosting plan or function app SKU, migrate App Service to Container Apps, modernize legacy Azure Java SDKs from com.microsoft.azure to com.azure, or migrate Azure Cache for Redis to Azure Managed Redis.

Instrument Azure-hosted web apps with Azure Application Insights telemetry by choosing auto-instrumentation or code instrumentation for ASP.NET Core, Node.js, or Python. Use when the user wants to enable telemetry, observe app health, create an App Insights resource, or wire instrumentation into a webapp.

Manage Azure cost by querying actual spend, forecasting future spending, and optimizing resources to reduce waste. Use when the user asks about Azure costs or bills, wants a cost breakdown, asks how much they are spending, wants to forecast spending, optimize or reduce spend, find orphaned resources, rightsize VMs, investigate a cost spike, or lower storage and AKS costs.

Debug Azure production issues with AppLens, Azure Monitor, resource health, and safe triage across App Service, Container Apps, Functions, AKS, virtual machines, and messaging. Use when the user needs to troubleshoot production incidents, high CPU or deployment failures, VM connectivity such as RDP, SSH, or blocked NSG rules, AKS problems such as pod pending, crashloop, node not ready, or image pull failures, cold starts, failing health probes, resource health, or Event Hubs and Service Bus S...

Deploys and operates Prometheus, Grafana, Loki, and Alertmanager for Open Horizons observability. Use this skill when deploying the monitoring stack, configuring dashboards, validating alert rules, checking metrics, reviewing SLO signals, or troubleshooting observability behavior.

Assess and improve the reliability posture of Azure Functions and Azure App Service workloads by scanning deployed resources for zone redundancy, ZRS storage, health probes, and multi-region failover, then driving staged remediation through CLI or infrastructure-as-code patches with user confirmation. Use when the user asks to assess or check reliability, review zone redundancy or multi-region failover, improve high availability or disaster recovery, find single points of failure, or evaluate...

Migrate a Backstage adopter app from the legacy frontend system to the new extension-based frontend system through hybrid and full-migration phases. Use when converting createApp, feature discovery, routes, sidebar, APIs, themes, or app-level frontend compatibility.

Migrate a Backstage app from the old frontend system to the new one. Use this skill when converting an app to use the new extension-based frontend system, including the hybrid migration phase and the full migration of routes, sidebar, plugins, APIs, themes, and other app-level concerns.

Install and use Backstage's AI catalog model for AiResource skills and rules plus mcp-server API entities, ownership, lifecycle, relationships, and source locations. Use when cataloging AI skills, governance rules, agents, or MCP servers.

Create or assess a standalone Backstage adopter application with version-aware prerequisites, package layout, first-run configuration, and baseline validation. Use when starting a Backstage app, reinstalling an app shell, or checking whether a repository is a valid adopter app.

Design, edit, validate, and troubleshoot Backstage app configuration, environment overlays, schemas, secrets, integrations, and frontend visibility. Use when working with app-config YAML, BACKSTAGE_ENV, config:check, deployment overrides, or configuration errors.

Configure, review, and troubleshoot Backstage sign-in, identity resolvers, auth providers, delegated third-party access, callbacks, and permissions. Use when setting up GitHub, Microsoft, guest, proxy, or custom auth providers or fixing login failures.

Run and compare the Backstage catalog query performance battery against a safe database replica, capture PostgreSQL plans and buffers, detect regressions, and update the baseline. Use when changing catalog queries, indexes, schemas, or database performance behavior.

Model, register, discover, validate, and troubleshoot Backstage Software Catalog entities, providers, processors, ownership, relations, locations, and lifecycle. Use when handling catalog-info YAML, entity ingestion, org discovery, duplicate entities, or catalog governance.

Prepare, implement, validate, and document contributions to backstage/backstage or a close fork using targeted tests, exact root typechecking, formatting, linting, API reports, changesets, DCO, and Apache headers. Use when changing Backstage core packages, plugins, docs, or contributor workflows.

Configure, secure, and validate Backstage technical integrations with GitHub, Azure and Azure DevOps, and ServiceNow across catalog discovery, events, software templates, CI/CD views, incidents, and provider credentials. Use when setting up or troubleshooting integrations outside user sign-in.

Choose and implement Backstage framework extension points, core backend services, frontend blueprints, service refs, modules, lifecycle, auth, permissions, schedulers, tracing, metrics, and generated API references. Use when designing plugin architecture or selecting supported framework APIs.

Install, configure, authorize, and troubleshoot Backstage Kubernetes frontend and backend plugins, cluster discovery, entity annotations, authentication, permissions, proxies, custom resources, and service-owner views. Use when working with Kubernetes tabs, clusters, pods, or integration errors.

Register typed Backstage backend actions and expose selected actions as authenticated MCP tools with schemas, attributes, permissions, filters, server instructions, and well-known action validation. Use when configuring the Actions Registry, Actions Service, MCP Actions Backend, or AI tool exposure.

Install, configure, emit, process, route, and troubleshoot Backstage notifications and optional real-time signals. Use when handling user or group notifications, external emitters, email or Slack processors, scaffolder notifications, settings, topics, or delivery failures.

Operate, monitor, troubleshoot, and harden production Backstage services, databases, schedulers, integrations, health endpoints, logs, and deployments. Use when handling startup failures, readiness problems, database errors, provider refresh issues, performance incidents, or production runbooks.

Design, implement, test, and troubleshoot Backstage permission policies, basic and resource permissions, conditional decisions, rules, frontend authorization, and plugin integration. Use when implementing RBAC, ABAC, resource filtering, action visibility, or fixing authorization failures.

Plan, architect, scaffold, validate, and prepare custom Backstage plugins and modules using official Backstage documentation. Use when the user asks for new, legacy, or dual frontend plugins, backend plugins, backend modules, catalog processors, entity providers, scaffolder actions, search collators, auth providers, permission policies, TechDocs addons, common packages, node packages, plugin ADRs, architecture, validation, or community publication preparation.

Install, configure, extend, operate, and troubleshoot Backstage Search frontends, engines, collators, indices, result extensions, filters, schedules, and permissions. Use when working with search pages, Catalog or TechDocs indexing, custom collators, Postgres or Elasticsearch, or missing results.

Design, implement, validate, and troubleshoot Backstage Software Templates, custom actions, Golden Paths, skeleton rendering, repository publication, and catalog registration. Use when working with template.yaml, scaffolder actions, parameters, step outputs, or template execution failures.

Configure, build, preview, publish, migrate, and troubleshoot Backstage TechDocs and MkDocs content. Use when handling techdocs-ref annotations, mkdocs.yml, local or external builders, object-storage publishers, CI generation, broken docs, or wiki-to-TechDocs migration.

Plan, execute, and validate Backstage application or plugin dependency upgrades with release-aware package alignment, migrations, config review, changesets, and rollback. Use when bumping Backstage versions, resolving package skew, adopting new systems, or preparing an upgrade PR.

Plan, apply, inspect, or uninstall the Backstage Expert repository workspace kit for adopter or core profiles. Use when publishing bundled instructions, VS Code prompts, and the optional Backstage safety hook into a target repository.

Migrate Backstage app or plugin UI from Material-UI to Backstage UI with version-checked component mappings, CSS setup, accessibility, analytics, styling, and visual validation. Use when replacing @material-ui imports, MUI icons, makeStyles, or adopting BUI.

Migrate Backstage plugins from Material-UI (MUI) to Backstage UI (BUI). Use this skill when migrating components, updating imports, replacing styling patterns, or converting MUI components to their BUI equivalents.

Migrate a Backstage backend plugin from a hand-written Express router to the repository's typed OpenAPI server tooling while preserving routes, auth, permissions, errors, tests, and optional client generation. Use when onboarding createOpenApiRouter or modernizing a router with OpenAPI.

Use this skill when the user wants to migrate an existing Backstage backend plugin's hand-written Express router to the typed OpenAPI tooling. Optionally, can also add typed client generation and migrate router tests to the OpenAPI test wrapper.

Instrument Backstage frontend plugins with meaningful Analytics API events and tests while avoiding duplicate BUI navigation events or UI noise. Use when adding or reviewing captureEvent, AnalyticsContext, event taxonomy, noTrack overrides, or analytics behavior.

Instrument a Backstage frontend plugin with analytics events using the Backstage Analytics API. Use this skill when adding, reviewing, or extending event capture (`captureEvent`, `AnalyticsContext`) in plugin components, deciding whether an interaction warrants an event, or writing tests for analytics behavior.

Fully migrate a Backstage frontend plugin to the new frontend system and remove legacy support. Use when performing internal or intentionally breaking migrations from createPlugin to createFrontendPlugin, new route refs, blueprints, PageLayout, and legacy dependency removal.

Fully migrate a Backstage plugin to the new frontend system, dropping all old system support. Use this skill for internal plugins that only need to run in a single app, or when you are ready to remove backward compatibility entirely.

Add new frontend-system support to an existing Backstage plugin while retaining its legacy entry point. Use when published or shared plugins need dual compatibility, alpha exports, PageBlueprint extensions, route reuse, and both old and new app consumers.

Add new frontend system support to an existing Backstage plugin while keeping the old system working. Use this skill for published or shared plugins that need to work in both old and new frontend system apps.

Migrate a Backstage adopter app from the legacy frontend system to the new extension-based frontend system through hybrid and full-migration phases. Use when converting createApp, feature discovery, routes, sidebar, APIs, themes, or app-level frontend compatibility.

Migrate a Backstage app from the old frontend system to the new one. Use this skill when converting an app to use the new extension-based frontend system, including the hybrid migration phase and the full migration of routes, sidebar, plugins, APIs, themes, and other app-level concerns.

Install and use Backstage's AI catalog model for AiResource skills and rules plus mcp-server API entities, ownership, lifecycle, relationships, and source locations. Use when cataloging AI skills, governance rules, agents, or MCP servers.

Apply Backstage AI Catalog, Actions Registry, and MCP Actions conventions. Use when editing AiResource or mcp-server entities, backend actions, or MCP Actions configuration.

Create or assess a standalone Backstage adopter application with version-aware prerequisites, package layout, first-run configuration, and baseline validation. Use when starting a Backstage app, reinstalling an app shell, or checking whether a repository is a valid adopter app.

Design, edit, validate, and troubleshoot Backstage app configuration, environment overlays, schemas, secrets, integrations, and frontend visibility. Use when working with app-config YAML, BACKSTAGE_ENV, config:check, deployment overrides, or configuration errors.

Apply Backstage adopter-app composition and configuration conventions. Use when editing app packages, backend packages, backstage.json, or app-config files.

Apply Backstage sign-in, identity resolver, delegated access, service auth, and permission-boundary conventions. Use when editing auth configuration or provider modules.

Configure, review, and troubleshoot Backstage sign-in, identity resolvers, auth providers, delegated third-party access, callbacks, and permissions. Use when setting up GitHub, Microsoft, guest, proxy, or custom auth providers or fixing login failures.

Run and compare the Backstage catalog query performance battery against a safe database replica, capture PostgreSQL plans and buffers, detect regressions, and update the baseline. Use when changing catalog queries, indexes, schemas, or database performance behavior.

Model, register, discover, validate, and troubleshoot Backstage Software Catalog entities, providers, processors, ownership, relations, locations, and lifecycle. Use when handling catalog-info YAML, entity ingestion, org discovery, duplicate entities, or catalog governance.