Aspire
microsoft/aspire.dev
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps.
Debug Fastly Compute deployments that appear successful but return stale/wrong responses.
Install Fastly Compute Deployment Debugging
$ npx skills add divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install divinevideo/divine-mobile fastly-compute-deployment-debugging --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/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .claude/skills/fastly-compute-deployment-debugging && 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 "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .claude/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debuggingType 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 divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install divinevideo/divine-mobile fastly-compute-deployment-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .agents/skills/fastly-compute-deployment-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .agents/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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 divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install divinevideo/divine-mobile fastly-compute-deployment-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .cursor/skills/fastly-compute-deployment-debugging && 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 "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .cursor/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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/divinevideo/divine-mobile.git --path .agents/skills/fastly-compute-deployment-debugging--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 divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install divinevideo/divine-mobile fastly-compute-deployment-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .gemini/skills/fastly-compute-deployment-debugging && 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 "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .gemini/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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 divinevideo/divine-mobile fastly-compute-deployment-debuggingInstalls 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 divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .github/skills/fastly-compute-deployment-debugging && 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 "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .github/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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 divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install divinevideo/divine-mobile fastly-compute-deployment-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fastly-compute-deployment-debugging .opencode/skills/fastly-compute-deployment-debugging && 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 "fastly-compute-deployment-debugging" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/fastly-compute-deployment-debugging into .opencode/skills/fastly-compute-deployment-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fastly-compute-deployment-debugging", 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
fastly-compute-deployment-debugging- GitHub stars
- 265
- Token cost
- ~1.3k tokens
- SKILL.md length
- 416 words
- Files
- 1
- Skills in repo
- 103
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Debug Fastly Compute deployments that appear successful but return stale/wrong responses.
- Works in 6 steps: Verify Code is Actually Deployed → Diagnose Cached Error Responses → Check Domain Configuration (Two APIs!) → …
- Fastly compute publish succeeds but version check shows old version
- SKILL.md covers Problem, Context / Trigger Conditions, Solution and Verification, plus 3 more sections
- Calls curl; reaches custom-domain.com and service.edgecompute.app
What it does
Fastly Compute Deployment Debugging is an agent skill from divinevideo/divine-mobile. Debug Fastly Compute deployments that appear successful but return stale/wrong responses. Use when: (1) fastly compute publish succeeds but version check shows old version, (2) new endpoints return 404 after deployment, (3) cache-busted requests work but regular requests fail, (4) fastly domain list doesn't show your custom domain. Covers edge propagation timing, cached error responses, and domain management API differences.
Its SKILL.md is about 1.3k 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, covering Deployment and Debugging. The licence is MPL-2.0.
When your agent uses it
- Fastly compute publish succeeds but version check shows old version
- New endpoints return 404 after deployment
- Cache-busted requests work but regular requests fail
- Fastly domain list doesnt show your custom domain
Example prompts
- “/fastly-compute-deployment-debugging”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8d5fbf2. 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
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
custom-domain.comservice.edgecompute.appapi.fastly.com
Also links to:
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 Deployment Debugging loads about 1.3k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 416 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 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 8d5fbf2, republished under its MPL-2.0 licence (© divinevideo). 416 words, ~1,284 tokens.
Download SKILL.mdSave it as
.claude/skills/fastly-compute-deployment-debugging/SKILL.md (or your agent's skills folder).- name
- fastly-compute-deployment-debugging
- description
- Debug Fastly Compute deployments that appear successful but return stale/wrong responses. Use when: (1) fastly compute publish succeeds but version check shows old version, (2) new endpoints return 404 after deployment, (3) cache-busted requests work but regular requests fail, (4) fastly domain list doesn't show your custom domain. Covers edge propagation timing, cached error responses, and domain management API differences.
- author
- Claude Code
- version
- 1.0.0
- date
- 2026-01-21
Fastly Compute Deployment Debugging
Problem
After deploying to Fastly Compute, requests return stale content or 404s even though:
fastly compute publishreported success- The new version shows as "active" in
fastly service-version list - The code is correct and works locally
Context / Trigger Conditions
- Version endpoint returns old version string after deployment
- New routes/features return 404
fastly purge --alldoesn't fix the issue- Requests with cache buster (
?v=random) work but regular requests don't fastly domain listdoesn't show your custom domain- Different POPs return different results
Solution
1. Verify Code is Actually Deployed
# Check the direct edgecompute.app URL (bypasses custom domain config)
curl https://your-service.edgecompute.app/version
# Compare to custom domain
curl https://your-custom-domain.com/versionIf edgecompute.app works but custom domain doesn't, it's a domain configuration issue.
2. Diagnose Cached Error Responses
The most common issue: 404s get cached at edge POPs before new code propagates.
# Test with cache buster
curl "https://your-domain.com/endpoint?bust=$RANDOM"
# Test without
curl "https://your-domain.com/endpoint"If cache-busted works but regular doesn't = cached error response.
Fix: Wait 2-5 minutes for full propagation, then purge:
fastly purge --all --service-id YOUR_SERVICE_ID3. Check Domain Configuration (Two APIs!)
Fastly has TWO domain management systems:
| System | CLI Command | API Endpoint |
|---|---|---|
| Classic Domains | fastly domain list | /service/{id}/version/{ver}/domain |
| Versionless Domains | (not shown in CLI) | /domain-management/v1/domains |
If fastly domain list doesn't show your domain, check the versionless API:
# Get your API token
TOKEN=$(fastly profile token)
# Query domain-management API
curl -s -H "Fastly-Key: $TOKEN" \
"https://api.fastly.com/domain-management/v1/domains?filter%5Bfqdn%5D=your-domain.com"Look for "activated": true and "verified": true.
4. Force Clean Rebuild
If build caching is suspected:
rm -rf pkg target
fastly compute publish --comment "clean build"5. Wait for Propagation
Fastly Compute deployments can take 2-5 minutes to propagate to all POPs worldwide.
Even after fastly service-version list shows the version as active, some POPs may
still serve old code.
Timeline:
- Version marked "active": ~30 seconds
- Most POPs updated: ~1-2 minutes
- All POPs updated: ~3-5 minutes (sometimes longer)
Show full SKILL.md (165 more words)Show less
6. Check Real-time Logs
fastly log-tail --service-id YOUR_SERVICE_IDThen make a request and see if it appears. If no logs appear, the request isn't reaching your Compute code (likely a domain/routing issue).
Verification
After waiting and purging:
# Multiple requests to hit different POPs
for i in 1 2 3 4 5; do
curl -s "https://your-domain.com/version"
sleep 1
doneAll should return the new version.
Example
Scenario: Deployed thumbnail serving code, but /hash.jpg returns 404.
Debug steps:
curl https://service.edgecompute.app/hash.jpg?v=123→ 200 (code works!)curl https://custom-domain.com/hash.jpg→ 404 (cached)- Wait 3 minutes
fastly purge --all --service-id XXXcurl https://custom-domain.com/hash.jpg→ 200 (working!)
Root cause: 404 was cached at edge before new code propagated.
Notes
- Accounts created before Sept 2025: May have classic domains, newer accounts use versionless
- Don't panic: If version check works on edgecompute.app, the code is deployed - just wait
- Purge timing: Purge AFTER propagation completes, not immediately after deploy
- POP variance: Different geographic POPs may propagate at different speeds
- Error caching: Fastly may cache 404/500 responses - this amplifies propagation issues
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-deployment-debugging of divinevideo/divine-mobile.
Open the folder on GitHubat commit 8d5fbf2
Compare with similar skills
Fastly Compute Deployment Debugging 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 |
|---|---|---|---|---|---|---|
| Fastly Compute Deployment Debugging this skilldivinevideo/divine-mobile | 265 | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| Aspiremicrosoft/aspire.dev | 196 | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Operating Livekit Agentslivekit-examples/agent-starter-python | 264 | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Medusa Cloud Local Buildmedusajs/medusa-agent-skills | 225 | — | ~1k | Automated safety check: Notes | None | |
| Tonic System DeployLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Release Engineeringmagnus919/agent-skills | 111 | — | ~3.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Operating Livekit Agents
livekit-examples/agent-starter-python
Deploys and operates a LiveKit agent in production: shipping a version to LiveKit Cloud and rolling it back, secrets and configuration, the worker process model and prewarming, safe async inside…
Medusa Cloud Local Build
medusajs/medusa-agent-skills
Reproduces a Medusa Cloud build on your machine with mcloud local build, to debug build-failed deployments without pushing or waiting on Cloud.
Tonic System Deploy
LeoYeAI/openclaw-master-skills
Software deployment workflow for systems with separate UAT and PROD environments.
Release Engineering
magnus919/agent-skills
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags…
Frontend Forge Extension Operations
kubesphere/kubesphere
Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.
More from divinevideo/divine-mobile
All 103 skills in this repoArgocd Externalsecret Namespace Permission
divinevideo/divine-mobile
Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y".
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.
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.
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.
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.
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).
Related
Categories
Questions about Fastly Compute Deployment Debugging
What does Fastly Compute Deployment Debugging do?
Debug Fastly Compute deployments that appear successful but return stale/wrong responses. Fastly Compute Deployment Debugging is an agent skill from divinevideo/divine-mobile. Debug Fastly Compute deployments that appear successful but return stale/wrong responses.
When should I use Fastly Compute Deployment Debugging?
Fastly Compute Deployment Debugging fits situations like: fastly compute publish succeeds but version check shows old version; new endpoints return 404 after deployment; cache-busted requests work but regular requests fail; fastly domain list doesnt show your custom domain.
How do I install Fastly Compute Deployment Debugging in Claude Code?
Run `npx skills add divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a claude-code`. Or copy the skill folder (.agents/skills/fastly-compute-deployment-debugging in divinevideo/divine-mobile) into .claude/skills/fastly-compute-deployment-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Fastly Compute Deployment Debugging in Codex?
Run `npx skills add divinevideo/divine-mobile --skill fastly-compute-deployment-debugging -a codex`. Or copy the skill folder (.agents/skills/fastly-compute-deployment-debugging in divinevideo/divine-mobile) into .agents/skills/fastly-compute-deployment-debugging in your project. Codex loads it when a task matches its description.
Can I use Fastly Compute Deployment Debugging 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-deployment-debugging -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-deployment-debugging, .gemini/skills/fastly-compute-deployment-debugging, .github/skills/fastly-compute-deployment-debugging and .opencode/skills/fastly-compute-deployment-debugging in your project.
What does Fastly Compute Deployment Debugging need to run?
Going by SKILL.md and its folder, Fastly Compute Deployment Debugging needs the command-line tools its instructions call (curl).
Does Fastly Compute Deployment Debugging access the network?
SKILL.md names 4 domains. In commands or code: custom-domain.com, service.edgecompute.app and api.fastly.com; the agent is likely to contact these when it follows the instructions. As links in the text: fastly.com. This is read from the text; nothing was executed.
Is Fastly Compute Deployment Debugging 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 Deployment Debugging use?
Fastly Compute Deployment Debugging 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 Deployment Debugging use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Deployment Debugging?
Skills that share tags, products or a category with Fastly Compute Deployment Debugging: Aspire (microsoft/aspire.dev, 196 stars), Operating Livekit Agents (livekit-examples/agent-starter-python, 264 stars), Medusa Cloud Local Build (medusajs/medusa-agent-skills, 225 stars) and Tonic System Deploy (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fastly Compute Deployment Debugging?
divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 265 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 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.