Productivity

Turn a meeting transcript into short notes with decisions, actions and open questions.

Make a first-week checklist for a new teammate.

Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.

Agent skills: WCAG audit, house plans, floor plan CAD, cloud computer tasks

The one skill for "will this succeed, and why not?", for ideas AND live products. Mode IDEA (before deck, plan or code; hackathon, startup, feature, research topic) and Mode PRODUCT (an existing site/app). Use when the user says "idea check", "is this worth building", "research my idea", "roast", "roast my landing page", "why no signups", or pastes a problem statement, names an idea, or gives a product URL. Runs like experienced founders, PMs, investors and judges: kill-questions, a skeptic round, real-behaviour evidence, incumbent teardown, economics, a 41-check failure-mode sweep, pre-mortem, then a verdict (DEAD/UNKNOWN/ALIVE) or a graded product roast with an ordered fix list. Every source opened, every claim labelled.

Writes BRIEF.md before a website is designed, in one of two modes the user picks. Site mode gathers what the page needs (offer, audience, proof, sections, style inputs) and hands off to /style-guide without business advice. Diagnose mode starts from the user's real situation (nothing yet, a niche, a freelance account or service with few clients, a live site), researches demand and competitors, stress-tests the idea with independent reviewers, and may conclude that a site is not the next step. Use when the user invokes /brief, wants to start a website or landing page, asks what site or business to build, wants a site that makes money but has no idea, wants a niche or idea validated, asks whether an idea is worth it, or asks why they get no clients. Not for generating tokens or building pages.

Diagnoses a project that is in trouble and builds an honest recovery plan - separates symptoms from root causes using the project's own documents, sizes the gap in time, cost and scope, lays out the real options (recover, reduce scope, add time or money, pause and re-plan, stop), and writes a one-page brief for the sponsor, in English or Arabic. Use this whenever someone says their project is late, over budget, stuck, failing, "red", out of control, or losing the client's or sponsor's confidence; has inherited a troubled project; needs to tell leadership bad news about a project; or asks how to get a project back on track, even if they do not use the word "recovery". Not for planning a healthy project from scratch, routine status reporting, or resolving personal conflicts between individuals.

Turn a meeting recording (m4a, mp3, wav, mp4, ...) into minutes on the user's own computer. Whisper transcribes, pyannote separates speakers, and the agent writes minutes from the speaker-labelled transcript. Use when the user gives a recording and asks for minutes, a summary, a transcript, speech-to-text, or "who said what". 회의 녹음으로 회의록, 전사본, 화자 분리, STT 를 요청할 때 사용한다. The audio never leaves the computer.

Mask personal data (GDPR) and confidential information (corporate trade secrets, procurement tenders, FOIA exemptions, and statutory secrecy such as Swedish OSL) in PDF, Word, PowerPoint or image files using specialized non-generative encoder AI in the EU (98.30% precision, 93.17% recall, 95.67% F1; interactive web review GUI; strict zero retention) via https://redact.aigine.se/mcp. Use when a document that may contain information about identifiable people, trade secrets, or public/statutory secrecy is about to be sent to an external AI model or service, shared, or released, or when the user asks to redact, anonymize, pseudonymize or mask a document.

在动手实现之前，通过可交互的 HTML 页面与用户对齐一个软件想法或难题的框架：模型用自己的话复述理解、提供灵感、指出空缺与矛盾、定位难点，用户用点选和备注回应，直到用户认为框架成立。仅在用户明确调用（例如 /frame-align）时使用，不要自行触发。

This skill should be used when the user asks to "challenge this plan", "red-team this", "what could go wrong", "pre-mortem this", "adversarial review", "poke holes", "stress-test this design", "find the flaws", or "review this before I build it". It looks for the reasons a plan, design, diff, decision or another skill's output will fail, ranks the concerns against a fixed severity bar, and ends with one verdict (PROCEED, AMEND or RETHINK). Runs interactively by default, or in report mode with no questions when called by a worker agent or when the caller asks for "report mode".

