Loading...
Loading...
Found 8,980 Skills
Expert knowledge for Chaos Studio development including troubleshooting, limits & quotas, security, configuration, and integrations & coding patterns. Use when defining ARM/Bicep experiments, deploying Chaos Agents, using CLI/REST, or integrating with Azure Monitor, and other Chaos Studio related development tasks. Not for Azure Monitor (use azure-monitor), Azure Resiliency (use azure-resiliency), Azure Reliability (use azure-reliability), Azure Site Recovery (use azure-site-recovery).
ISA-5.1 tag naming, ISA-88 batch control, ISA-95 enterprise integration, ISA-18.2 alarm management, and ISA-101 HMI standards reference. Use when working with instrument tags, naming conventions, or plant hierarchy.
Scrapin.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Scrapin.io data.
Fast Track for Feature Process - When requirements are clear and scope is small, skip the complete design process, write a compact {slug}-design.md, and proceed directly to implementation after one confirmation from the user. What is compressed is divergent discussions and phased reviews, not quality standards - code pointers, acceptance criteria, etc., must not be omitted. Trigger scenarios: User says "quick mode", "fastforward", "cut the steps", "just start working". Not suitable for complex features involving cross-subsystem integration, new terminology sorting, or more than 4 promotion steps - in these cases, proactively inform the user to revert to the complete process.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, so that both AI and humans can look them up when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — bugs, configuration traps, environment issues, integration failures; The knowledge track records findings that "should be the default approach going forward" — best practices, workflow improvements, reusable patterns. Trigger scenarios: Proactively prompt for input when wrapping up feature-acceptance or issue-fix, or when the user says phrases like "document knowledge", "learning", "document learnings", "record this experience". Spec documents record what was done and how it was done, while learning documents record what pitfalls were encountered / what was learned — the two complement each other and are not interchangeable.
Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead.
Azure AI Vision integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure AI Vision data.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.
Steedos Server real-time WebSocket system using Socket.IO. Covers the AppGateway (@WebSocketGateway), connection authentication via cookies, room-based event routing (tenant-scoped rooms), subscribe/unsubscribe events, metadata change notifications, record change events, notification broadcasting, and Moleculer event integration for cross-service real-time communication.
Sendr platform help — AI-powered personalized outreach with lipsync video, dynamic landing pages, lead finder (479M+ contacts), and campaign sequencing. Use when setting up Sendr campaigns, lipsync video audio is out of sync, Sendr credits burning too fast, Lead Finder or Data Studio buttons are greyed out, dynamic pages not rendering for prospects, Sendr API or webhook integration not working, or Sendr Zapier automations failing. Do NOT use for general outbound strategy without a platform (use /sales-cadence), or general deliverability without Sendr (use /sales-deliverability).
Treasure Data platform help — enterprise AI-native CDP with profile unification, audience segmentation, journey orchestration, 400+ connectors, AI Marketing Cloud suites. Use when setting up Treasure Data CDP, unifying customer profiles across channels, building audience segments in Treasure Data, activating audiences to ad platforms or CRMs, configuring Treasure Data connectors or integrations, writing SQL queries in Treasure Data, troubleshooting Treasure Data workflows or jobs, or working with the TD API. Do NOT use for general CRM data quality without Treasure Data context — use /sales-data-hygiene instead.
LeadIQ platform help — Chrome extension-first B2B prospecting with AI outreach writing, champion tracking, and CRM enrichment via GraphQL API. Use when captured contacts from LinkedIn have wrong phone numbers, Salesforce sync keeps assigning leads to wrong accounts, Chrome extension freezes or won't load on LinkedIn, credits are burning too fast on phone lookups, HubSpot integration is too complex through Workato, or Scribe AI emails sound too generic. Do NOT use for building prospect lists across multiple tools (use /sales-prospect-list), general enrichment strategy across providers (use /sales-enrich), outbound sequence design (use /sales-cadence).