181 skills · sorted by relevance
Organize meeting notes into a clear layout with attendees, an agenda checklist, decisions, and next meeting details. An action items table highlights who owns each task, when it is due, and its current status.
Create a printable, single-page A4 invoice with sender and billing details, itemized charges, tax breakdowns, totals, and payment instructions. The layout includes invoice dates and deadlines, with print styling that preserves color contrast.
Turn a major product initiative into a testable hypothesis with a clear target user and expected outcome. Define small experiments, measurable success criteria, and an evaluation timeframe before committing to full development.
Make specific C# behavior testable by adding a minimal way to replace time, randomness, or other external dependencies. Preserve public APIs and production behavior, then run repeatable tests without real file access or waiting.
Create and edit Obsidian Bases files to organize notes into tables, cards, and lists. Filter notes by tags or properties, calculate values such as days until a deadline, and configure grouping and summaries.
Draft daily or weekly schedules from tasks, deadlines, availability, and stated energy patterns. Include fixed commitments, breaks, and buffers, flag work that will not fit, and review supplied activity logs to suggest practical adjustments.
Idiomatic context.Context usage in Golang — propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel for background work outliving requests. Apply when designing context propagation across layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or storing values in context. Not for code that merely accepts ctx as first parameter.
The English summary is being prepared. Showing the original description.
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action for each (draft reply, calendar hold, scaffold a project, snooze). Use when user says "triage my inbox", "check my academic email", "what needs my attention this week", "go through my mail", or when run as a scheduled routine. NEVER auto-sends or auto-accepts anything.
The English summary is being prepared. Showing the original description.
Never get auto-renewed into another year again — the contract inventory with the dates that matter (notice deadlines, not renewal dates), the calendar system with decision-time buffers, and the renewal-decision ritual that renegotiates instead of rubber-stamping. Use when asked track our contracts and renewals, we got auto-renewed again, when do we have to decide on this vendor, or set up renewal management. Produces the inventory with notice-deadline math, the alert system, the renewal-decision checklist, and the negotiation-window playbook.
The English summary is being prepared. Showing the original description.
Prepare for China's annual individual income tax reconciliation (个税年度汇算): check income, deductions and special additional deductions, compare the two treatments of a year-end bonus, and estimate the refund or amount to pay before filing in the 个人所得税 app. Use when asked 个税汇算怎么弄, 年终奖单独计税还是合并, 我能退多少税, 专项附加扣除, or how does China's annual tax reconciliation work. Produces a filing checklist, the deductions the person may be missing, a bonus comparison, the estimate with workings, and deadlines. Not tax advice.
The English summary is being prepared. Showing the original description.
Turn a list of goals, tasks, deadlines, and working constraints into a practical schedule with next actions and follow-ups.
The English summary is being prepared. Showing the original description.
Use when auditing an AISTATS submission for OpenReview readiness, abstract/full-paper deadlines, the 8-page submission body, double-blind anonymity, supplementary material, reproducibility checklist, dual-submission policy, reviewer volunteer requirements, desk-reject triggers, and final-week submission sequencing.
The English summary is being prepared. Showing the original description.
Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
The English summary is being prepared. Showing the original description.
Use when running the final pre-submission preflight for an Academy of Management Annals (Annals) proposal or invited full review via the Manuscript Central portal — proposal-vs-invited-review route, deadlines, formatting, CV, and anonymity. Final checks; it does not draft content.
The English summary is being prepared. Showing the original description.
Use when writing the short proposal that gates an Academy of Management Annals (Annals) review — the ≤5-page, four-heading proposal submitted under the twice-yearly deadlines before any full review is invited. Builds the proposal; it does not gather the literature (amann-literature-synthesis) or run the portal preflight (amann-submission).
The English summary is being prepared. Showing the original description.
Use when planning an AAMAS project timeline from venue fit through abstract, full-paper or extended-abstract upload, supplementary material, the double-blind rebuttal, decision, IFAAMAS camera-ready, registration, and presentation, with track-specific deadlines and backward-planning offsets for a game-theory-plus-experiments paper.
The English summary is being prepared. Showing the original description.
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
The English summary is being prepared. Showing the original description.
Deep clause-by-clause NDA review from Recipient or Discloser perspective. Produces issue log with redlines, fallbacks, rationales, owners, deadlines. Use when reviewing NDAs for negotiation or approval.
The English summary is being prepared. Showing the original description.
Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log with preferred redlines, fallbacks, rationales, owners, and deadlines.
The English summary is being prepared. Showing the original description.
Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident — including "is this even a personal data breach?" triage, (2) User asks about breach notification obligations or deadlines, (3) User mentions "72 hours", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions "Data Breach" or "Incident" or "Data Leakage" or "Ransomware" or "Exfiltration", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs audit-ready breach documentation (.docx) or an EDPB-template-aligned breach notification / evidence file — including follow-up and withdrawal notifications, (11) Breach involves an AI system requiring AI Act Art. 73 serious incident screening.
The English summary is being prepared. Showing the original description.
Track A-share sell-side M&A and deal pipeline with milestones, deadlines, and action items. Adapted from the original deal-tracker skill for Chinese market deal processes. Triggers on "A股交易跟踪", "并购进度", "deal tracker China", "M&A pipeline A-share", or "track progress on [deal]".
The English summary is being prepared. Showing the original description.
Use when a campaign needs its full design asset list before anyone opens a tool — asset type, dimensions, channel, quantity, priority, owner, deadline, and status, with deadlines counted backward from launch day on a T-14 to D+1 timeline plus a naming convention. Trigger on 'campaign asset list', 'what does the designer need', 'list the design files', 'creative asset plan', 'how many banners do we need', 'the designer keeps asking what to make'. Not for — the spec for one individual image, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; an urgent mid-campaign swap, see `48-quick-visual-brief-global`; resizing an existing master, see `50-asset-resize-global`.
The English summary is being prepared. Showing the original description.
Build or review gRPC services and clients in .NET. USE FOR: ASP.NET Core gRPC, protobuf contracts, unary or streaming RPC, gRPC client factory, interceptors, deadlines, cancellation, channel reuse, backend service integration. DO NOT USE FOR: broad browser-facing APIs without gRPC-Web tradeoff review, SignalR realtime hubs, plain REST APIs. INVOKES: dotnet build/test and focused service or client smoke checks when code changes.
The English summary is being prepared. Showing the original description.
Manages newsroom editorial workflows. Use when tracking assignments, managing deadlines, or coordinating editorial calendars.
The English summary is being prepared. Showing the original description.