Edge Computing

Deep edge computing workflow—what runs at edge vs origin, caching, KV and data locality, security, limits, and latency validation. Use when deploying to CDN/...

Security Scan

This is an instruction-only, platform-agnostic edge-computing workflow guide whose requirements and instructions are consistent with its stated purpose and do not request credentials or install code.

Purpose & Capability

The skill name and description match the SKILL.md content: it provides architecture and rollout guidance for CDN/edge deployments. It does not request unrelated binaries, env vars, or accesses that would be incoherent with an advisory workflow.

Instruction Scope

The instructions are high-level procedural guidance (six stages, checklist, tips). They do not instruct the agent to read system files, access credentials, contact external endpoints, or perform other actions outside advisory scope.

Install Mechanism

No install spec and no code files are present (instruction-only). That minimizes on-disk risk; nothing is downloaded or executed by the skill itself.

Credentials

The skill declares no required environment variables, credentials, or config paths. There is no disproportionate request for secrets or unrelated service keys.

Persistence & Privilege

The skill is not marked always:true and does not request persistent system presence or modify other skills. Agent autonomous invocation is allowed by platform default but not escalated by this skill.

Assessment

This skill is a generic, read-only workflow checklist for edge deployments and appears coherent and low-risk. Before installing: verify you trust the (unknown) author if you plan to convert guidance into automated scripts; avoid adding secrets or platform credentials into any automation derived from these instructions; when implementing platform-specific changes, follow official vendor docs and review any code you or an agent generates for network calls or secret use. If you want the agent to act (not just advise), restrict its permissions and review generated code before deployment.

Edge runtimes move logic closer to users—with strict CPU/time limits, different APIs than full Node, and tenant isolation requirements.

When to Offer This Workflow

Trigger conditions:

• Auth, redirects, or personalization at the CDN layer
• HTML rewriting, A/B assignment, or bot mitigation at the edge
• Global latency SLOs for read-heavy paths

Initial offer:

Use six stages: (1) workload fit, (2) edge vs origin split, (3) data & state, (4) security & tenancy, (5) limits & cost, (6) testing & rollout). Confirm platform (Workers, Lambda@Edge, Fastly Compute, etc.).

---

Stage 1: Workload Fit

Goal: Prefer short, CPU-light, request-scoped work—not long jobs or huge body buffering.

Exit condition: Explicit list of what remains on origin (heavy SSR, large uploads).

---

Stage 2: Edge vs Origin Split

Goal: Document what runs where: geo headers, redirects, cache key logic, A/B bucketing, partial HTML injection.

Practices

• Cache Vary and cookie behavior documented to avoid wrong personalization leakage

---

Stage 3: Data & State

Goal: If using edge KV/Durable Objects/regional stores, state consistency (eventual vs strong) and rate of round-trips to origin.

---

Stage 4: Security & Tenancy

Goal: Validate JWT/session at edge; isolate tenants; never embed secrets in deploy bundles visible to clients.

---

Stage 5: Limits & Cost

Goal: Wall-clock CPU limits, request size caps, egress pricing; graceful degradation or fallback to origin.

---

Stage 6: Testing & Rollout

Goal: Canary per region/PoP; synthetics from multiple locations; compare p95 vs origin-only path.

---

Final Review Checklist

• Workload fits edge constraints
• Edge vs origin responsibilities documented
• State/consistency strategy clear
• Multi-tenant security reviewed
• Limits, cost, fallback documented
• Multi-region validation performed

Tips for Effective Guidance

• Edge runtimes differ from full Node—verify available APIs (fs, streams, crypto).
• Read platform-specific cold-start and isolate model docs.

Handling Deviations

• Hybrid: edge for headers/cache only; heavy compute stays on origin.