meeting-notetaker

Fetch and present meeting notes from monday.com Notetaker, or show the next upcoming meeting with full context prep. Use when: asked to summarize a meeting,...

This skill's instructions explicitly tell the agent to 'source' a local .context file and to read Google Calendar credentials from a hardcoded path, but the skill metadata declares no required secrets or config paths. Sourcing a file can run arbitrary shell code and will expose any variables or secrets inside it. Before installing or enabling this skill: 1) ask the publisher to update the manifest to declare required config paths and credentials (and explain why each is needed), 2) inspect the actual .context and credentials files the skill will read to ensure they contain only expected configuration (not executable code or unrelated secrets), 3) confirm that the MCP tools referenced (get_notetaker_meetings, monday-api-mcp__create_item) exist and are trusted, and 4) if you cannot verify these, avoid enabling the skill or run it in an isolated/test account. The mismatch between declared requirements and runtime behavior is the main concern.

Type: OpenClaw Skill Name: meeting-notetaker Version: 1.0.0 The skill is classified as suspicious because it explicitly instructs the AI agent to bypass standard tool abstractions and directly read sensitive credential files located at `/opt/ocana/openclaw/.gog/credentials.json` and a local `.context` file in `SKILL.md`. While these actions are framed as necessary workarounds for fetching calendar data and meeting notes, direct file-system access to credentials and environment variables represents a high-risk pattern that could be exploited. No evidence of intentional data exfiltration to unauthorized endpoints was found, but the instructions grant the agent excessive privilege over system-level secrets.