
sapui5-cli
Manages SAPUI5/OpenUI5 projects using the UI5 Tooling CLI (@ui5/cli). Use when initializing UI5 projects, configuring ui5.yaml or ui5-workspace.yaml files, building UI5 applications or libraries, running development servers with HTTP/2 support, creating custom build tasks or server middleware, managing workspace/monorepo setups, troubleshooting UI5 CLI errors, migrating between UI5 CLI versions, or optimizing build performance. Supports both OpenUI5 and SAPUI5 frameworks with complete configuration and extensibility guidance.
- Installs
- 824
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/secondsky/sap-skills --skill sapui5-cli- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sapui5-cli automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
SAPUI5/OpenUI5 CLI Management Skill
Related Skills
- sap-dependency-security: Use for secure CLI/toolchain upgrades, lockfile hardening, and deterministic installs in UI5 tooling workflows
Table of Contents
Overview
This skill provides comprehensive guidance for working with the UI5 CLI (UI5 Tooling), the official command-line interface for developing, building, and deploying SAPUI5 and OpenUI5 applications and libraries.
Current CLI Version: 4.0.55 (verified via npm on 2026-05-31) Node.js Requirements: v20.11.0+ or v22.0.0+ (v21 not supported) npm Requirements: v8.0.0+
When to Use This Skill
Use this skill when you need to:
- Initialize new UI5 projects or enable CLI support for existing projects
- Configure ui5.yaml for applications, libraries, theme-libraries, or modules
- Build UI5 projects with optimization, bundling, and minification
- Run local development servers with HTTP/2, SSL, and CSP support
- Extend build processes with custom tasks or server middleware
- Manage monorepo/workspace configurations with multiple UI5 projects
- Troubleshoot common UI5 CLI errors and build issues
- Migrate between CLI versions (v1 → v2 → v3 → v4)
- Optimize build performance and analyze dependencies
Quick Start Workflow
New Project Setup
# 1. Install UI5 CLI (choose one)
npm install --global @ui5/cli # Global installation
npm install --save-dev @ui5/cli # Project-level installation
# 2. Initialize project (if new)
npm init --yes # Initialize npm
ui5 init # Create ui5.yaml
# 3. Select framework variant
ui5 use openui5@latest # For OpenUI5
ui5 use sapui5@latest # For SAPUI5
# 4. Add framework libraries
ui5 add sap.ui.core sap.m sap.ui.table themelib_sap_fiori_3
# 5. Start development
ui5 serve # Start dev server
ui5 serve --open index.html # Start and open browser
# 6. Build for production
ui5 build --all # Build with dependencies
ui5 build --clean-dest # Clean before building
Existing Project Setup
# 1. Enable CLI support
ui5 init
# 2. Configure framework (if ui5.yaml exists)
ui5 use openui5@latest # or sapui5@latest
# 3. Verify setup
ui5 tree # Show dependency tree
ui5 serve # Test development server
Project Types
UI5 CLI supports four project types, each with specific configurations:
1. Application
Standard UI5 applications with a webapp directory.
- Virtual path mapping:
webapp/→/ - Generates Component-preload.js when Component.js exists
- See
templates/ui5.yaml.applicationfor configuration template
2. Library
Reusable component libraries for sharing across projects.
- Virtual path mappings:
src/→/resources,test/→/test-resources - Requires namespace directory structure (e.g.,
src/my/company/library/) - See
templates/ui5.yaml.libraryfor configuration template
3. Theme Library
Provides theming resources for libraries.
- Same virtual mappings as standard libraries
- Resources organized by namespace (e.g.,
my/library/themes/custom_theme/) - See
references/configuration.mdfor detailed configuration
4. Module
Third-party resources with flexible path mapping.
- Resources copied without modification
- Custom virtual-to-physical path mappings
- See
references/project-structures.mdfor module configuration
Core Commands Reference
Project Initialization
ui5 init # Initialize UI5 CLI configuration
ui5 use <framework>[@version] # Set framework (openui5/sapui5)
ui5 add <libraries...> # Add framework libraries
ui5 remove <libraries...> # Remove framework libraries
Development
ui5 serve [options] # Start development server
--port <number> # Specify port (default: 8080)
--open <path> # Open browser to path
--h2 # Enable HTTP/2
--accept-remote-connections # Allow non-localhost access
ui5 tree [options] # Display dependency tree
--flat # Show flat list
--level <number> # Limit tree depth
Building
ui5 build [child-command] [options] # Build project
preload # Create preload bundles (default)
self-contained # Create standalone bundle
jsdoc # Generate JSDoc documentation
--all # Include all dependencies
--include-dependency <names> # Include specific dependencies
--exclude-dependency <names> # Exclude dependencies
--dest <path> # Output directory (default: ./dist)
--clean-dest # Clean destination before build
--create-build-manifest # Store build metadata
--experimental-css-variables # Generate CSS variable artifacts [experimental]
Configuration
ui5 config set <key> [value] # Set configuration value
ui5 config get <key> # Get configuration value
ui5 config list # List all settings
# Common configurations
ui5 config set ui5DataDir /path/.ui5 # Change cache directory
Utility
ui5 versions # Display all module versions
ui5 --help # Display help
ui5 --version # Display version
For complete command reference, see references/cli-commands.md.
Configuration File Structure
Basic ui5.yaml Structure
specVersion: "4.0" # Specification version (required)
type: application # Project type (required)
metadata:
name: my.project.name # Project name (required)
copyright: "© ${currentYear} Company" # Optional copyright
framework:
name: SAPUI5 # OpenUI5 or SAPUI5
version: "1.120.0" # Framework version
libraries:
- name: sap.ui.core
- name: sap.m
- name: sap.ui.table
- name: themelib_sap_fiori_3
optional: true # Optional library
resources:
configuration:
paths:
webapp: webapp # Path mapping
propertiesFileSourceEncoding: UTF-8 # Encoding (default: UTF-8)
builder:
resources:
excludes:
- "index.html" # Exclude from build
- "/resources/my/project/test/**"
server:
settings:
httpPort: 8080 # HTTP port
httpsPort: 8443 # HTTPS port
For complete configuration reference, see references/configuration.md.
Progressive Disclosure: Detailed References
This main skill file provides essential workflows and quick reference. For detailed information on specific topics, refer to these reference files:
Core References
references/cli-commands.md: Complete CLI command reference with all options and examplesreferences/configuration.md: Comprehensive ui5.yaml configuration guide (includes workspace config)references/project-structures.md: Detailed project types with directory structures and build output styles
Advanced Topics
references/extensibility.md: Custom tasks, middleware, and project shims with complete API documentationreferences/filesystem-api.md: Complete FileSystem API for custom task/middleware developmentreferences/build-process.md: Complete build process including tasks, minification, source maps, and bundlingreferences/server-features.md: Complete server documentation with middleware stack, HTTP/2, SSL, and CSPreferences/code-analysis.md: Dependency analyzers, JSDoc generation, and code analysis featuresreferences/es-support.md: Complete ECMAScript version support, restrictions, and module format requirements
Performance & Troubleshooting
references/benchmarking.md: Performance testing and benchmarking with hyperfinereferences/migration-guides.md: Complete version migration guides (v1→v2→v3→v4)references/troubleshooting.md: Common issues, errors, and solutions with exact error messages
Common Workflows
Workflow 1: Setting Up a New Application
When to use: Starting a new SAPUI5/OpenUI5 application from scratch.
Steps:
- Initialize npm project:
npm init --yes - Install UI5 CLI:
npm install --save-dev @ui5/cli - Initialize UI5 configuration:
ui5 init - Select framework:
ui5 use sapui5@latest(oropenui5@latest) - Add required libraries:
ui5 add sap.ui.core sap.m themelib_sap_fiori_3 - Create application structure (webapp/, Component.js, manifest.json)
- Start development server:
ui5 serve - Commit configuration:
git add ui5.yaml package.json && git commit
Workflow 2: Enabling CLI for Existing Project
When to use: Adding UI5 CLI support to an existing UI5 project.
Steps:
- Navigate to project root
- Run
ui5 initto create ui5.yaml - Configure framework:
ui5 use sapui5@latest - Add libraries:
ui5 add sap.ui.core sap.m sap.ui.table - Adjust ui5.yaml
resources.configuration.pathsif needed - Test with
ui5 serve - Build with
ui5 build --all
Workflow 3: Creating a Custom Build Task
When to use: Extending the build process with custom processing.
Steps:
- Create task file (e.g.,
lib/tasks/customTask.js) - Implement task using Task API (see
templates/custom-task-template.js) - Create task extension in ui5.yaml or separate file
- Configure task in builder.customTasks section
- Test with
ui5 build - For details, see
references/extensibility.md
Workflow 4: Setting Up a Workspace/Monorepo
When to use: Managing multiple related UI5 projects in a single repository.
Steps:
- Create ui5-workspace.yaml in root project
- Define workspace name and dependency resolutions
- Point to local project directories using relative paths
- Use
--workspace <name>flag to activate specific workspace - Run
ui5 treeto verify dependency resolution - For details, see
references/configuration.md(workspace section)
Workflow 5: Migrating to UI5 CLI v4
When to use: Upgrading from UI5 CLI v3 to v4.
Prerequisites:
- Verify Node.js v20.11.0+ or v22.0.0+
- Verify npm v8.0.0+
Steps:
- Update CLI:
npm install --save-dev @ui5/cli@latest - Update specVersion in ui5.yaml to
"4.0" - Review breaking changes in
references/migration-guides.md - Remove
usePredefineCallsbundle option if present - Update bundle sections to use
async: truefor modern loading - Test build:
ui5 build --all - Test server:
ui5 serve - Verify application functionality
Decision Trees
Framework Selection Decision
Question: Which framework should I use?
Does project need SAP-specific components (e.g., sap.ui.comp, sap.ushell)?
├─ YES → Use SAPUI5
│ └─ Command: ui5 use sapui5@latest
└─ NO → Can use OpenUI5
└─ Command: ui5 use openui5@latest
Note: SAPUI5 projects can depend on OpenUI5, but not vice versa.
Build Type Decision
Question: Which build type should I use?
What is the deployment target?
├─ Standard deployment (with separate framework loading)
│ └─ Use: ui5 build --all
│
├─ Standalone deployment (single bundle with framework)
│ └─ Use: ui5 build self-contained --all
│
├─ Documentation generation
│ └─ Use: ui5 build jsdoc
│
└─ Development/testing (no build needed)
└─ Use: ui5 serve
Custom Extension Decision
Question: Should I create a custom task or middleware?
What do you need to extend?
├─ Build process (modify/generate resources during build)
│ └─ Create custom task (see templates/custom-task-template.js)
│ Examples: Transpiling, image optimization, file generation
│
├─ Development server (modify requests/responses during dev)
│ └─ Create custom middleware (see templates/custom-middleware-template.js)
│ Examples: Proxying, authentication, dynamic content
│
└─ Third-party library configuration
└─ Create project shim (see references/extensibility.md)
Examples: Configuring non-UI5 npm packages
Templates
This skill provides working templates for common configurations:
templates/ui5.yaml.application: Complete application configurationtemplates/ui5.yaml.library: Complete library configurationtemplates/ui5-workspace.yaml: Monorepo workspace setuptemplates/custom-task-template.js: Custom build task boilerplatetemplates/custom-middleware-template.js: Custom server middleware boilerplate
Important Notes
Specification Versions
UI5 CLI uses specification versions to manage features:
- 4.0: Current major version (verified CLI v4.0.55, requires Node.js v20.11.0+)
- 3.0-3.2: Compatible with CLI v3.0.0+
- 2.0-2.6: Compatible with CLI v2.0.0+
- 0.1-1.1: Legacy versions (automatic migration attempted)
Always use the latest specVersion for new projects.
Framework Version Requirements
- OpenUI5: Minimum version 1.52.5
- SAPUI5: Minimum version 1.76.0
Development vs. Build
Important: During development, always use ui5 serve instead of ui5 build. Building should only occur when deploying to production. The development server provides:
- Faster reload times
- On-the-fly resource processing
- Better debugging experience
- Automatic dependency resolution
Global vs. Local Installation
When both global and local UI5 CLI installations exist, the local version takes precedence automatically. This allows different projects to use different CLI versions.
Override behavior: UI5_CLI_NO_LOCAL=X ui5 serve
Cache Management
UI5 CLI caches framework versions in ~/.ui5/ (configurable via ui5DataDir).
Clear cache: rm -rf ~/.ui5/framework/
Known Issues & Limitations
ECMAScript Module Limitations
UI5 CLI does not support JavaScript modules with import/export syntax. All modules must use sap.ui.define format.
Unsupported:
import Module from './module.js';
export default MyClass;
Supported:
sap.ui.define(['./module'], function(Module) {
return MyClass;
});
Template Literal Restrictions
Expressions in template literals cannot be used in:
- Dependency declarations
- Smart Template names
- Library initialization calls
Unsupported:
sap.ui.define([`modules/${moduleName}`], ...); // Will fail
Bundling Restrictions (v4.0+)
JavaScript modules requiring 'top level scope' cannot be bundled as strings. They will be omitted from bundles with error logging.
Manifest Version Compatibility
For UI5 1.71, manifest _version property must be ≤ 1.17.0 for supportedLocales generation. Update manifest version to match UI5 framework version.
Troubleshooting Quick Reference
For detailed troubleshooting, see references/troubleshooting.md.
Common Issues
Issue: ERR_SSL_PROTOCOL_ERROR in Chrome when accessing HTTP server
Solution: Chrome enforces HTTPS via HSTS. Clear HSTS settings:
- Navigate to
chrome://net-internals/#hsts - Enter domain (e.g., localhost)
- Click "Delete"
Issue: Excessive disk space in ~/.ui5/
Solution: Clear cached framework versions:
rm -rf ~/.ui5/framework/
Issue: Build fails with "TypeError: invalid input"
Solution: Check manifest _version compatibility with UI5 framework version. For UI5 1.71, use manifest version ≤ 1.17.0.
Issue: Custom task not executing
Solution: Verify task configuration:
- Check task is properly defined in ui5.yaml
- Verify
beforeTaskorafterTaskreferences valid task name - Check task file exports async function with correct signature
- Use
ui5 build --verbosefor detailed logging
Environment Variables
UI5_LOG_LVL: Set log level (silent/error/warn/info/perf/verbose/silly)UI5_DATA_DIR: Override default data directory (~/.ui5)UI5_CLI_NO_LOCAL: Disable local CLI precedence (use global)
Examples:
UI5_LOG_LVL=verbose ui5 build
UI5_DATA_DIR=/custom/.ui5 ui5 serve
Best Practices
- Always commit ui5.yaml and package.json to version control
- Use local CLI installation for project consistency (
--save-dev) - Pin framework versions for production builds
- Use workspaces for monorepo setups instead of npm linking
- Enable HTTP/2 during development (
ui5 serve --h2) - Clean builds for production (
ui5 build --clean-dest --all) - Validate configurations before committing (use validation scripts)
- Test with multiple browsers when using CSP policies
- Document custom tasks and middleware in project README
- Keep CLI updated to benefit from latest features and fixes
Additional Resources
- Official Documentation: https://ui5.github.io/cli/stable/
- API Reference: https://ui5.github.io/cli/v4/api/
- JSON Schema: https://ui5.github.io/cli/schema/ui5.yaml.json
- GitHub Repository: https://github.com/SAP/ui5-tooling
- SAP Community: https://community.sap.com/
- npm Registry: https://www.npmjs.com/package/@ui5/cli
Bundled Resources
Reference Documentation
references/cli-commands.md- Complete CLI command referencereferences/configuration.md- Configuration options and ui5.yamlreferences/project-structures.md- Project structure patternsreferences/server-features.md- Development server featuresreferences/build-process.md- Build process and optimizationreferences/es-support.md- ES module supportreferences/extensibility.md- Extensibility optionsreferences/code-analysis.md- Code analysis toolsreferences/migration-guides.md- Migration from older versionsreferences/troubleshooting.md- Common issues and solutionsreferences/benchmarking.md- Performance benchmarking
Templates
templates/ui5.yaml.application- Application configuration templatetemplates/ui5.yaml.library- Library configuration templatetemplates/ui5-workspace.yaml- Workspace configuration templatetemplates/custom-task-template.js- Custom task boilerplatetemplates/custom-middleware-template.js- Custom middleware boilerplate
Version Information
- CLI Version Covered: 4.0.55+
- Last Updated: 2026-05-31
- Next Review: 2026-02-21 (Quarterly)
This skill follows official Anthropic Agent Skills best practices and SAP UI5 CLI documentation standards.
FAQ
What does the sapui5-cli skill do?
Manages SAPUI5/OpenUI5 projects using the UI5 Tooling CLI (@ui5/cli). Use when initializing UI5 projects, configuring ui5.yaml or ui5-workspace.yaml files, building UI5 applications or libraries, running development servers with HTTP/2 support, creating custom build tasks or server middleware, managing workspace/monorepo setups, troubleshooting UI5 CLI errors, migrating between UI5 CLI versions, or optimizing build performance. Supports both OpenUI5 and SAPUI5 frameworks with complete configuration and extensibility guidance.
How do I install sapui5-cli?
Run npx skills add https://github.com/secondsky/sap-skills --skill sapui5-cli in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sapui5-cli/ (personal) or .claude/skills/sapui5-cli/ (project).
Which AI agents can use sapui5-cli?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sapui5-cli safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sapui5-cli?
It is published by secondsky in secondsky/sap-skills. It has 824 recorded installs.
More from secondsky/sap-skills
sap-abap
secondsky/sap-skills
Comprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field symbols, data references, exception handling, or ABAP unit testing. Covers both classic ABAP and modern ABAP for Cloud Development patterns.
sap-fiori-tools
secondsky/sap-skills
Develops SAP Fiori applications using SAP Fiori tools extensions for VS Code and SAP Business Application Studio. Use when: generating Fiori Elements or Freestyle SAPUI5 applications, configuring Page Editor for List Report or Object Page, working with annotations and Service Modeler, setting up deployment to ABAP or Cloud Foundry, creating adaptation projects, using Guided Development, previewing with mock data or live data, configuring SAP Fiori launchpad, or using AI-powered generation with Project Accelerator/Joule. Technologies: SAP Fiori Elements, SAPUI5, OData V2/V4, CAP, SAP BTP, ABAP, Cloud Foundry, fiori-mcp-server (MCP tools for AI-assisted generation).
sap-cap-capire
secondsky/sap-skills
SAP Cloud Application Programming Model (CAP) development skill using Capire documentation. Use when: building CAP applications, defining CDS models, implementing services, working with SAP HANA/SQLite/PostgreSQL databases, deploying to SAP BTP Cloud Foundry or Kyma, implementing Fiori UIs, handling authorization, multitenancy, or messaging. Covers CDL/CQL/CSN syntax, Node.js and Java runtimes, event handlers, OData services, and CAP plugins.
sap-btp-developer-guide
secondsky/sap-skills
Develops business applications on SAP Business Technology Platform (BTP) using CAP (Node.js/Java) or ABAP Cloud. Use when: building cloud applications on SAP BTP, deploying to Cloud Foundry or Kyma runtimes, integrating with SAP HANA Cloud, implementing SAP Fiori UIs, connecting to remote SAP systems, building multitenant SaaS applications, extending SAP S/4HANA or SuccessFactors, setting up CI/CD pipelines, implementing observability, or following SAP development best practices. Keywords: SAP BTP, Business Technology Platform, CAP, Cloud Application Programming Model, ABAP Cloud, Cloud Foundry, Kyma, SAP HANA Cloud, SAP Fiori, SAPUI5, CI/CD, observability, multitenant, SaaS, SAP BTP ABAP environment, SAP Business Application Studio, SAP Cloud SDK, SAP Integration Suite, SAP Event Mesh, SAP Connectivity Service, SAP Destination Service, XSUAA, OAuth, OpenID Connect, OData, CDS, Core Data Services, ABAP CDS, ABAP RESTful Application Programming Model, RAP, ABAP development, SAP BTP deve
sap-btp-best-practices
secondsky/sap-skills
SAP BTP best practices for enterprise architecture, account management, security, and operations, with verification evidence tracked in the repository ledger. Use when planning BTP implementations, setting up account hierarchies, configuring environments, implementing authentication, designing CI/CD pipelines, establishing governance, building Platform Engineering teams, implementing failover strategies, or managing application lifecycle on SAP BTP. Keywords: SAP BTP, account hierarchy, global account, directory, subaccount, Cloud Foundry, Kyma, ABAP, SAP Identity Authentication, CI/CD, governance, Platform Engineering, failover, multi-region, SAP BTP best practices
sap-btp-connectivity
secondsky/sap-skills
SAP BTP Connectivity skill covering Destination Service, Connectivity Service, Cloud Connector, Connectivity Proxy, and Transparent Proxy for Kubernetes. Use when configuring destinations (HTTP, RFC, LDAP, MAIL, TCP), setting up cloud-to-on-premise connectivity, implementing OAuth and principal propagation, deploying connectivity proxies in Kubernetes/Kyma, troubleshooting connectivity errors (405, 407, 503), or configuring multitenancy.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.