Use this skill whenever the user responds to an answer Claude already gave (or to several answers, or to pasted text) by asking for less of it rather than more: the bottom line, the gist, the conclusion, tl;dr, the key points, a shorter version, a simpler explanation, or a visual of it. Also use it when they say the answer is too long or confusing. Requests in any language count (\"покажи кратко\", \"长话短说\", \"要点だけ\", \"一言で\"). Also use it for a recap of everything done or decided so far in the session. The skill re-tells the same content: the answer in plain words first, then a chart, tiles or table of its data, then short bullets. It keeps every number, name, command and warning, invents nothing and cuts wording, not facts: text ends up about half to two-thirds as long; tables keep their size. Commands: /glance, /btw /glance, /glance [what|on|super|off|status|help]. Don't use it for new deliverables such as documents, dashboards, slides, emails, exports or translations, or for new questions about the topic.

Diagnose and troubleshoot Windows 10/11 and Windows Server problems with Microsoft's TroubleShootingScript toolset (TSS) - map a symptom to the right TSS scenario and exact .\TSS.ps1 command, run a read-only health triage of the local machine (event logs, crashes, BSODs, disks, services, updates, network, domain), and analyze an already-collected TSS / MS_DATA zip into plain-English findings. Use this whenever the user describes a Windows problem (slow PC, crashes, blue screen, account lockouts, logon or GPO problems, DNS/Wi-Fi/VPN/SMB/proxy connectivity, printing, RDP/AVD/Windows 365, Windows Update or activation failures, Start menu/Store/app issues, WMI/WinRM, Hyper-V, clustering), asks "which TSS scenario", "what does TSS collect", "how do I trace X", mentions TSS, MS_DATA, xray or SDP, asks whether TSS is expired or wants it updated, or hands over a support-data zip or .evtx files to read - even if they don't name TSS.

Reach any goal a command can score (fix every failing test, finish an audit, make something faster or smaller, port a tool, polish a UI or a text) by climbing in small verified steps. Each change is scored by a locked check, committed if it wins and undone if it doesn't, across one or many repos. Use when the user says "belay", "hill climb", "climb this", or "keep going until it passes", wants a long unattended run toward a measurable target, or asks to resume or report on a climb.

Convert software feature requests, integrations, and change proposals into scoped implementation approaches, small development tasks, and measurable acceptance criteria. Use when a user asks for a technical plan, backlog, or implementation breakdown. Planning does not authorize coding, deploying, or creating CRM records.

Digest all meetings from a given day — uses the calendar as source of truth and the configured meeting-notes sources as content. Extracts decisions, action items, and blockers, writes structured notes to Context/Meeting Notes/.

Triage customer support requests, identify missing evidence, suggest safe next actions, and draft CRM tasks and customer replies. Use when assessing support messages, preparing responses, or turning requests into actionable internal tasks. Never imply that a message was sent or a ticket was created unless it actually happened.

B2B 大客户销售与售前教练，面向企业软件/数字化办公/OA/ERP/SaaS 销售场景（如泛微 e-cology、低代码、AI 智能体、电子签章等）。 两种触发场景：(1) 用户粘贴与客户的微信聊天、邮件、会议纪要、拜访记录或电话录音稿，需要判断客户意向与采购阶段、 解读对方真实态度、指出用户沟通失误、并给出可直接复制发送的回复；(2) 用户询问销售全流程问题——找线索、破冰、约见、 需求挖掘、方案演示、报价与压价、招投标、陪标判断、竞品应对、催单、续约、客户看板管理等，贯穿"线索—触达—需求—方案— 商务—签约—续约"全过程。中文为主。 B2B enterprise sales coach: analyze customer conversations, diagnose buying stage and decision chain, flag mistakes, draft copy-paste replies, and answer questions across the whole sales lifecycle.

制定、展开和调整最多12周的训练计划与课表，整合功能性力量、跑步和游泳。用于健身计划、混合训练或hybrid training、月周安排、单次训练、外部计划适配及中断后重入；不用于备赛或临床诊疗。

Populate a shared whiteboard (Wallflower, built on tldraw) with what's worth discussing before a meeting or a private review, take further passes when people ask for more, then read back what people did to it and separate their judgment from yours. Use from a prep thread, cold or already holding context, when the user asks to "put this on the board", "prep the board", "populate the board", "take another pass", or "what did the room do with the board".

Create a printable invoice, quote or receipt from one small input, log expenses to a plain ledger, list overdue invoices with the next payment reminder drafted in plain English or simple Bengali, and see a simple cash-flow view — for non-technical small businesses. Use when a small business owner needs an invoice from a messy message, wants to know who owes them money and what to write next, or wants this month's money in, money out and money owed on one screen.

Facilitates a time-boxed risk discovery interview or workshop for one person or a group treated as a single voice, up to 60 minutes (default 30), to draw out the top 3 to 5 risks of a company, project or scenario, rank them by perceived criticality and, when time allows, rate likelihood and impact on 1 to 5 scales. Produces an erm format risk register and a markdown session summary that can be consolidated across sessions. Sessions can be paused and resumed from the saved files. Works with two companion skills, erm (https://github.com/wai-kwan/enterprise-risk-management) which completes and rates the register, including a hand-off mid session, and kri…

Kairos — build job-tailored, fabrication-safe resumes from your real experience. Use when the user wants to set up their career knowledge base, score a job they're interested in, tailor a resume/cover letter for a specific role, or review their application history. Drives the Kairos MCP tools.

软件开发团队（主理人齐活林）：按 SOP 编排产品经理、架构师、UI/UX 设计师、工程师、代码审查者、QA 六个子智能体协作交付软件。按需组队（单专家/小队/加强小队/完整队/审查队），项目简报替代全文转交，标准文件按需加载；标准流程为需求→PRD→架构与任务分解→UI 规范→按切片实现→交付前审查→测试验证，带质量门禁；小需求走快速模式，Bug 走 BugFix 快捷路径（复杂/模糊 Bug 先做条件诊断），既有 PR/分支/变更的规范整改走整改档，另支持只读的上线前审查。当用户提出开发应用/网站/工具/新功能、修复 Bug、按规范修整或返修既有 PR/变更、代码审查、上线前检查，或点名“软件开发团队”“标准流程”时使用；也可通过 /dev-team 显式调用。