Meeting Assistant

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This instruction-only meeting notes skill is coherent and purpose-aligned, but it creates persistent meeting records and offers optional recurring and cross-skill workflows that users should enable deliberately.

This looks safe to use as a local meeting-management workflow. Before installing, review the AGENTS.md and optional HEARTBEAT instructions, choose where meeting records should live, and only enable cross-skill integrations or recurring scans if you want that persistent behavior.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Meeting notes, decisions, attendees, and action items may persist locally and influence future briefs or reviews.

Why it was flagged

The skill intentionally stores meeting history for future retrieval and use.

Skill content
Files meeting records so past decisions are searchable and linkable
Recommendation

Keep the meetings folder in an appropriate location, review generated notes and action items for accuracy, and avoid storing sensitive transcripts or private details unless you are comfortable retaining them.

What this means

If the heartbeat pattern is adopted, the agent may perform recurring reviews of local meeting files rather than acting only on one-off prompts.

Why it was flagged

The advanced heartbeat pattern describes recurring local checks of meeting action items.

Skill content
Every Monday morning, scan meetings/open-actions.md
Recommendation

Only add heartbeat instructions if you want recurring checks, and keep them limited to local review and draft/report generation.

What this means

Meeting, client, project, or business context may be combined across skills if those optional chains are enabled.

Why it was flagged

The advanced patterns describe optional workflows that pass context between this skill and other assistant skills.

Skill content
Chain research-assistant → meeting-assistant
Recommendation

Use cross-skill workflows only with trusted skills, verify imported research before relying on it, and avoid passing sensitive information into integrations that do not need it.