Faas
v1.0.0Deep workflow for serverless workloads—event sources, IAM, cold start/latency, limits, observability, security, cost, and deployment patterns (functions, con...
⭐ 0· 58·0 current·0 all-time
by@clawkk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (serverless deep workflow) match the SKILL.md content. The guidance covers event sources, IAM, networking, observability, costs, and deployment patterns — all expected for a serverless design/debugging workflow. There are no unrelated resource requests (no cloud creds, binaries, or install steps).
Instruction Scope
SKILL.md is a focused six-stage workflow and checklist. It does not instruct the agent to read local files, environment variables, system configuration, or to transmit data to external endpoints. Mentions of IAM/KMS/roles are contextually appropriate guidance rather than requests for secrets.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes risk from on-disk code or external downloads.
Credentials
The skill declares no required environment variables, credentials, or config paths. Discussion of permissions and KMS is advisory; nothing in the skill asks for unrelated secrets or broad access.
Persistence & Privilege
always is false and there is no install behavior that would persist or modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other risky attributes.
Assessment
This skill is a text-only workflow for designing and debugging serverless systems and appears internally consistent. It does not ask for credentials or install code itself. Before you act on its recommendations, be cautious when: (1) granting real cloud credentials or IAM permissions—prefer least-privilege short-lived tokens and review policies before applying them; (2) running any CLI/automation commands the workflow suggests—review commands for scope and destination; and (3) sharing logs or config that may contain secrets or PII. If you later use follow-up code or tooling based on these recommendations, re-evaluate that code's install and env requirements separately.Like a lobster shell, security has layers — review code before you run it.
latestvk97dy430kbmvdsya9dzhcjv36x83pwda
License
MIT-0
Free to use, modify, and redistribute. No attribution required.