Agent Skills: meeting-coach-worker
Coach workers, employees, and individual contributors to turn meetings, transcripts, minutes, and work notes into better execution: infer leader expectations, diagnose previous work, identify next actions, judge delivery readiness, and prepare a high-bandwidth update. Use after meetings, during work, before reviews, or across repeated low-value discussions. Perform semantic review from source evidence.
ID: shareai-lab/shareai-skills/meeting-coach-worker
31454
Install this agent skill to your local
Skill Files
The files that make up meeting-coach-worker.
More agent skills
- openclaw-release-validationGuide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.
- review-docsReview and improve tldraw SDK documentation against the voice and docs guides, scoring each article and iterating until it passes. Use when asked to review docs, audit an article in apps/docs/content, check whether documentation follows the style guide, or improve existing documentation.
- dyad:debug-minified-errorMap a minified error stack trace from a production Dyad build back to original source locations using source maps.
- mergeWait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR. Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge.
- rag-hybrid-searchHybrid search combining semantic and keyword retrieval for RAG pipelines. Implement BM25 + dense vector search with fusion strategies.
- amy-expertPatterns for extending `amy`, the Amethyst CLI in `cli/`. Use when adding an `amy <verb>` command, touching files under `cli/src/main/kotlin/…/cli/`, wiring a new subcommand into `Main.kt`, writing an interop test script that drives Amy, or extracting logic out of `amethyst/` into `commons/` so a CLI command can call it. Enforces the thin-assembly-layer rule (no Nostr protocol or business logic inside `cli/`), the dual-output contract (text by default, single-line JSON object on stdout under `--json`, exit codes 0/1/2/124), and the extract-from-Android recipe. Complements `nostr-expert` (protocol in Quartz), `kotlin-multiplatform` (expect/actual for extraction), and `feed-patterns` / `account-state` / `relay-client` (where the business logic should end up). NOT for general Nostr or Kotlin work — those have their own skills.