New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fastly Compute Backend Production Setup

by divinevideo in divinevideo/divine-mobile

Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge.

MPL-2.0Auto-check passedDevOps & Cloud

Install Fastly Compute Backend Production Setup

skills CLI
$ npx skills add divinevideo/divine-mobile --skill fastly-compute-backend-production-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install divinevideo/divine-mobile fastly-compute-backend-production-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fastly-compute-backend-production-setup .claude/skills/fastly-compute-backend-production-setup && rm -rf skills-src

Use ~/.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/

Facts

Skill name
fastly-compute-backend-production-setup
GitHub stars
266
Token cost
~1.2k tokens
SKILL.md length
369 words
Files
1
Skills in repo
103
Repo updated
First seen
Licence
MPL-2.0

At a glance

Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge.

  • Works in 4 steps: Create the backend via CLI → Activate the new version → Verify backend exists → …
  • Backend works locally but fails in production with backend does not exist
  • SKILL.md covers Problem, Context / Trigger Conditions, Root Cause and Solution, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fastly Compute Backend Production Setup is an agent skill from divinevideo/divine-mobile. Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Use when: (1) Backend works locally but fails in production with "backend does not exist", (2) TLS alert received (alertid=0) errors when calling external APIs from Fastly, (3) Backends defined in fastly.toml aren't available after deployment. The fastly.toml [[backends]] section only applies during initial service creation - existing services require backends to be added via CLI or API with proper SSL/SNI configuration.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. The licence is MPL-2.0.

When your agent uses it

  • Backend works locally but fails in production with backend does not exist
  • TLS alert received (alertid=
  • Errors when calling external APIs from Fastly
  • Backends defined in fastly.toml arent available after deployment

Example prompts

  • “Requested backend named”
  • “does not exist”
  • “backend does not exist”
  • “/fastly-compute-backend-production-setup”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Create the backend via CLI
  2. Activate the new version
  3. Verify backend exists
  4. Redeploy your code

What it can do on your machine

Read from SKILL.md and the folder at commit c3d6f7e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and toml).

    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):

    • fastly.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.

Context cost

Fastly Compute Backend Production Setup loads about 1.2k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 369 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~140
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 passed

The automated check found no risky patterns in SKILL.md.

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 divinevideo/divine-mobile at commit c3d6f7e, republished under its MPL-2.0 licence (© divinevideo). 369 words, ~1,183 tokens.

