SEO Optimizer Pro

This skill's behavior (local analysis + sending content to your chosen AI provider) matches its stated purpose, but there are metadata inconsistencies you should resolve before installing. Actionable steps: - Do not provide multiple provider API keys by default. Only set the environment variable for the single provider/model you will use. - Verify which env var the model you plan to call requires (e.g., ANTHROPIC_API_KEY for claude-*, OPENAI_API_KEY for gpt-*). The code will error if the required env var is missing. - The registry-level metadata in this package incorrectly states 'no required env vars' despite the manifest and code requiring a provider key; consider this a sign of sloppy packaging. If you rely on registry metadata, confirm with the manifest/README or the source repository. - Review the included source (seo_optimizer.py) yourself or have an engineer inspect it to confirm no hidden network calls or unexpected file access beyond the documented provider SDKs. - Test with non-sensitive sample content and a throwaway API key (or minimal-privilege account) before analyzing private data. Check the chosen provider's data-retention and privacy policies because your content will leave your machine to that provider. - Confirm the project/source repository (manifest references GitHub) and contact the author if you need clarification about the metadata mismatch or distribution/restrictions in LICENSE.md. If these checks pass and you only set the single provider key required for your chosen model, the skill appears coherent with its purpose. If the author cannot explain the metadata mismatch or the package requests multiple unrelated secrets at runtime, avoid installation.