SkillsAdd

smithery/sanmak

security-env

Use when adding config, credentials, external services, or environment variables.

Installation

$ npx skills add smithery/sanmak --skill security-env
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

firebase-security-rules-auditor Similar name
firebase/agent-skills

>- Audits Firebase (Firestore, Cloud Storage) security rules for vulnerabilities, privilege esc…

111K installs
better-auth-security-best-practices Similar name
better-auth/skills

Configure rate limiting, manage auth secrets, set up CSRF protection, define trusted origins, s…

30.3K installs
firestore-security-rules-auditor Similar name
firebase/agent-skills 20.4K installs
security-review Similar name
getsentry/skills

Security code review for vulnerabilities.

15.5K installs
security-best-practices Similar name
openai/skills

Perform language and framework specific security best-practice reviews and suggest improvements…

8.2K installs
security-threat-model Similar name
openai/skills

Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabili…

5.4K installs

Also in this package

Other skills from smithery/sanmak.

npx skills add smithery/sanmak
nextjs-app-ui 0

Browse all from smithery/sanmak

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 610 B
  • docs SUMMARY.md 101 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Goal

Keep secrets out of the repo and document required configuration safely.

Do

  • Store secrets in .env only; never commit real keys.
  • Update .env.example with new variable names and defaults.
  • Prefer server-only env usage for secrets (API routes, server components).
  • Sanitize logs to avoid leaking tokens.

Don't

  • Commit secrets or embed keys in client code.

Examples

  • "Add a new API key and update .env.example."
  • "Move client-only env usage to a server route."