Security audit
Security checks for vulnerabilities and agentic risk
This is a Markdown-only coaching skill for software team conflict analysis, with no evidence of hidden execution, data access, persistence, or credential handling.
Reasonable to install if you want structured advice for recurring software or game team conflict. Treat its archetype labels as rough framing, not facts about a person, and be careful with workplace escalation or HR-sensitive situations.
This markdown instruction says to translate guidance into "safer team-language," and the entire reference is written as an English-only operating document, but it provides no user choice or opt-in for language/locale. Under the policy, forcing a specific language without user opt-in is a natural-language policy issue.
The manifest description says to use the skill when someone describes a teammate, lead, stakeholder, client, or collaborator creating friction or slowing decisions, which is a wide and natural class of everyday requests. It does not give explicit trigger phrases, exclusions, or narrow context boundaries, so the activation scope is somewhat ambiguous for when this skill should be invoked versus more general advice or coaching skills.
No suspicious patterns detected.
