Security audit
Security checks for vulnerabilities and agentic risk
This meeting assistant is not malicious, but it needs review because it can join live meetings and capture audio/chat without clear consent or confirmation safeguards.
Review before installing. Use this only where you are allowed to bring a bot into the meeting, notify participants, and send meeting audio/chat/transcripts to the configured gateway and AI providers. Prefer explicit prompts such as join/transcribe this specific meeting URL, and avoid relying on broad automatic triggers.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Get your Habilis MCP Token:
Set Environment Variables:
The skill description explains functionality but does not clearly warn users that the agent may join a live meeting, capture participant audio and chat, transcribe speech, and generate minutes. In a meeting-assistant context this omission is especially risky because users may invoke the skill without understanding the privacy, consent, and legal implications for all participants.
The README advertises transcription, diarization, voice interaction, and chat capture, but it does not clearly and prominently warn that live meeting audio, transcript data, and chat content are transmitted to external services such as the MCP gateway and third-party AI/voice providers. In a meeting-assistant context, this omission is security-relevant because users may unknowingly expose sensitive business or personal communications to external processors, creating consent, privacy, and compliance risks.
The triggers jitsi and google meet are overly broad and likely to match ordinary user mentions of those platforms rather than an explicit request to summon a meeting bot. In this skill’s context, accidental activation is more dangerous because the advertised behavior includes joining live meetings, capturing audio/chat, and producing transcripts, which could cause unintentional participation and privacy violations.
This manifest describes a meeting bot with extensive capabilities, but it does not specify when the skill should or should not be invoked, nor does it list concrete trigger phrases or scope limits. In a manifest file, that lack of specificity can create ambiguous activation conditions and unintended invocation overlap with other meeting-related requests.
The natural-language description emphasizes real-time transcription, speaker diarization, duplex voice, and meeting-minute generation, but it does not mention whether language or locale is user-selectable. For speech and transcription skills, silently defaulting to a language or locale can create policy issues if the user is not given an opt-in choice.
No suspicious patterns detected.