Analyzes meeting transcripts and recordings to surface behavioral patterns, communication anti-patterns, and actionable coaching feedback. Use this skill whenever the user uploads or points to meeting transcripts (.txt, .md, .vtt, .srt, .docx), asks about their communication habits, wants feedback on how they run meetings, requests speaking ratio analysis, mentions filler words or conflict avoidance, or wants to compare their communication across time periods. Also trigger when users mention tools like Granola, Otter, Fireflies, or Zoom transcripts. Even if the user just says "look at my meetings" or "how do I come across in meetings" — use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
alirezarezvani/claude-skills☆ 2.8万2026年8月30日 更新
Captures the user's brand identity once via a 10-question onboarding wizard (primary/accent HEX + heading + body Google Fonts + design style editorial/technical/minimal/playful + default output directory + syntax theme + TOC behavior + optional logo/company), validates body-text and link contrast against WCAG 2.2 AA, derives 12 CSS custom properties in HSL space, and stores the result for every markdown-html converter to consume. Use before any markdown-html conversion. Triggers on first-run onboarding ("set up the brand", "configure markdown-html", "run onboarding"), on explicit reset ("reset the design system", "re-onboard"), and is checked by every converter via config_loader.py before rendering. Refuses to save if body-text contrast fails AA 4.5:1 or the output dir isn't writable. Precedence is project (./.markdown-html/) > global (~/.config/markdown-html/) > built-in defaults; MARKDOWN_HTML_NO_CONFIG=1 bypasses.
日本語の概要は準備中です。原文の説明を表示しています。
alirezarezvani/claude-skills☆ 2.8万2026年8月30日 更新
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry. Covers hypothesis-driven threat hunting, IOC sweep generation, z-score anomaly detection, and MITRE ATT&CK-mapped signal prioritization.
日本語の概要は準備中です。原文の説明を表示しています。
alirezarezvani/claude-skills☆ 2.8万2026年8月30日 更新
Discover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks to analyze a codebase for potential loops, mine coding-thread history for work done more than once, turn repeated engineering work into a loop, find or recommend a published loop, create a recurring agent workflow or automation cadence, turn an outcome into a bounded copy-ready loop, or review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping behavior.
日本語の概要は準備中です。原文の説明を表示しています。
alirezarezvani/claude-skills☆ 2.8万2026年8月30日 更新
Run end-user cmux diagnostics. Use when cmux hooks, notifications, session restore, settings, browser automation, socket access, CLI control, or agent resume behavior is not working, or when the user asks for a cmux health check, doctor report, or support-safe debug summary.
日本語の概要は準備中です。原文の説明を表示しています。
manaflow-ai/cmux☆ 2.8万2026年10月14日 更新
Customize cmux for an end user, including terminal, browser, Markdown, diff, file preview, notes, HTML, and right-sidebar viewers. Use when changing cmux.json actions, custom commands, workspace layouts, plus-button behavior, surface tab bar buttons, Command Palette entries, Dock controls, sidebar and app settings, shortcuts, notifications, browser routing, examples-library presets, or Ghostty-backed terminal preferences.
日本語の概要は準備中です。原文の説明を表示しています。
manaflow-ai/cmux☆ 2.8万2026年10月14日 更新
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
日本語の概要は準備中です。原文の説明を表示しています。
manaflow-ai/cmux☆ 2.8万2026年10月14日 更新
Socket command threading and focus policy for cmux CLI/socket work. Use when adding or changing socket commands, CLI commands, telemetry commands, focus/select/open/close/send-key behavior, or automation that could steal app focus.
日本語の概要は準備中です。原文の説明を表示しています。
manaflow-ai/cmux☆ 2.8万2026年10月14日 更新
View and edit cmux settings in ~/.config/cmux/cmux.json, including terminal, browser, Markdown, diff, notes, HTML, file preview, and sidebar-tool behavior. Use when the user wants to change cmux preferences, set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux recognizes. Triggers on '/cmux-settings', 'change cmux setting', 'customize viewer', 'set <something> in cmux', 'cmux config', 'cmux.json', or 'rebind a cmux shortcut'.
日本語の概要は準備中です。原文の説明を表示しています。
manaflow-ai/cmux☆ 2.8万2026年10月14日 更新
OpenCode Desktop should be RTL-aware. Use when implementing or reviewing RTL/LTR behavior in the web app, desktop app, CSS, menus, scrolling, resizing, icons, mixed-direction text, or Electron title bars.
日本語の概要は準備中です。原文の説明を表示しています。
Kilo-Org/kilocode☆ 2.8万2026年10月14日 更新
Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.
日本語の概要は準備中です。原文の説明を表示しています。
phuryn/pm-skills☆ 2.7万2026年10月10日 更新
Segment users from feedback data based on behavior, JTBD, and needs. Identifies at least 3 distinct user segments. Use when segmenting a user base, analyzing diverse user feedback, or building a segmentation model.
日本語の概要は準備中です。原文の説明を表示しています。
phuryn/pm-skills☆ 2.7万2026年10月10日 更新
Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs. Use when defining your ICP, analyzing PMF survey data, or understanding who your best customers are.
日本語の概要は準備中です。原文の説明を表示しています。
phuryn/pm-skills☆ 2.7万2026年10月10日 更新
Validate skill files for structural compliance and behavioral correctness. Four modes: static linter, spec, category rubric, audit.
日本語の概要は準備中です。原文の説明を表示しています。
Donchitos/Claude-Code-Game-Studios☆ 2.6万2026年10月8日 更新
Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.
日本語の概要は準備中です。原文の説明を表示しています。
EveryInc/compound-engineering-plugin☆ 2.6万2026年10月14日 更新
Add a new feature, put work behind a feature flag, roll something out (per organization, for everyone, cloud or self-hosted), revert or kill a feature, or make a big change to existing behavior such as a new engine. Use BEFORE writing the feature code, and when finishing or removing a rollout.
日本語の概要は準備中です。原文の説明を表示しています。
different-ai/openwork☆ 2.4万2026年10月14日 更新
Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.
日本語の概要は準備中です。原文の説明を表示しています。
every-app/open-seo☆ 2.4万2026年10月14日 更新
Update NemoClaw documentation for merged behavior changes. Use for post-merge catch-up or a requested documentation drift audit.
日本語の概要は準備中です。原文の説明を表示しています。
NVIDIA/NemoClaw☆ 2.3万2026年10月14日 更新
Use when a source code change needs a changelog entry, or before committing and pushing any bug fix, feature, or behavior change to source code - detecting when entries are required, categorizing changes correctly (added/changed/fixed/deprecated/removed/security), writing user-facing titles, and creating the JSON entry in .changelogs/
日本語の概要は準備中です。原文の説明を表示しています。
handsontable/handsontable☆ 2.2万2026年10月15日 更新
Use when writing, fixing, or reviewing tests for any Handsontable change (unit, E2E, or wrapper), and whenever a test is red during feature work. Enforces that tests prove intended behavior – not just execute code, and never "green for the sake of green". Covers intent-first (write the test from the requirement, ideally before the code), deciding whether the code or the test is wrong when red (default: the code), the banned ways of faking green, write-the-failing-test-first, verify-with-a-real-run, no hollow assertions, not mocking the unit under test, and migrating broken legacy tests.
日本語の概要は準備中です。原文の説明を表示しています。
handsontable/handsontable☆ 2.2万2026年10月15日 更新
Use when testing a local or public URL on a real device via BrowserStack, opening a live browser session on Android, iOS, or desktop browsers, or when the user mentions BrowserStack, real device testing, mobile testing, cross-browser testing, touch testing, or wants to verify behavior on a specific phone, tablet, or browser version. Also trigger when the user says "test this on Android/iPhone/Safari/Chrome mobile", asks to open a live session, or mentions demo-mobile.html, even if they don't mention BrowserStack by name.
日本語の概要は準備中です。原文の説明を表示しています。
handsontable/handsontable☆ 2.2万2026年10月15日 更新
Use when creating a demo or test page for manual testing of Handsontable. Trigger when the user asks to create a demo, test page, repro page, reproduction case, manual test, or wants to verify a bug fix or feature visually. Also trigger when the user mentions dev-generated.html, dev-pr.html, dev-latest.html, dev.html, or wants to compare behavior between a released version and a local build. Use this for any PR that needs a manual testing artifact.
日本語の概要は準備中です。原文の説明を表示しています。
handsontable/handsontable☆ 2.2万2026年10月15日 更新
Use when creating a new Handsontable plugin, modifying an existing plugin's behavior, adding hooks or options to a plugin, or working with the plugin lifecycle (enablePlugin, disablePlugin, updatePlugin). Covers the full plugin contract, conflict registration, settings validation, and IndexMapper integration.
日本語の概要は準備中です。原文の説明を表示しています。
handsontable/handsontable☆ 2.2万2026年10月15日 更新
Turn a recorded software failure into a reproducible bug report with timestamps and observed behavior.
日本語の概要は準備中です。原文の説明を表示しています。
screenpipe/screenpipe☆ 2.2万2026年10月14日 更新