fastlike
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.
What this skill does
## Trigger and scope
Trigger on: Fastly Compute, Compute@Edge, WASM on Fastly, fastlike, XQD ABI, Compute request lifecycle, 508 loop detection, backend subrequests, body streaming, profiling a local Compute app, embedding a Fastly Compute runtime in Go code, or any question about how Compute platform primitives work internally (caching, KV stores, edge rate limiting, ACLs, geolocation, secret stores, config stores, dictionaries, logging, dynamic backends, request collapsing, async I/O).
Do NOT use for: Fastly VCL (use falco), Fastly CLI/API (use fastly-cli or fastly), Viceroy, CDN comparison, WAF, Terraform, cache purging via API, or Fastly logging/stats configuration.
# Fastlike — Local Compute Runtime & Reference
Fastlike is a Go implementation of the Fastly Compute ABI. It runs compiled WebAssembly programs locally, implementing the same 249+ host functions that Fastly's production Compute platform provides: backends, dictionaries, KV stores, caching, geolocation, rate limiting, ACLs, secret stores, and more.
Equally important, **the fastlike source code is the most complete programmatic specification of how Fastly Compute works** — its ABI implementations document every platform primitive, request lifecycle detail, and data structure as executable code.
**Fastlike documentation**: https://github.com/avidal/fastlike
## Source Code as Compute Reference
When you have access to the fastlike source code locally (default: `~/src/fastlike`), use these paths to answer specific Compute questions:
| Question | Read This File | Why |
| ----------------------------------------------------------- | ---------------------------------------------------- | --------------------------------------------------------------- |
| "How does the request lifecycle work?" | `instance.go`, `xqd_http_downstream.go` | Per-request setup, execution, downstream handling |
| "What ABI functions exist for X?" | `xqd_*.go` files | Each file implements a group of related ABI functions |
| "How do backend subrequests work?" | `xqd_backend.go`, `backend.go` | Request sending, dynamic backends, timeouts |
| "How does caching work?" | `xqd_cache.go`, `xqd_http_cache.go`, `cache.go` | Cache operations, Vary, surrogate keys, request collapsing |
| "How does KV store work?" | `xqd_kv_store.go`, `kv_store.go` | CRUD operations, pagination, generation-based concurrency |
| "How does rate limiting work?" | `xqd_erl.go`, `erl.go` | Rate counters, penalty boxes, threshold checks |
| "How do ACLs work?" | `xqd_acl.go`, `acl.go` | CIDR-based IP filtering, most-specific match |
| "What configuration options exist?" | `options.go` | Every `With*` functional option for the runtime |
| "What error codes can operations return?" | `constants.go` | All XQD status codes and error types |
| "How does the profiler work / what does a trace look like?" | `profile.go`, `profile_json.go`, `docs/profiling.md` | Trace data model, JSON wire format, deep-mode metrics, encoders |
For a comprehensive guide, see [understanding-compute-from-source.md](references/understanding-compute-from-source.md).
## Install from Source
Requires Go 1.24+.
```bash
# Clone and build
git clone https://github.com/avidal/fastlike.git ~/src/fastlike
cd ~/src/fastlike
make build # Creates bin/fastlike
# Or install to GOPATH/bin
make install
# Or install directly
go install fastlike.dev/cmd/fastlike@latest
```
## Quick Start
```bash
# Minimal: WASM + single backend. The wasm path is positional.
bin/fastlike -backend localhost:8000 app.wasm
```
Flags can appear on either side of the wasm path.
## Fastlike vs Viceroy
| Feature | Fastlike | Viceroy |
| -------------- | ---------------------------- | ----------------------------------------- |
| Language | Go | Rust |
| Geolocation | Custom JSON file (`-geo`) | Built-in defaults |
| Hot reload | SIGHUP (`-reload`) | Restart required |
| Install | `go install` or `make build` | `cargo install` or `fastly compute serve` |
| Local backends | `-backend name=host:port` | `[local_server.backends]` in fastly.toml |
**When to use Fastlike**: Non-Rust Compute apps, want custom geo data, need hot reload, debugging.
**When to use Viceroy**: Rust Compute apps with cargo-nextest, Component Model projects, using `fastly compute serve`.
## Common Configurations
**With named backends:**
```bash
bin/fastlike \
-backend api=api.example.com:8080 \
-backend cache=redis:6379 \
-backend localhost:8000 \
app.wasm
```
**Development mode with hot-reload:**
```bash
bin/fastlike -backend localhost:8000 -reload -v 2 app.wasm
```
Send `SIGHUP` to reload the WASM without restarting.
**With the built-in profiler:**
```bash
bin/fastlike -backend localhost:8000 -profile-ui localhost:6060 app.wasm
```
Open `http://localhost:6060/` for the trace index. Each request lands as `/r/{id}` (HTML) or `/r/{id}.json` (canonical native JSON; also `.chrome.json`, `.firefox.json`, `.pprof`). Add `-profile deep` for body byte / cache outcome / header / wasm heap metrics. Non-loopback `-profile-ui` requires `-profile-auth TOKEN` (or explicit `-profile-insecure-ui`). See [profiling.md](references/profiling.md).
**Full configuration:**
```bash
bin/fastlike \
-bind 0.0.0.0:5000 \
-backend localhost:8000 \
-dictionary config=./config.json \
-kv store=./data.json \
-config-store settings=./settings.json \
-secret-store secrets=./secrets.json \
-acl blocklist=./acl.json \
-logger output=./logs.txt \
-geo ./geodata.json \
-compliance-region us-eu \
-v 2 \
-reload \
app.wasm
```
## Required Arguments
| Argument | Description |
| ------------------------------ | ---------------------------------------------------------- |
| `<wasm-file>` | Positional path to the WebAssembly program (required) |
| `-backend VALUE` or `-b VALUE` | Backend server (required, repeatable) |
## Optional Flags
| Flag | Default | Description |
| ------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------- |
| `-bind ADDR` | `localhost:8000` | Server bind address |
| `-reload` | false | Enable SIGHUP hot-reload |
| `-v INT` | 0 | Verbosity (0-2) |
| `-dictionary NAME=FILE` or `-d` | - | Load dictionary from JSON Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.