Search: "secrets"

Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.

Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.

This skill should be used when the user asks to "open source this project", "prepare this repository for public release", "make this repo public", "check open-source readiness", "choose a license for this project", or "set up release automation" ahead of a public launch. Provides a release-readiness workflow covering secrets hygiene, licensing, documentation, CI, and language-specific packaging.

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

Security guard for AI agents — blocks malicious skills, prevents data leaks, protects secrets. 24 detection rules, runtime action evaluation, trust registry.

Local-first identity, memory, and secrets for AI agents. Portable state across models and harnesses.

Work with the user's AgentPlaybooks playbooks through the connected AgentPlaybooks MCP server — list and open playbooks, adopt a playbook's persona and instructions, read and write its memory, use its skills, keep work documents on its canvas, call its connected tools, and use vault secrets without seeing their values. Use when the user mentions a playbook, asks Claude to remember something across sessions or tools, wants a shared team memory, or wants to call an API with a stored credential.

Check a pull request is small, described, tested, and free of secrets before opening or reviewing it. Use when drafting a PR, reviewing a diff, or verifying a change is ready to share.

Please change your api keys to env variable or secrets manager or another place