speak-security-basics
Security best practices for Speak API keys, audio data privacy, student data protection, and COPPA/FERPA compliance. Use when implementing security basics features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak security basics", "speak security basics". '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-security-basics --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Speak Security Basics ## Overview Security best practices for Speak API keys, audio data privacy, student data protection, and COPPA/FERPA compliance. ## Prerequisites - Completed `speak-install-auth` setup - Valid API credentials configured - ffmpeg installed for audio processing ## Instructions ### API Key Security ```bash # Never commit API keys echo '.env' >> .gitignore echo '.env.local' >>
What does the speak-security-basics skill do?
Security best practices for Speak API keys, audio data privacy, student data protection, and COPPA/FERPA compliance. Use when implementing security basics features, or troubleshooting Speak language learning integration issues. Trigger with phrases like "speak security basics", "speak security basics". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill speak-security-basics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.