Download SKILL.mdSave it as .claude/skills/fastly-compute-backend-production-setup/SKILL.md (or your agent's skills folder).
name
fastly-compute-backend-production-setup
description
Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Use when: (1) Backend works locally but fails in production with "backend does not exist", (2) TLS alert received (alert_id=0) errors when calling external APIs from Fastly, (3) Backends defined in fastly.toml aren't available after deployment. The fastly.toml [[backends]] section only applies during initial service creation - existing services require backends to be added via CLI or API with proper SSL/SNI configuration.
author
Claude Code
version
1.0.0
date
2025-01-28

Fastly Compute Backend Production Setup

Problem

Backends defined in fastly.toml work during local development with fastly compute serve but return "Requested backend named 'X' does not exist" errors in production after deployment with fastly compute publish.

Context / Trigger Conditions

  • Error: Requested backend named 'funnelcake' does not exist
  • Error: TLS alert received (alert_id=0) when connecting to HTTPS backends
  • Backend works with fastly compute serve locally
  • fastly.toml has [[backends]] section properly configured
  • Service was created before the backend was added to fastly.toml

Root Cause

The [[backends]] section in fastly.toml is only processed during initial service creation via the [setup] configuration. Once a service exists, changes to backends in fastly.toml are ignored - you must add/modify backends through the Fastly CLI or API.

From the Fastly CLI output:

INFO: Processing of the fastly.toml [setup] configuration happens only for a new service. Once a service is created, any further changes to the service or its resources must be made manually.

Solution

Step 1: Create the backend via CLI
bash
fastly backend create \
  --service-id YOUR_SERVICE_ID \
  --version active \
  --autoclone \
  --name backend-name \
  --address api.example.com \
  --port 443 \
  --override-host api.example.com \
  --use-ssl \
  --ssl-cert-hostname api.example.com \
  --ssl-sni-hostname api.example.com

Key flags:

  • --autoclone: Creates a new version automatically
  • --ssl-cert-hostname: Required for SSL certificate validation
  • --ssl-sni-hostname: Required for TLS SNI (fixes alert_id=0 errors)
Step 2: Activate the new version
bash
fastly service-version activate --service-id YOUR_SERVICE_ID --version VERSION_NUMBER
Step 3: Verify backend exists
bash
fastly backend list --service-id YOUR_SERVICE_ID --version active
Step 4: Redeploy your code

After adding the backend, redeploy to ensure the code and backend are in the same version:

bash
fastly compute publish

Then verify backends still exist in the new version:

bash
fastly backend list --service-id YOUR_SERVICE_ID --version active
Show full SKILL.md (143 more words)Show less

Verification

  1. Check logs with fastly log-tail --service-id YOUR_SERVICE_ID
  2. Make a request that uses the backend
  3. Confirm no "backend does not exist" or TLS errors in logs

Example

Given this fastly.toml (which works locally but not in production):

toml
[[backends]]
  name = "funnelcake"
  address = "relay.dvines.org"
  port = 443
  override_host = "relay.dvines.org"
  use_ssl = true

Add the backend to an existing service:

bash
# Create backend with SSL properly configured
fastly backend create \
  --service-id WfOrPTFYmwwxRvqrfralLA \
  --version active \
  --autoclone \
  --name funnelcake \
  --address relay.dvines.org \
  --port 443 \
  --override-host relay.dvines.org \
  --use-ssl \
  --ssl-cert-hostname relay.dvines.org \
  --ssl-sni-hostname relay.dvines.org

# Activate the new version
fastly service-version activate --service-id WfOrPTFYmwwxRvqrfralLA --version 49

# Redeploy code
fastly compute publish

Notes

  • Each fastly compute publish creates a new version that inherits backends from the previous active version
  • If you need different backends for different environments, consider using environment variables or separate services
  • The --autoclone flag is essential - you cannot modify an active version directly
  • Backend names in your code must exactly match the --name parameter
  • Requested backend named 'X' does not exist - Backend not created in service
  • TLS alert received (alert_id=0) - Missing SNI hostname configuration
  • Mandatory SSL cert checks require specifying cert hostname - Missing ssl-cert-hostname

References

© divinevideo, MPL-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

Just SKILL.md in .agents/skills/fastly-compute-backend-production-setup of divinevideo/divine-mobile.

Open the folder on GitHubat commit c3d6f7e

Compare with similar skills

Fastly Compute Backend Production Setup 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.

Fastly Compute Backend Production Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fastly Compute Backend Production Setup this skilldivinevideo/divine-mobile266—~1.2kAutomated safety check: PassMPL-2.0
Monitor CInrwl/nx29k6 repos~4.7kAutomated safety check: PassMIT
Terraform and OpenTofu Guideagentscope-ai/QwenPaw36k6 repos~4.2kAutomated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT

Similar skills

  • Monitor CI

    nrwl/nx

    Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.

    29k GitHub starsUsed in 6 repos~4.7k tokens
    DevOps & CloudAuto-check passed

  • Terraform and OpenTofu Guide

    agentscope-ai/QwenPaw

    Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.

    36k GitHub starsUsed in 6 repos~4.2k tokens
    DevOps & CloudAuto-check passed

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • Analyze GitHub Action Logs

    withastro/astro

    Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Docs Learn PR Preview

    netdata/netdata

    Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.

    81k GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

More from divinevideo/divine-mobile

All 103 skills in this repo

  • Argocd Externalsecret Namespace Permission

    divinevideo/divine-mobile

    Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".

    266 GitHub stars~931 tokensUpdated today
    Auto-check passed

  • Art Direct

    divinevideo/divine-mobile

    Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language.

    266 GitHub stars~4.8k tokensUpdated today
    Auto-check passed

  • Async Await Null Race Condition

    divinevideo/divine-mobile

    Fix "Null check operator used on a null value" errors when an object is set to null during an async await.

    266 GitHub stars~881 tokensUpdated today
    Auto-check passed

  • AWS V4 Signing Custom Headers Gcs

    divinevideo/divine-mobile

    Add custom metadata headers (x-amz-meta-) to AWS v4 signed requests for GCS S3-compatible API.

    266 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Bash Herestring Newline Secrets

    divinevideo/divine-mobile

    Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings.

    266 GitHub stars~791 tokensUpdated today
    Auto-check passed

  • Blossom Content Addressed URL Filtering

    divinevideo/divine-mobile

    Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp).

    266 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

Categories

Questions about Fastly Compute Backend Production Setup

What does Fastly Compute Backend Production Setup do?

Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge. Fastly Compute Backend Production Setup is an agent skill from divinevideo/divine-mobile. Fix "Requested backend named 'X' does not exist" or TLS alert errors in Fastly Compute@Edge.

When should I use Fastly Compute Backend Production Setup?

Fastly Compute Backend Production Setup fits situations like: backend works locally but fails in production with backend does not exist; TLS alert received (alertid=; errors when calling external APIs from Fastly; backends defined in fastly.toml arent available after deployment.

How do I install Fastly Compute Backend Production Setup in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill fastly-compute-backend-production-setup -a claude-code`. Or copy the skill folder (.agents/skills/fastly-compute-backend-production-setup in divinevideo/divine-mobile) into .claude/skills/fastly-compute-backend-production-setup in your project. Claude Code loads it when a task matches its description.

How do I install Fastly Compute Backend Production Setup in Codex?

Run `npx skills add divinevideo/divine-mobile --skill fastly-compute-backend-production-setup -a codex`. Or copy the skill folder (.agents/skills/fastly-compute-backend-production-setup in divinevideo/divine-mobile) into .agents/skills/fastly-compute-backend-production-setup in your project. Codex loads it when a task matches its description.

Can I use Fastly Compute Backend Production Setup 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 divinevideo/divine-mobile --skill fastly-compute-backend-production-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fastly-compute-backend-production-setup, .gemini/skills/fastly-compute-backend-production-setup, .github/skills/fastly-compute-backend-production-setup and .opencode/skills/fastly-compute-backend-production-setup in your project.

What does Fastly Compute Backend Production Setup need to run?

SKILL.md names no scripts, command-line tools or credentials: Fastly Compute Backend Production Setup is instructions for the agent only.

Does Fastly Compute Backend Production Setup access the network?

SKILL.md names 1 domain. As links in the text: fastly.com. This is read from the text; nothing was executed.

Is Fastly Compute Backend Production Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fastly Compute Backend Production Setup use?

Fastly Compute Backend Production Setup is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fastly Compute Backend Production Setup use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Fastly Compute Backend Production Setup?

Skills that share tags, products or a category with Fastly Compute Backend Production Setup: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fastly Compute Backend Production Setup?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 10, 2026.

Source: divinevideo/divine-mobile on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.