vercel
Deploy and manage Vercel projects, domains, environment variables, and serverless functions using the `vercel` CLI.
What this skill does
# Vercel Skill Use the `vercel` CLI to deploy and manage Vercel projects. ## Deployments Deploy current directory: ```bash vercel ``` Deploy to production: ```bash vercel --prod ``` List recent deployments: ```bash vercel ls ``` Inspect a deployment: ```bash vercel inspect <deployment-url> ``` View deployment logs: ```bash vercel logs <deployment-url> ``` Redeploy a previous deployment: ```bash vercel redeploy <deployment-url> ``` ## Projects List all projects: ```bash vercel project ls ``` Link current directory to a project: ```bash vercel link ``` Remove a project: ```bash vercel project rm <project-name> ``` ## Domains List domains: ```bash vercel domains ls ``` Add a domain to a project: ```bash vercel domains add <domain> <project-name> ``` Check domain configuration: ```bash vercel domains inspect <domain> ``` ## Environment Variables List env vars for a project: ```bash vercel env ls ``` Add an env var: ```bash vercel env add <name> ``` Pull env vars to local .env file: ```bash vercel env pull ``` Remove an env var: ```bash vercel env rm <name> ``` ## Local Development Run project locally with Vercel's dev server: ```bash vercel dev ``` Pull latest project settings: ```bash vercel pull ``` Build project locally: ```bash vercel build ``` ## Secrets (Legacy) Note: Secrets are deprecated in favor of Environment Variables. ## Teams List teams: ```bash vercel teams ls ``` Switch to a team: ```bash vercel switch <team-slug> ``` ## Authentication Check current login: ```bash vercel whoami ``` Login: ```bash vercel login ``` Logout: ```bash vercel logout ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.