docs-deployment

docs-deployment is a skill for Claude Code from cdskill/qalma. It costs 107 tokens per session (2,042 once invoked), scanned A, original, MIT.

A deployment guide for the Qalma documentation website, which is a statically generated site served from Amazon S3 and CloudFront.

In plain words
What is it for?
Use it when working on the docs site's S3 or CDN hosting, infrastructure, caching, domain, TLS certificate, deployment role, or CI deployment workflow.
Why use it?
It explains how the documentation is built, cached, secured, and released so hosting changes follow the project's existing setup.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

Good fit Use it when working on the docs site's S3 or CDN hosting, infrastructure, caching, domain, TLS certificate, deployment role, or CI deployment workflow.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cdskill/qalma/docs-deployment
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cdskill/qalma --skill docs-deployment
Clone the repo
git clone --depth 1 https://github.com/cdskill/qalma

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for docs-deployment

README.md
[![agentmods](https://agentmods.dev/badge/skills/cdskill/qalma/docs-deployment/github.svg)](https://agentmods.dev/skills/cdskill/qalma/docs-deployment)
Your own site
<a href="https://agentmods.dev/skills/cdskill/qalma/docs-deployment"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/docs-deployment/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for docs-deployment

Your own site · 80×15
<a href="https://agentmods.dev/skills/cdskill/qalma/docs-deployment"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/docs-deployment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,042 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.02042
Opus 5.5 $0.00043 $0.00817
Sonnet 5.5 $0.00021 $0.00408
Haiku 4.5 $0.00011 $0.00204

Measured 1mo ago against content hash ff893314c77b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-deployment scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -I https://qalma.dev/ # 200, content-encoding: br
.claude/skills/docs-deployment/SKILL.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

docs-deployment

Infrastructure and delivery for apps/docs (the @qalma/editor docs site). This skill covers hosting and deployment only — not application code.

Hosting model: SSG (not SSR)

apps/docs is built as static site generation — prerendered HTML + hashed assets, no Node server at runtime. Configured in apps/docs/vite.config.ts via the Analog plugin: static: true + prerender (routes + discover) + sitemap host: 'https://qalma.dev/'. Deployable output: dist/apps/docs/analog/public/.

Why SSG over SSR for the docs:

  • Docs content only changes on redeploy → nothing to render per request.
  • SEO is identical to SSR (both ship fully-rendered HTML).
  • Better TTFB/FCP: prerendered HTML served from the CDN edge, no per-request compute.
  • Cheaper and zero ops: no server to run, scale or patch.

Why S3 + CloudFront over Amplify: the build stays in the existing Nx CI (single source of truth, Nx cache) instead of Amplify's own build system, and we get full control of Cache-Control per path — the real lever for FCP/TTFB. Amplify runs CloudFront underneath anyway, so there is no CDN/perf loss.

Architecture

GitHub Actions (nx affected → nx build docs)
        │  assumes IAM role via OIDC (no stored keys)
        ▼
   private S3 bucket  ◀── OAC ──  CloudFront (edge, HTTP/3, Brotli)  ──▶  https://qalma.dev
        ▲                                ▲
   aws s3 sync                    ACM cert (us-east-1) + Route 53 apex alias
   + invalidation

Where things live

  • IaC: infra/terraform/ — providers.tf (AWS + us_east_1 alias for the cert), s3.tf, cloudfront.tf, dns_cert.tf (Route 53 zone as data + ACM + A/AAAA aliases), iam_oidc.tf, variables.tf, outputs.tf, functions/rewrite.js. Human walkthrough: infra/terraform/README.md.
  • CI: .github/workflows/deploy.yml.
  • Deployable artifact: dist/apps/docs/analog/public/.

Infrastructure (Terraform/OpenTofu)

One terraform apply creates ~14 resources:

  • S3: private bucket (block public access on), bucket policy granting read only to this CloudFront distribution via OAC. No website endpoint.
  • CloudFront: distribution with http2and3, compress = true (Brotli/gzip), managed CachingOptimized policy, apex alias, PriceClass_All (global). A CloudFront Function (functions/rewrite.js, viewer-request) maps clean URLs to …/index.html; 403/404 custom_error_response → /index.html (SPA fallback).
  • ACM: DNS-validated cert in us-east-1 (required for CloudFront).
  • Route 53: cert-validation records + apex A/AAAA aliases to CloudFront (hosted zone must already exist; referenced as data).
  • IAM/OIDC: GitHub OIDC provider + least-privilege deploy role (S3 sync + CloudFront invalidation only), trust scoped to repo:cdskill/qalma:ref:refs/heads/main.

Read the full file on GitHub · 156 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 156 lines · 107 tokens per session scan A ff893314c77b

Subscribe to this mod's changes

docs-deployment is a skill published in the GitHub repository cdskill/qalma (10 stars, last pushed 2d ago), licensed MIT. It adds 107 tokens to every session and 2,042 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

terraform-fullstack-infrastructure-as-code

Manage fullstack cloud infrastructure with Terraform modules, environment promotion, drift detection, and safe rollout practices.

vaquarkhan/Fullstack-development-agent-skills · 28 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

mirrord-chaos

Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the mirrord chaos CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate…

metalbear-co/mirrord · 119 tokens

atmos-hooks

Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.

cloudposse/atmos · 46 tokens

atmos-modernization

Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.

cloudposse/atmos · 36 tokens

atmos-sbom

Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.

cloudposse/atmos · 36 tokens