Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Video Conferencing

ASecurity

Run excellent video conferences — platform-agnostic best practices for facilitation, engagement, and hybrid setups.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreactsecurity

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill video-conferencing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Video Conferencing?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Video Conferencing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-video-conferencing/badge)](https://www.skillsdirectory.com/skills/aicodedecode-video-conferencing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: video-conferencing
description: Run excellent video conferences — platform-agnostic best practices for facilitation, engagement, and hybrid setups.
category: enterprise-communication
---

## Overview

Video conferencing is the default meeting medium for distributed work — this skill covers platform-agnostic excellence: setup, facilitation, engagement techniques, hybrid configurations, and troubleshooting. It complements tool-specific skills (zoom-pro, teams-pro) with universal principles that apply everywhere.


Video conferencing infrastructure — platforms, hardware, and practices — underpins remote and hybrid work.
Beyond choosing Zoom vs. Teams vs. Meet, mastery covers room systems, production quality, accessibility, and the meeting culture that makes video effective.
## When to use

- Improving video meeting quality generally
- Facilitating engaging virtual meetings
- Setting up hybrid meeting rooms
- Training teams on video best practices
- Troubleshooting common video issues
- Designing virtual event experiences

- Equipping conference rooms for hybrid meetings
- Standardizing platforms across organizations
- Improving video meeting quality and engagement
- Planning large virtual events
- Planning town halls and all-hands
## Core concepts

**Technical foundation.** Stable internet (wired beats wifi for hosts), good audio (headset mic — the highest-ROI upgrade), decent camera (eye-level, face lit from the front), and tested setup before important meetings. 90% of "bad video meetings" are bad audio.

**Facilitation.** More active than in-person: call on people by name, use round-robins, monitor chat visibly, time-box segments, and build in interaction every 10 minutes (polls, breakout discussions, chat prompts). Silence on video means disengagement, not agreement.

**Engagement techniques.** Cameras-on norms (discussed, not mandated blindly), chat as a parallel channel (questions, reactions, links), reactions/emoji for quick pulses, breakout rooms for real discussion in large groups, and collaborative docs for shared note-taking.

**Meeting types.** Status (keep short, consider async alternative), decision (pre-reads essential, structured discussion), brainstorming (breakouts + silent writing before sharing), 1:1s (cameras on, no multitasking — it's a relationship meeting), all-hands (broadcast + Q&A, rehearsed).

**Hybrid setups.** The hard problem: room audio that remote participants can hear (ceiling mics or individual mics, not laptop speakers), cameras showing the room (not just the back of heads), remote-first norms (everyone on their own device for chat/reactions), and a dedicated advocate for remote voices.

**Accessibility.** Captions on (accuracy varies — speak clearly), shared materials in advance, verbal descriptions of visuals ("the chart shows..."), and recordings with transcripts for those who couldn't attend.


**Platform selection.** Evaluate: reliability, scale limits, breakout capabilities, recording/transcription, integrations, security certifications, and cost at your scale.
Standardize on one primary platform — multi-platform chaos confuses everyone.
Exception paths for client-mandated alternatives.
**Room hardware.** Cameras (framing for equity — remote participants should see everyone), microphones (ceiling arrays beat table pucks for large rooms), displays, and one-touch join.
Bad room audio is the #1 hybrid meeting complaint — invest in microphones first.
Test from the remote participant's perspective regularly.
**Meeting equity.** Remote participants get: clear audio, visible faces, chat monitoring (dedicated), and equal speaking opportunities.
Hybrid meetings default to favoring in-room participants — counter deliberately.
Consider "one laptop per person" even in rooms for full equity.
## Practical workflow

1. **Set standards.** Team norms: cameras, mute discipline, chat use, backgrounds, and "video-ready" workspace basics. Publish a one-page guide.
2. **Prepare each meeting.** Agenda in invite, pre-reads attached, tech tested (for hosts), materials ready to share, and backup plan (phone dial-in if video fails).
3. **Facilitate actively.** Open with purpose and norms, engage by name, watch for disengagement (cameras off + silent = check in), use breakouts for groups over 8, and park tangents.
4. **Manage hybrid.** Test room setup before important hybrids, assign a remote advocate, ensure room audio/video works for remote, and default to remote-first behaviors.
5. **Close and follow up.** Decisions, owners, deadlines — stated aloud and written. Share recording/notes within 24h.
6. **Improve.** Gather feedback on recurring meetings, track engagement signals, upgrade room tech where hybrids suffer, and kill meetings that don't earn their video time.

**Engagement check-ins:** "Drop a 1–5 in chat: how are we doing on time?" "Quick poll: which option?" "Two minutes silent writing, then share." "Breakouts of 3 for 10 minutes, then report back."


**Room setup standard:** one-touch join → auto-framing camera → ceiling mics → dual displays (people + content) → occupancy sensors → support contact posted.
Standardize across rooms — users should not relearn every space.
**Pre-meeting checklist:** agenda shared → tech tested → materials pre-loaded → remote participants confirmed → recording/transcription enabled → chat monitor assigned.
Five minutes of prep prevents fifty minutes of dysfunction.
## Common pitfalls

- **Audio neglect.** Investing in cameras while audio is terrible. Fix audio first — always.
- **Passive facilitation.** Hoping discussion happens. Video needs active facilitation or it dies.
- **Hybrid afterthought.** Room-centric meetings where remote participants watch a bad stream. Design hybrid deliberately.
- **No interaction.** 60-minute monologue on video. Interact every 10 minutes or lose the room.
- **Camera mandates without context.** Requiring cameras while ignoring fatigue and equity. Discuss norms; allow flexibility with reason.
- **Skipping pre-reads.** Using meeting time for information transfer. Read before, discuss during.
- **Tech untested.** Discovering the room mic doesn't work with 20 people waiting. Test before important meetings.
- **Hardware afterthought.** Great platform, terrible mics. Audio quality determines meeting quality more than video — budget accordingly.
- **No remote advocate.** In-room side conversations excluding remote attendees. Assign chat monitors; pause for remote input explicitly.
- **Back-to-back scheduling.** No transition time between video calls. Buffer time is not waste — it is recovery and preparation.
- **Unmuted chaos.** Large meetings without mute discipline. Default mute-on-entry for 10+ participants — always.
- **No recordings policy.** Unclear what gets recorded and retained. Define policies upfront — privacy and storage both matter.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →