Loading...
Loading...
Found 233 Skills
Upgrade an existing EmDash project with upgrade-emdash, interpret .emdash/UPGRADE.md, apply required project changes, and verify the package, skill, and migration result. Use when asked to update or upgrade EmDash dependencies. Do not use for an unrelated schema change or a known database migration without a package upgrade.
Implement health checks in Umbraco backoffice using official docs
Implement package views in Umbraco backoffice using official docs
Analyze and port WordPress plugin behavior, custom post types, shortcodes, admin workflows, and stored data to current EmDash extension points. Use for WordPress-plugin migrations or when deciding which behavior belongs in an EmDash plugin, site schema, seed, or Astro code. Do not use for visual theme ports without plugin functionality.
Manually invoked skill for reskinning Payload UI components. Requires Figma URL. Usage: /ui4
Design composable recommendation, ranking, and feed pipelines using the six-stage Source→Hydrator→Filter→Scorer→Selector→SideEffect framework popularized by xAI's open-sourced For You algorithm. Use this skill whenever the user is building any system that picks "the top K items for a (user, context)" — social feeds, content CMSs, RAG rerankers, task prioritizers, notification triage, search reranking, ad ranking.
Reasoning skill for prior authorization clinical policy evaluation. Use when the user asks about payer clinical criteria, step therapy requirements, medical necessity definitions, CMS LCD/NCD coverage rules, appeals documentation strategy, formulary tier implications, or FHIR Da Vinci PAS implementation guidance. Triggers include "prior auth policy", "step therapy", "medical necessity", "coverage determination", "LCD", "NCD", "formulary tier", "PA appeal", "peer-to-peer review", "Da Vinci PAS", "clinical criteria", "PA denial", "drug authorization", "utilization management".
Reasoning skill for healthcare claims billing rules and fraud detection logic. Use when the user asks about CMS billing rules, place of service codes, global surgery periods, modifier usage (25 59 76 77), NCCI edit logic, column 1 column 2 code pairs, mutually exclusive procedures, modifier indicators, fraud waste and abuse patterns, E&M upcoding, unbundling, phantom billing, impossible day detection, coding error versus fraud distinction, FWA investigation methodology, or claims audit logic. Triggers include "CMS billing rules", "NCCI edits", "modifier 25", "modifier 59", "global surgery period", "upcoding", "unbundling", "phantom billing", "impossible day", "FWA", "fraud waste abuse", "coding error vs fraud", "claims audit", "billing compliance", "E&M level selection".
Apply Hyva UI template-based components to a Hyvä theme. This skill should be used when the user wants to add, install, or apply a Hyva UI component (such as header, footer, gallery, menu, minicart, etc.) to their Hyvä theme. It lists available non-CMS components and their variants, displays component README instructions, and copies component files to the theme directory.
Create, repair, or extend local Docker Compose and Dockerfile setups for PHP/Laravel and CMS projects, Node.js, Python, and monorepos. Use when Dockerizing a project for development, adding local databases or supporting services, or safely merging existing development Compose configurations. Inspect the repository first, infer safe defaults, ask only about unresolved high-impact choices, preserve existing work, and verify generated files. Do not use as a production deployment workflow.
Create / provision / set up a NEW Digital Experience (Communities) / Experience Cloud site — employee service, IT support, help desk, HR, customer, and partner portals — via the headless-360 MCP site-creation APIs. Use whenever a user asks to create/provision/set up a portal, site, or community, e.g.: 'create an employee service portal', 'create an IT Support Portal', 'create an Agentforce Employee Center', including wiring MIAW (Messaging for In-App/Web) at create. This is the site-CREATION skill and OWNS provisioning a new Aura OR LWR Experience Builder site from scratch — trigger it even when the user says 'Experience Builder site' or 'LWR site', as long as a NEW site is wanted. It always writes a portal-creation report as its final step (never ad hoc via CLI) and never makes a legacy Tabs+Visualforce site. DO NOT TRIGGER only for modifying an EXISTING site's pages/routes/theme/branding/guest-access metadata (experience-lwr-site-generate), existing-site customization (experience-ui-bundle), CMS, Commerce.
Guides all better-i18n integration decisions — SDK selection (Next.js, React, Expo, Swift, Flutter, Remix), CDN vs GitHub workflow, AI-powered translation management via MCP tools, CLI health checks (scan, doctor, sync), Content CMS (localized models, entries, custom fields), file format conventions (flat / nested / namespaced), key naming, publish flows, and quality analytics. Use whenever building, modifying, or reviewing any localization feature — including i18n setup, adding languages, managing translation keys, publishing, or integrating AI workflows.