Ssr Ssg

v1.0.0

Deep workflow for SSR, SSG, ISR, and hybrid rendering—choosing modes per route, data freshness, caching, streaming, hydration, SEO, and operational trade-off...

0· 66·0 current·0 all-time
byClawKK@codekungfu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (SSR/SSG/hybrid rendering guidance) match the SKILL.md content. The guidance is about route classification, rendering choices, caching, streaming, hydration, SEO and ops—everything requested is appropriate for a deep workflow document.
Instruction Scope
SKILL.md contains purely architectural and operational guidance for developers; it does not instruct the agent to read local files, access environment variables, call external endpoints, or run commands. It asks the agent to confirm framework/hosting with the user, which is within scope.
Install Mechanism
No install spec and no code files. Instruction-only skills have the lowest install risk; nothing is downloaded or written to disk.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no surprising credential requests and no unjustified access to secrets.
Persistence & Privilege
Flags are default (always: false, user-invocable: true). The skill does not request permanent presence or system-level modifications.
Assessment
This skill is a pure, framework-agnostic workflow for choosing rendering strategies and appears coherent and low-risk: it doesn't install software or ask for credentials. Before using, confirm the target framework and hosting (Next.js App vs Pages, edge vs serverless) so the agent's advice can be concrete. If you have strict policies about autonomous agent actions, remember the skill can be invoked by the agent (platform default) — but by itself it does not request elevated privileges or secrets. If you want extra caution, run the skill only interactively (user-invoked) and avoid granting any unrelated credentials to the agent environment.

Like a lobster shell, security has layers — review code before you run it.

latestvk97801qejxrhfxf3wx8gbjzccn83gd0w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments