Security audit
Security checks for vulnerabilities and agentic risk
This skill provides ordinary workflow guidance, but its financial-review name does not match its weather-oriented description and broad activation keywords.
Expect a generic workflow template rather than a specialized financial forecast reviewer. Prefer explicit invocation because its broad keywords may match unrelated requests. Review any generated analysis or code changes before relying on them.
The usage section lists generic keywords such as current, api, key, required, and users, which occur in many unrelated requests. The accompanying trigger examples describe Weather-style workflows and general bug fixing rather than financial-model review, leaving the intended activation scope unclear.
The trigger list includes generic words such as current, key, required, and users, which occur in many unrelated requests. The description on line 4 also permits activation for generic workflow or analysis requests, without exclusions or a requirement that they concern financial forecast review or Weather-style skills.
The trigger list includes broad terms such as current, key, required, and users, which routinely appear in unrelated requests. No exclusion conditions or requirement for a domain-specific combination limits these triggers, creating a clear risk of unintended invocation.
The description and default prompt contain fragmented text about Weather-style workflows, fixing bugs, and hardening, rather than defining when a financial-model forecast reviewer should activate. With implicit invocation enabled, this mismatch leaves the intended invocation conditions ambiguous.
L77 lists everyday terms such as "current", "key", "required", and "users" as usage signals, which could match unrelated requests. Although the example trigger sentences mention Weather-style workflows, the file does not require that context when matching these keywords or provide exclusions for unrelated requests.
The usage keywords include generic terms such as current, key, required, and users, which could match unrelated requests. The trigger sentences do not clarify whether those keywords require a financial-model forecasting context, and no exclusions limit unintended activation.
