Backend Patterns
v0.1.2Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
⭐ 4· 5.4k·28 current·30 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (backend patterns for Node.js/Express/Next.js) matches the content: architecture patterns, code snippets, and best-practice guidance. There are no unexpected requested binaries, env vars, or other resources that conflict with the stated purpose.
Instruction Scope
SKILL.md is a long set of code examples and explanations (repositories, services, caching, transactions, middleware). It references external services and helper functions (e.g., supabase, redis, verifyToken, generateEmbedding, vectorSearch) as implementation examples, but the skill does not instruct the agent to read system files, exfiltrate data, or contact any specific external endpoints. Note: the examples assume that when a developer implements them they will supply service credentials in their app—those credentials are not requested by this skill.
Install Mechanism
There is no install spec and no code files beyond SKILL.md. No downloads or package installations are specified, so the skill does not write code to disk or pull external artifacts at install time.
Credentials
The skill declares no required environment variables, secrets, or config paths. While examples mention services (Supabase, Redis, vector embeddings) that in real use require credentials, the skill itself does not request or require any credentials.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent presence, nor does it modify other skills or system-wide settings.
Assessment
This skill is an instruction-only cookbook of backend patterns and appears internally consistent. Before using any code from it, review and validate code samples in your own environment: supply and protect any required service credentials (Supabase, Redis, etc.), audit generated SQL and RPC functions for injection risks, and ensure authentication helpers (verifyToken) are implemented securely. Because the skill can be invoked by the agent, be aware that any follow-up code-generation or runnable snippets produced by the agent will be suggestions — do not paste secrets into prompts or execute generated SQL/commands without review.Like a lobster shell, security has layers — review code before you run it.
latestvk9717jvarq56ab3eeftk7qytrx80abm3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.