AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Gitlab Pages Ci

skill-frontier-ai-next-mgarlbot-gitlab-pages-ci · by frontier-ai-next

GitLab CI — test job and GitLab Pages job (artifact `public/`); `.gitlab-ci.yml` templates

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-frontier-ai-next-mgarlbot-gitlab-pages-ci

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-frontier-ai-next-mgarlbot-gitlab-pages-ci)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Gitlab Pages Ci? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

GitLab CI + Pages

The GitLab Runner executes the pipeline, not the bot. Your job is to add or fix .gitlab-ci.yml in the repo and list what to enable in GitLab (Settings → Pages, visibility).

General layout

  • stages: [test, deploy] (or [test, pages]).
  • test job: same stack as local (Python/Node/Go). Default image from process env GITLAB_CI_DEFAULT_IMAGE (e.g. python:3.12-bookworm) — use it in YAML if the project has no image:.
  • pages job: GitLab requires a public/ artifact. Build the static site (MkDocs, VitePress, sphinx -b html, SPA npm run build then copy into public/) and declare:
pages:
  stage: deploy
  needs: ["test"]
  script:
    - mkdir -p public
    - cp -r dist/* public/   # example; adapt to the project
  artifacts:
    paths:
      - public

Python (pytest) + minimal Pages stub

Template “tests + placeholder site”:

stages: [test, deploy]

variables:
  PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"

test:
  stage: test
  image: python:3.12-bookworm
  cache:
    paths: [.cache/pip]
  before_script:
    - python -m pip install -U pip
    - test -f requirements.txt && pip install -r requirements.txt || true
    - test -f pyproject.toml && pip install -e ".[dev]" || true
  script:
    - pytest -q || true

pages:
  stage: deploy
  needs: ["test"]
  image: alpine:latest
  script:
    - mkdir -p public
    - echo 'CIGitLab Pages OK' > public/index.html
  artifacts:
    paths: [public]

Tune pytest for the real layout (tests/, uv run, etc.).

Node / static frontend

  • image: node:22-bookworm (or project LTS).
  • cache: { paths: [node_modules/] }
  • script: npm ci && npm run build → output in dist/ or build/ → copy into public/.

Important

  • No secrets in YAML; use GitLab CI/CD Variables (masked).
  • If .gitlab-ci.yml already exists — extend stages/jobs; do not break production-branch deploy without explicit user approval.
  • After merge: Pages URL like https://.gitlab.io// (depends on settings); tell the user to check Deploy → Pages in the UI.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.