netlify
Use the Netlify CLI (netlify) to create/link Netlify sites and set up CI/CD (continuous deployment) from GitHub, especially for monorepos (multiple sites in one repo like Hugo sites under sites/<domain>). Use when Avery asks to deploy a new site, connect a repo to Netlify, configure build/publish settings, set environment variables, enable deploy previews, or automate Netlify site creation.
What this skill does
# netlify Use the `netlify` CLI to create projects (“sites”), link local folders, and configure CI/CD from GitHub. ## Pre-reqs - `netlify --version` - Logged in (`netlify login`) **or** provide `--auth $NETLIFY_AUTH_TOKEN`. - Know the Netlify team/account slug you want to create sites under (optional but recommended). Helpful checks: ```bash netlify status netlify sites:list ``` ## Monorepo pattern (recommended) For **one repo with multiple sites** (e.g. `sites/seattlecustomboatparts.com`, `sites/floridacustomerboatparts.com`): - Create **one Netlify site per domain**. - Set the site’s **Base directory** to that subfolder. - Put a `netlify.toml` *inside that subfolder*. This keeps each domain’s build config self-contained. ### Hugo subfolder `netlify.toml` Create `sites/<domain>/netlify.toml`: ```toml [build] command = "hugo --minify" publish = "public" [build.environment] HUGO_VERSION = "0.155.1" ``` (Adjust HUGO_VERSION as needed.) ## Fast workflow: create + link + init CI/CD ### 1) Create a Netlify site (project) Run inside the site folder you want to deploy (base dir): ```bash cd sites/<domain> netlify sites:create --name <netlify-site-name> --account-slug <team> --with-ci ``` Notes: - `--with-ci` starts CI hooks setup. - If you need manual control, add `--manual`. ### 2) Link local folder to the created site If not linked already: ```bash netlify link ``` ### 3) Connect to GitHub for continuous deployment ```bash netlify init ``` This is usually interactive (select Git remote/repo + build settings). For automation we can pre-create `netlify.toml` and then accept defaults. ## Environment variables Set per-site vars: ```bash netlify env:set VAR_NAME value netlify env:list ``` Useful for monorepos: - `CONTACT_EMAIL` (or other shared config) ## Deploy Manual deploys (handy for quick preview): ```bash netlify deploy # draft deploy netlify deploy --prod # production deploy ``` ## Included scripts - `scripts/hugo_netlify_toml.sh`: create a `netlify.toml` in a Hugo subfolder - `scripts/netlify_monorepo_site.sh`: helper to create/link/init a site for a subfolder When using scripts, prefer passing `NETLIFY_AUTH_TOKEN` via env for non-interactive runs.
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.