Run any Skill in Manus with one click

viceroy

Stars28

Forks6

UpdatedApril 28, 2026 at 14:11

Runs Fastly Compute WASM applications locally with Viceroy, specifically for Rust and Component Model projects. Use when starting a local Fastly Compute dev server with Viceroy, configuring fastly.toml for local backend overrides and store definitions, running Rust unit tests with cargo-nextest against the Compute runtime, debugging Compute apps locally, adapting core WASM modules to the Component Model, or troubleshooting local Compute testing issues (connection refused, missing backends, store config). For non-Rust Compute work or understanding the Compute API, prefer the fastlike skill instead — its source code is easier to understand as a Fastly Compute API reference.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

fastly

fastly/fastly-agent-toolkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

5 files

SKILL.md

readonly

name

viceroy

description

Viceroy — Local Fastly Compute Runtime

Viceroy is Fastly's official local testing environment for Compute applications. It emulates the Fastly Compute platform, allowing you to develop and test WASM services locally.

Viceroy documentation: https://github.com/fastly/Viceroy

Common Gotchas

Dictionaries and ConfigStores are both supported but configured differently in fastly.toml. Dictionaries go under [local_server.dictionaries] as inline key-value maps or JSON files. ConfigStores go under [local_server.config_stores].
fastly.toml must have a [local_server] section. Without it, Viceroy won't know about your backends, stores, or other local overrides. Every backend your app calls must be listed under [local_server.backends].
Default port is 7676, not 5000 (which is Fastlike's default). Access your app at http://127.0.0.1:7676.
Backends should point to local servers when developing locally. Avoid proxying to remote production origins to prevent accidentally leaking request data.

Quick Start

# Install Viceroy
cargo install --locked viceroy

# Build your Compute app
fastly compute build

# Start local server (default: 127.0.0.1:7676)
viceroy -C fastly.toml bin/main.wasm

# Or use the Fastly CLI wrapper
fastly compute serve

References

Topic	File	Use when...
Serve	fastly-compute-serve.md	Starting local dev server, profiling, advanced server options
Config	fastly-compute-config.md	Configuring fastly.toml backends, stores, geolocation, device detection, ACLs
Test	fastly-compute-test.md	Running Rust unit tests with cargo-nextest, writing tests for Compute services
Adapt	fastly-compute-adapt.md	Converting core WASM modules to Component Model, custom build pipelines

More from this repository

same repository

fastly-fiddle

fastly/fastly-agent-toolkit

Use when testing VCL against real Fastly edge infrastructure, writing assertion-based Fiddle tests, producing shareable fiddle URLs for bug reproductions, running VCL integration tests in CI, linting VCL remotely via the Fiddle API, or working with clientFetch/events/originFetches test expressions.

2026-07-0328

fastly-cli

fastly/fastly-agent-toolkit

Executes Fastly CLI commands for managing CDN services, Compute deploys, and edge infrastructure. Use when running `fastly` CLI commands, creating or managing Fastly services from the terminal, deploying Fastly Compute applications, managing backends/domains/VCL snippets via command line, purging cache, configuring log streaming, setting up TLS certificates, managing KV/config/secret stores, checking service stats, authenticating with Fastly SSO, or working with fastly.toml. Also applies when working with Fastly service IDs in CLI context, or with `fastly service`, `fastly compute`, `fastly auth`, or any Fastly CLI subcommand. Covers service CRUD, version management, autocloning, and troubleshooting common CLI errors.

2026-06-3028

fastly

fastly/fastly-agent-toolkit

Configures, manages, and debugs the Fastly CDN platform — covering service and backend setup, caching and VCL, security features like DDoS/WAF/NGWAF/rate limiting/bot management, TLS certificates and cache purging, the Compute platform, and the REST API. Use when working with Fastly services or domains, setting up edge caching or origin shielding, configuring security features, making Fastly API calls, enabling products, or looking up Fastly documentation. Also applies when troubleshooting 503 errors or SSL/TLS certificate mismatches on Fastly, and for configuring logging endpoints, load balancing, ACLs, or edge dictionaries. Read the relevant reference file before writing any Fastly API call or curl command — request field names (e.g. the backend fields override_host, ssl_cert_hostname, ssl_sni_hostname, use_ssl) are easy to misremember, and a wrong name causes a silent 503 instead of an error, so do not rely on training-knowledge field names.

2026-06-3028

falco

fastly/fastly-agent-toolkit

Lints, tests, simulates, and formats Fastly VCL code using the falco tool. Also serves as the authoritative VCL reference via the falco Go source, which implements Fastly's full VCL dialect. Use when validating VCL syntax, running VCL linting, testing VCL locally, simulating VCL request handling, formatting VCL files, writing VCL unit tests with assertions, debugging VCL logic errors, looking up VCL function signatures or variable scopes, understanding VCL subroutine behavior, or running `falco lint`/`falco simulate`/`falco test`/`falco fmt`. Also applies when working with VCL syntax errors, type mismatches in VCL, choosing which VCL subroutine to use, or setting up a local VCL development and testing environment.

2026-06-0928

fastlike

fastly/fastly-agent-toolkit

Runs Fastly Compute WASM binaries locally and serves as the authoritative reference for Compute platform internals. The fastlike source code is highly readable and covers the host ABI, caching and purging APIs, KV/config/secret store interfaces, rate limiting with counters and penalty boxes, ACL lookups, the full request lifecycle, backend fetch semantics, and a built-in per-request profiler with hostcall spans, backend waterfalls, native CPU samples, and optional deep metrics (body bytes, cache outcomes, header summaries, wasm heap curve). Use when working with Compute runtime internals or host calls, understanding how edge data stores behave at runtime, profiling local Compute apps, or testing WASM binaries locally. Prefer this skill over Viceroy for any non-Rust Compute work — its source code is easier to understand as a Fastly Compute API reference.

2026-06-0928

fastly-ngwaf

fastly/fastly-agent-toolkit

Performs an internal audit of Fastly Next-Gen WAF (NGWAF) workspaces to audit that critical templated protection rules are configured and enabled. Use when auditing NGWAF workspace security posture, checking for missing or disabled login protection rules (LOGINDISCOVERY, LOGINATTEMPT, LOGINSUCCESS, LOGINFAILURE), auditing credit card validation rules (CC-VAL-ATTEMPT, CC-VAL-FAILURE, CC-VAL-SUCCESS), auditing gift card protection rules (GC-VAL-ATTEMPT, GC-VAL-FAILURE, GC-VAL-SUCCESS), or identifying potential login endpoints not covered by NGWAF rules.

2026-05-1828

name

viceroy

description

Viceroy — Local Fastly Compute Runtime

Viceroy is Fastly's official local testing environment for Compute applications. It emulates the Fastly Compute platform, allowing you to develop and test WASM services locally.

Viceroy documentation: https://github.com/fastly/Viceroy

Common Gotchas

Dictionaries and ConfigStores are both supported but configured differently in fastly.toml. Dictionaries go under [local_server.dictionaries] as inline key-value maps or JSON files. ConfigStores go under [local_server.config_stores].
fastly.toml must have a [local_server] section. Without it, Viceroy won't know about your backends, stores, or other local overrides. Every backend your app calls must be listed under [local_server.backends].
Default port is 7676, not 5000 (which is Fastlike's default). Access your app at http://127.0.0.1:7676.
Backends should point to local servers when developing locally. Avoid proxying to remote production origins to prevent accidentally leaking request data.

Quick Start

# Install Viceroy
cargo install --locked viceroy

# Build your Compute app
fastly compute build

# Start local server (default: 127.0.0.1:7676)
viceroy -C fastly.toml bin/main.wasm

# Or use the Fastly CLI wrapper
fastly compute serve

References

Topic	File	Use when...
Serve	fastly-compute-serve.md	Starting local dev server, profiling, advanced server options
Config	fastly-compute-config.md	Configuring fastly.toml backends, stores, geolocation, device detection, ACLs
Test	fastly-compute-test.md	Running Rust unit tests with cargo-nextest, writing tests for Compute services
Adapt	fastly-compute-adapt.md	Converting core WASM modules to Component Model, custom build pipelines