Explore skills
Showing 72421–72450 of 74358 skills
Commit a skill authored in this workspace to the liferay-portal repository, collapsing the workspace's duplicated agent trees into the repository's symlinked layout. Use when the user asks to commit, contribute, or upstream a skill, and as the handoff from `author-skill`.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexDeploy a client extension, module, or theme to the running Liferay server (Tomcat or Docker) and verify it started. Use at the end of any skill that produces deployable artifacts, when the user asks to deploy, when verifying that a previous deployment took effect, or when troubleshooting a bundle that does not appear in Liferay.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexAudit, prompt, and enable Liferay feature flags required by a given workflow. Use when a skill needs a flag set (LPD-63311 for MCP, LPD-17564 for CMS and object collaborators on 2026.Q1 and 2026.Q2, etc.), when the user asks to enable a flag, when an API returns 404, or when a Headless endpoint silently returns 400 UnsupportedOperationException.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexBeginner friendly mentor walkthrough for creating, deploying, and verifying a first Liferay Client Extension. Use when the user appears new to Liferay or Client Extensions, or when the user explicitly asks for a guided experience. For experienced developers and advanced workflows, use `scaffold-client-extension` instead.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexGentle first run setup walkthrough for a user brand new to a Liferay Workspace. Use when a first time user needs step by step help creating a workspace, initializing the bundle, and starting the server for the first time. For diagnosing or repairing an existing workspace, use workspace-init.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexBack a Liferay Object with an external data source using the Object Entry Manager CET pattern. Use when the user wants to connect an object to an external REST API, database, or SaaS system rather than storing data in Liferay's own database.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexConnect DXP to Liferay Analytics Cloud / Liferay Data Platform (LDP) and track custom events from fragments and client extensions with the Analytics SDK — `Analytics.track`, real time segments, and checking that an event reaches LDP. Use when the user asks to connect DXP to Analytics Cloud or LDP, track a custom event from a fragment or a client extension, read the visitor's real time segments, verify that an event arrives in LDP, or build an Event Analysis. Deciding when an event should fire belongs to other skills.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexAuthenticate to and operate on a Liferay Cloud (LXC / DXP Cloud) project via the `lcp` CLI — deploy client extensions, view logs, restart services, list resources. Use when the user mentions lcp/LXC/liferay.cloud, when an LCP.json is present in the workspace, or when the user references a console.liferay.cloud URL.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate and configure Liferay Data Sets (Frontend Data Sets) over object entries through the data-set-admin API — table, list, and card views, columns and renderers, filters, default sort, row and creation actions, custom renderer and filter client extensions — then place the Data Set fragment on a page and move the definition between environments. Use when the user asks for a table, list, or card grid of object entries, a filterable listing, or a Data Set that renders nothing or crashes.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexManage workspace environment configurations (local/dev/uat/prod), promote changes between environments, export object data models, and capture a running site as a reusable site initializer CET. Use when the user asks to promote to UAT, export this site, migrate object data, or set up environment specific properties.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexBuild a Liferay Form Container — the native page element that creates or edits an Object entry from a Content Page or a Display Page Template — over the live page API or the site initializer tree. Covers field fragment keys, the submit button, multistep forms, success redirects, hidden context fields, edit forms on a DPT, the gated content recipe (teaser and form, then the full entry), and the permission that makes a form render at all. Use when the user asks for a form that saves to an object, a lead or contact form, gated content behind a form, an edit form on a display page, or a form that renders nothing.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexAdd business logic to Liferay Objects via object actions, workflow definitions, and notification templates. Use when the user asks to send a notification on create, trigger an action on update, wire a workflow, or automate any response to object entry lifecycle events.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate, update, and publish Liferay Object definitions — fields, relationships, picklists, and validations. Use when the user asks to create an object, add a field, define a picklist, add a relationship, or set up an object validation.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate and configure site pages, navigation menus, display page templates, page templates, and SEO settings via the Headless Admin Site API. Use when the user asks to create a page, set up navigation, build a display page template for an object, or configure page SEO.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate roles, assign permissions on objects and pages, and manage site memberships via Headless Admin User and object collaborators APIs. Use when the user asks to add a role, grant permissions, make a page private, share an entry with one user, or control who can view or edit an object's entries.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexSet up the Liferay MCP server, manage CLI session restart ordering, and diagnose MCP specific failure modes (transport version switch, the 2026.Q3 enable switch and tool sets, connection lifecycle, auth split, 204 false alarms, unencoded query strings, token limit exceeded). Use when the user asks to enable or set up MCP, when an MCP tool call returns errors, or before performing content/page/object operations where MCP is preferred over raw REST.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexProduction guardrails applied when generating or modifying any code or configuration intended for a nonlocal environment (UAT, prod, customer facing deploys). Use whenever the agent's output may reach a higher environment — to enforce state integrity, secret management, and security preserving debugging practices.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexStandards for building and deploying React based Custom Element Client Extensions. Use when the user wants to build a React powered widget, scaffold a React Custom Element CET, debug 404s on built assets, or troubleshoot an OSGi `Configuration deleted` loop. For nonReact Custom Element scaffolding or other CET types, use `scaffold-client-extension`.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexGenerate the directory structure and client-extension.yaml for any Liferay client extension type. Use when the user asks to create a client extension, scaffold a custom element, add an object action microservice, create a site initializer, or build any other CET. After scaffolding, calls deploy-and-verify to confirm startup.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate a Liferay input fragment that lives inside a Form Container and binds to an object field. Use when the user asks to build a form field, add a custom input to a form, create a picker or stepper for a form, or make a fragment that submits to an object.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate a Liferay page fragment — an HTML/CSS/JS building block that marketers drop onto Content Pages. Use when the user asks to create a fragment, build a hero section, or make a reusable page component.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCreate and configure the OAuth 2.0 application that a client extension needs to call Liferay Headless APIs, and the browser side client a fragment or widget needs to call a CET. Use when a CET of type objectAction, workflowAction, notificationType, siteInitializer, or any backend CET requires authenticated API access, or when browser code must call a client extension with a token. Called by scaffold-client-extension automatically when the CET type requires OAuth.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexCustomize the visual appearance of a Liferay site using themeCSS client extensions, master pages, and style books. Use when the user asks to change colors or fonts, create a theme, set up a style book, define a master page header/footer, or apply WCAG accessibility guidelines.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexBootstrap a Liferay Workspace, download and verify the bundle, set up auth verifiers, and complete first login bootstrap. Use when the user is starting fresh, when the server appears down or unreachable, when gradle.properties or bundles/ is missing, or when the user asks to set up, initialize, or scaffold a workspace.
liferay/liferay-portal
Stars: 2.2kClaude CodeCodexOpen a draft pull request in the Redocly CLI repository from a branch without a PR, or a new branch from main — commit the staged files, or the files of the change when nothing is staged, check the changeset, and fill the PR template without removing any of its sections. Use whenever the user asks to open, create, or prepare a PR or draft PR, push work for review, or ship a change, even if they do not say "draft".
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexUse when you create or tune the recheck block and recheck/* presets in redocly.yaml for a project — choose presets, set severities from measured counts, add exceptions, adopt a baseline, and validate the result.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexUse when you write or edit Markdown in a project whose redocly.yaml has a recheck block or a recheck/* preset in extends — run redocly recheck on the touched files before you commit them or hand them over, and fix what it finds.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexRedocly CLI for OpenAPI, AsyncAPI, Arazzo, and Overlay descriptions, and for Markdown docs. Use when the user wants to lint, bundle, split, or join an API description, apply decorators or overlays, build or preview API docs, lint Markdown or prose with recheck, test a live API with respect or Arazzo, capture traffic or check drift, get stats or a score, generate a TypeScript client, document an MCP server in an OpenAPI description, push to the Redocly platform, clone a Redocly-hosted project and open its pull requests, or find the node type a rule or plugin should target.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexImplement a Redocly CLI lint rule in a user's redocly.yaml or custom plugin for an OpenAPI, AsyncAPI, or Arazzo description. Use when the user wants a convention enforced, asks for a configurable rule or a plugin rule, debugs a rule that never reports or gives false positives, or migrates rules from another linter such as Spectral.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodexDesign of the ejected Redocly `cli` client generator. Read it, and update it, before changing generators/cli/.
Redocly/redocly-cli
Stars: 1.5kClaude CodeCodex