Authoring GitHub Workflows
dotnet/skills
Author and review GitHub Actions workflow YAML safely so syntactically-valid YAML can't ship a workflow that GitHub Actions refuses to run.
Set up CI/CD pipelines for Adobe App Builder projects. An agent skill from NeverSight/learn-skills.dev.
Install Appbuilder Cicd Pipeline
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipeline --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .claude/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .claude/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipelineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipeline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .agents/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .agents/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .agents/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipeline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .cursor/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .cursor/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NeverSight/learn-skills.dev.git --path data/skills-md/adobe/skills/appbuilder-cicd-pipeline--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipeline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .gemini/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .gemini/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipelineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .github/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .github/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .github/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NeverSight/learn-skills.dev appbuilder-cicd-pipeline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/data/skills-md/adobe/skills/appbuilder-cicd-pipeline .opencode/skills/appbuilder-cicd-pipeline && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "appbuilder-cicd-pipeline" agent skill from https://github.com/NeverSight/learn-skills.dev/tree/main/data/skills-md/adobe/skills/appbuilder-cicd-pipeline into .opencode/skills/appbuilder-cicd-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "appbuilder-cicd-pipeline", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
appbuilder-cicd-pipeline- GitHub stars
- 216
- Used in
- 1 other repo
- Token cost
- ~1.8k tokens
- SKILL.md length
- 715 words
- Files
- 13
- Skills in repo
- 42
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Set up CI/CD pipelines for Adobe App Builder projects. An agent skill from NeverSight/learn-skills.dev.
- Works in 4 steps: Copy assets/deploy-stage.yml →… → Copy assets/deploy-prod.yml →… → Copy assets/pr-test.yml →… → …
- The user mentions CI/CD for App Builder
- SKILL.md covers Pattern Quick-Reference, Fast Path (for clear requests), Quick Reference and Full Workflow (for ambiguous…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Appbuilder Cicd Pipeline is an agent skill from NeverSight/learn-skills.dev. Set up CI/CD pipelines for Adobe App Builder projects. Generates GitHub Actions workflows using adobe/aio-cli-setup-action@3 and adobe/aio-apps-action@3.3.0, plus patterns for Azure DevOps and GitLab CI. Handles OAuth S2S secrets injection, multi-workspace promotion (stage → prod), deploy gating with manifest validation. Use this skill whenever the user mentions CI/CD for App Builder, GitHub Actions for aio deploy, automated deployment pipelines, continuous integration, continuous delivery, deploy automation…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files (for example `stats.json`). Compatibility notes: Requires aio CLI, Node.js 18+, and a CI/CD platform (GitHub Actions, Azure DevOps, or GitLab CI)
It sits in DevOps & Cloud, covering CI/CD. It works with GitHub Actions, Azure DevOps, GitLab and GitHub. The repository describes itself as: Curated high-quality AI Agent Skills. Search, install, copy and share. Works with Claude Code, Cursor, OpenClaw, and other AI coding tools. The licence is Apache-2.0.
When your agent uses it
- The user mentions CI/CD for App Builder
- GitHub Actions for aio deploy
- Automated deployment pipelines
- Continuous integration
Example prompts
- “/appbuilder-cicd-pipeline”
Requirements
- Node.js
- Compatibility (from SKILL.md): Requires aio CLI, Node.js 18+, and a CI/CD platform (GitHub Actions, Azure DevOps, or GitLab CI)
- Pre-approved tools (allowed-tools): Bash(aio:*), Bash(npm:*), Bash(git:*), Read, Write, Edit
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Copy assets/deploy-stage.yml → .github/workflows/deploy_stage.yml
- Copy assets/deploy-prod.yml → .github/workflows/deploy_prod.yml
- Copy assets/pr-test.yml → .github/workflows/pr_test.yml
- Guide secrets setup using references/secrets-management.md
What it can do on your machine
Read from SKILL.md and the folder at commit 50f7fc9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(aio:*)Bash(npm:*)Bash(git:*)ReadWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developer.adobe.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires aio CLI, Node.js 18+, and a CI/CD platform (GitHub Actions, Azure DevOps, or GitLab CI)
From compatibility in the SKILL.md frontmatter.
Context cost
Appbuilder Cicd Pipeline loads about 1.8k tokens when it runs. Until then it costs about 189 tokens; SKILL.md has 715 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:55
orkspace.json>` to configure `.aio` and `.env` files - NoteMentions a .env fileSKILL.md:62
ce.json>` to configure local `.aio` and `.env`d. Run `assets/fetch-secrets.sh` to extract credential valuese. Guide user
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NeverSight/learn-skills.dev at commit 50f7fc9, republished under its Apache-2.0 licence (© NeverSight). 715 words, ~1,804 tokens.
Download SKILL.mdSave it as
.claude/skills/appbuilder-cicd-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.- name
- appbuilder-cicd-pipeline
- description
- Set up CI/CD pipelines for Adobe App Builder projects. Generates GitHub Actions workflows using adobe/aio-cli-setup-action@3 and adobe/aio-apps-action@3.3.0, plus patterns for Azure DevOps and GitLab CI. Handles OAuth S2S secrets injection, multi-workspace promotion (stage → prod), deploy gating with manifest validation. Use this skill whenever the user mentions CI/CD for App Builder, GitHub Actions for aio deploy, automated deployment pipelines, continuous integration, continuous delivery, deploy automation, multi-environment promotion, aio app add ci, or wants to automate their App Builder build and release process. Also trigger when users mention deploy workflows, release pipelines, or GitHub secrets for App Builder.
- allowed-tools
- Bash(aio:*), Bash(npm:*), Bash(git:*), Read, Write, Edit
- compatibility
- Requires aio CLI, Node.js 18+, and a CI/CD platform (GitHub Actions, Azure DevOps, or GitLab CI)
- metadata.category
- deployment-automation
- license
- Apache-2.0
App Builder CI/CD Pipeline
Set up CI/CD pipelines for Adobe App Builder projects — GitHub Actions (primary), Azure DevOps, GitLab CI. Uses OAuth S2S credentials with IMS authentication. Repository secrets only (no environment secrets).
Pattern Quick-Reference
| User wants | Template |
|---|---|
| GitHub Actions deploy-to-stage | assets/deploy-stage.yml |
| GitHub Actions deploy-to-prod | assets/deploy-prod.yml |
| GitHub Actions PR tests | assets/pr-test.yml |
| Extract secrets from workspace | assets/fetch-secrets.sh |
| Azure DevOps / GitLab CI / Jenkins | references/generic-pipeline-guide.md |
| Secrets setup guide | references/secrets-management.md |
| Debugging deploy failures | references/debugging.md |
Fast Path (for clear requests)
When the user says "set up CI/CD for my App Builder project" and they use GitHub, generate all 3 workflow files + secrets guide immediately:
- Copy
assets/deploy-stage.yml→.github/workflows/deploy_stage.yml - Copy
assets/deploy-prod.yml→.github/workflows/deploy_prod.yml - Copy
assets/pr-test.yml→.github/workflows/pr_test.yml - Guide secrets setup using
references/secrets-management.md
If user specifies Azure DevOps, GitLab CI, or Jenkins → use references/generic-pipeline-guide.md.
Quick Reference
- Workflow location:
.github/workflows/at repository root - Bootstrap command:
aio app add cigenerates starter workflow files - Official actions:
adobe/aio-cli-setup-action@3(CLI install) +adobe/aio-apps-action@3.3.0(build/test/deploy) - Auth model: OAuth Server-to-Server (S2S) with IMS — the
authcommand inaio-apps-actionis DEPRECATED (JWT). Do not use it. - Secrets scope: Repository secrets only. App Builder does NOT support GitHub environment secrets.
- Secrets per workspace: 14 secrets with workspace suffix (
_STAGE,_PROD) - Prerequisite: Add "I/O Management API" to each workspace in Developer Console before extracting secrets
- Workspace config: Run
aio app use <workspace.json>to configure.aioand.envfiles
Full Workflow (for ambiguous or complex requests)
- Check existing setup: Look for
.github/workflows/(fromaio app add cior manual). Check if workflows already exist. - Determine CI/CD platform: GitHub Actions is default. Ask if user needs Azure DevOps, GitLab CI, or Jenkins.
- Generate workflow files: Copy templates from
assets/to.github/workflows/. Customize triggers, branch names, and environment suffixes as needed. - **Guide secrets setup:**a. Ensure "I/O Management API" is added to the workspace in Developer Consoleb. Download
workspace.jsonfrom Developer Consolec. Runaio app use <workspace.json>to configure local.aioand.envd. Runassets/fetch-secrets.shto extract credential valuese. Guide user to add each secret to GitHub repository secrets (NOT environment secrets)f. Add_STAGEor_PRODsuffix to each secret name - Add custom secrets: If the app uses custom env vars, add them under the
envkey in the Deploy step - Validate: Run through
references/checklist.mdbefore merge - Troubleshoot: If deploy fails, consult
references/debugging.mdfor common scenarios - Test: Push to a branch and verify workflow runs successfully
Inputs To Request
- Current repository path and CI/CD platform preference
- Target Adobe organization, project, and workspace names
- Whether Stage, Production, or both workspaces need CI/CD
- Any custom secrets the application requires
Show full SKILL.md (290 more words)Show less
Deliverables
- Workflow YAML files in
.github/workflows/ - Secrets extraction output for repository configuration
- Pre-merge validation against
references/checklist.md
Quality Bar
- All workflow YAML must be syntactically valid
- Secrets must use repository scope, never environment scope
- OAuth S2S credentials only — no JWT auth references
- Each workspace gets its own secret set with correct suffix
- Workflows must use pinned action versions (
@3,@3.3.0)
References
- Use
references/github-actions-guide.mdfor GitHub Actions workflow patterns and secrets table. - Use
references/generic-pipeline-guide.mdfor Azure DevOps, GitLab CI, and Jenkins patterns. - Use
references/secrets-management.mdfor OAuth S2S credential extraction and GitHub secrets setup. - Use
references/debugging.mdfor troubleshooting deploy failures, CI errors, and workspace promotion issues. - Use
references/checklist.mdfor pre-merge CI readiness validation. - Use
assets/deploy-stage.yml,assets/deploy-prod.yml,assets/pr-test.ymlas workflow templates. - Use
assets/fetch-secrets.shto extract secret values from workspace configuration. - Official Adobe docs: https://developer.adobe.com/app-builder/docs/guides/app_builder_guides/deployment/cicd-using-github-actions
Common Issues
- Workflow not triggering: Verify workflow files are committed to the default branch and triggers match your branching strategy.
- Deploy fails with auth error: The
authcommand is deprecated. Ensure you are using OAuth S2S credentials, not JWT. Verify all 14 secrets are set correctly with the right workspace suffix. - "I/O Management API not found": Add the I/O Management API service to the workspace in Developer Console before extracting secrets.
- Environment secrets not working: App Builder does NOT support GitHub environment secrets. Move all secrets to repository-level secrets.
- Missing secrets: Run
fetch-secrets.shand compare output against the 14-secret table inreferences/github-actions-guide.md. Each value must be present and correctly suffixed. - Custom env vars not available in action: Add custom secrets under the
envkey in the Deploy step of the workflow, not just in GitHub secrets.
Chaining
- Chains FROM
appbuilder-action-scaffolder(after actions are implemented) - Chains FROM
appbuilder-testing(automated test execution in CI) - Standalone after setup (workflows run automatically on push/PR/release)
© NeverSight, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 12 other files in data/skills-md/adobe/skills/appbuilder-cicd-pipeline of NeverSight/learn-skills.dev.
- SKILL.md
- description_ar.txt
- description_cn.txt
- description_de.txt
- description_en.txt
- description_es.txt
- description_fr.txt
- description_it.txt
- description_ja.txt
- description_ko.txt
- description_ru.txt
- description_tw.txt
- stats.json
Open the folder on GitHubat commit 50f7fc9
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NeverSight/learn-skills.dev, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Appbuilder Cicd Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Appbuilder Cicd Pipeline this skillNeverSight/learn-skills.dev | 216 | 1 repos | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Authoring GitHub Workflowsdotnet/skills | 5.6k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Megalinter Checknvuillam/npm-groovy-lint | 248 | 1 repos | ~3.9k | Automated safety check: Notes | MIT | |
| CI CDEliasOulkadi/shokunin | 114 | — | ~3.4k | Automated safety check: Notes | MIT | |
| Tirith PoliciesStackGuardian/tirith | 170 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
Megalinter Check
nvuillam/npm-groovy-lint
Collect MegaLinter lint errors for the current repository. An agent skill from nvuillam/npm-groovy-lint.
CI CD
EliasOulkadi/shokunin
Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…
Tirith Policies
StackGuardian/tirith
Write, validate, run and debug Tirith IaC governance policies, install Tirith, and add it to a CI pipeline (GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins, Azure DevOps, CircleCI or any…
- Official
Sdaf Orientation And Surface
Azure/sap-automation
Orient a newcomer to the SAP Deployment Automation Framework (SDAF): explain the spine (control plane → workload zone → SAP system → software → install → operate/remove), summarise the three…
More from NeverSight/learn-skills.dev
All 42 skills in this repoAI Marketing Videos
NeverSight/learn-skills.dev
Create AI marketing videos for ads, promos, product launches, and brand content.
Google Calendar
NeverSight/learn-skills.dev
Interact with Google Calendar via the Google Calendar API – list upcoming events, create new events, update or delete them.
Agent Orchestrator
NeverSight/learn-skills.dev
Meta-agent skill for orchestrating complex tasks through autonomous sub-agents.
AI Automation Workflows
NeverSight/learn-skills.dev
Build automated AI workflows combining multiple models and services.
AI Content Pipeline
NeverSight/learn-skills.dev
Build multi-step AI content creation pipelines combining image, video, audio, and text.
AI Podcast Creation
NeverSight/learn-skills.dev
Create AI-powered podcasts with text-to-speech, music, and audio editing.
Related
Works with
Categories
Questions about Appbuilder Cicd Pipeline
What does Appbuilder Cicd Pipeline do?
Set up CI/CD pipelines for Adobe App Builder projects. An agent skill from NeverSight/learn-skills.dev. dev. Set up CI/CD pipelines for Adobe App Builder projects.
When should I use Appbuilder Cicd Pipeline?
Appbuilder Cicd Pipeline fits situations like: the user mentions CI/CD for App Builder; GitHub Actions for aio deploy; automated deployment pipelines; continuous integration.
How do I install Appbuilder Cicd Pipeline in Claude Code?
Run `npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a claude-code`. Or copy the skill folder (data/skills-md/adobe/skills/appbuilder-cicd-pipeline in NeverSight/learn-skills.dev) into .claude/skills/appbuilder-cicd-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Appbuilder Cicd Pipeline in Codex?
Run `npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a codex`. Or copy the skill folder (data/skills-md/adobe/skills/appbuilder-cicd-pipeline in NeverSight/learn-skills.dev) into .agents/skills/appbuilder-cicd-pipeline in your project. Codex loads it when a task matches its description.
Can I use Appbuilder Cicd Pipeline in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeverSight/learn-skills.dev --skill appbuilder-cicd-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/appbuilder-cicd-pipeline, .gemini/skills/appbuilder-cicd-pipeline, .github/skills/appbuilder-cicd-pipeline and .opencode/skills/appbuilder-cicd-pipeline in your project.
What does Appbuilder Cicd Pipeline need to run?
SKILL.md names no scripts, command-line tools or credentials: Appbuilder Cicd Pipeline is instructions for the agent only. Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(aio:*), Bash(npm:*), Bash(git:*), Read, Write, Edit. Compatibility (from SKILL.md): Requires aio CLI, Node.js 18+, and a CI/CD platform (GitHub Actions, Azure DevOps, or GitLab CI).
Does Appbuilder Cicd Pipeline access the network?
SKILL.md names 1 domain. As links in the text: developer.adobe.com. This is read from the text; nothing was executed.
Is Appbuilder Cicd Pipeline safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Appbuilder Cicd Pipeline use?
Appbuilder Cicd Pipeline is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Appbuilder Cicd Pipeline use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Appbuilder Cicd Pipeline?
Skills that share tags, products or a category with Appbuilder Cicd Pipeline: Authoring GitHub Workflows (dotnet/skills, 5.6k stars), ONNX Runtime CI Management (microsoft/onnxruntime, 22k stars), Megalinter Check (nvuillam/npm-groovy-lint, 248 stars) and CI CD (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Appbuilder Cicd Pipeline?
NeverSight (a GitHub organization) maintains it in NeverSight/learn-skills.dev, which has 216 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on October 9, 2026.
Source: NeverSight/learn-skills.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.