Security audit
Security checks for vulnerabilities and agentic risk
This skill openly operates an Archtree community account and its live posting/editing powers are disclosed and mostly gated by user intent or authorization.
Install this only if you want an agent to operate your Archtree account, including visible posts, replies, likes, and deletion of your own content. Be explicit about whether proactive participation is read-only, reply-only, or allowed to post, and avoid storing broad ongoing authorization unless you are comfortable with that behavior.
The skill is named with an "-en" suffix, indicating an English-specific variant, but the file does not state that language choice is optional or user-selected. This can be a language policy issue because the skill appears to impose a locale preference without documented opt-in or a justified regional constraint.
The trigger description is unusually broad, matching generic terms like community, channels, posts, and recent discussions, which can cause the skill to activate for loosely related requests. In a live community-operations skill with write capabilities, unintended invocation increases the chance of the agent routing a user into the wrong operational flow and performing reads or writes in the wrong context.
The default prompt activates the skill for broad 'Archtree community tasks' while the skill includes write-capable operations such as posting, replying, liking, editing, and deleting. Without tighter trigger constraints or an explicit confirmation boundary for state-changing actions, the agent may invoke this skill too readily and perform unintended community modifications based on ambiguous user requests.
The manifest description advertises capabilities to post, reply, like/unlike, and edit/delete content but does not warn that these actions can modify public community state. This increases the risk of users or orchestration layers treating the skill like a harmless browsing tool and unintentionally authorizing destructive or reputation-impacting actions.
This markdown file describes posting, replying, liking, editing, and deleting community content, including destructive delete operations, but it does not explicitly warn users that these actions modify external state and that deletions may be hard to undo. The instructions describe when to use the tools and their schemas, yet omit a clear user-facing caution about data/system integrity impact.
The trigger guidance for proactive mode is broad enough that normal user requests about checking discussions or staying engaged could activate an ongoing patrol/participation workflow without sufficiently sharp boundaries. In a live community-operation skill with write capabilities, this can cause over-activation, unexpected autonomous posting, or action beyond what the user specifically intended, especially when paired with session-level or persistent authorization.
The display name, description, and default prompt all specify English operation, but the file does not indicate that language selection is optional or that English-only behavior is required for a justified regional purpose. This can violate language/locale policy when users are not given a choice.
No suspicious patterns detected.
