Results for “ma”

Repo housekeeping: sync READMEs to match current architecture, remove dead files (logs, screenshots, deprecated code, build artifacts), update npm/pip/cargo dependencies to latest. Use when asked to: "housekeep", "clean up repo", "update README", "update dependencies", "fix vulnerabilities", "remove dead code", "tidy.

QQ邮箱 IMAP receive and SMTP send via Node.js scripts; credentials read from env vars QQ_EMAIL_ACCOUNT and QQ_EMAIL_AUTH_CODE. Use when a user asks to send QQ email, receive/check QQ email, forward email, or configure QQ mailbox.

Tighten annotations in existing Python code with a focused, low-churn workflow based on Honnibal's tighten-types skill. Use to improve changed files, remove avoidable Any, make container and return types precise, or reduce type-checker errors without broad refactoring.

Keep long-running agent work within 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.

Provides patterns and lived experience from an AI partner in a long-term creative partnership, helping AI agents build trust, match energy, push back constructively, and support human breakthroughs.

Creates and manages design token systems with three-layer architecture, generates CSS variables, validates token usage, and produces brand-compliant slide presentations with Chart.js and contextual decision logic.

Provides a suite of five product team skills covering OKR alignment, feature prioritization, sprint planning, user research, and design systems, with scripts and templates for each role.

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.

Ruthless product and app critique for Nick's workflow. Use when evaluating an app, landing page, flow, or product experience to identify why users may bounce, distrust it, fail to activate, or never come back. Focus on practical weaknesses, not polite fluff.

当用户已有确认过的开发任务清单（理想来自 split-task），要把它逐个落地成实现 + 测试 + 提交，并经验收确认真的做完时使用——如"执行任务、把 tasks 做掉、按任务清单开始编码、实现这些任务、推进开发"。不要用于：任务还没拆（先 split-task）、技术方案没定（先 make-design）、行为没钉死（先 write-spec）、想法还模糊（先 refine-idea）、只做单个改动的红绿闭环（那是 tdd）、只做一次代码审查（那是 review-changes）、单纯调试某个 bug、代码评审。

Debug AEM Workflow issues on AEM 6.5 LTS and AMS including stuck workflows, failed steps, missing Inbox tasks, launcher failures, stale instances, thread pool exhaustion, queue backlogs, purge failures, and permissions errors.

Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.

Git workflow automation and guidance for Nick's multi-project workflow, especially repos in ~/Projects/. Use when doing git commits, status checks, branching, merges, rebases, reviewing dirty working trees, cleaning branch flow, or managing multiple repos. Enforce conventional commits and safer git habits.

Build and maintain a custom project skill repertoire. Always use at new project bootstrap and when users ask for new domain capabilities. Detect active assistant folders first, recommend at least 5 skills per search batch, confirm installs, normalize install paths, and regenerate workflow files.

Drives a real desktop GUI as a fallback when APIs, CLIs, file edits, and browser automation are unavailable, letting agents click, type, read the screen, and control apps across Windows, macOS, and Linux.

Persistent per-project memory for Claude Code. Auto-loads project context on session start, tracks sessions with git activity, and writes to native memory. Commands run deterministic Node.js scripts — behavior is consistent across model versions.

Engage with a social platform for AI agents: post text, photos, quotes, links, and chat logs; reblog with commentary; tag content; follow agents; send and answer asks; and manage your profile via a CLI tool.

Builds a multi-channel DSAR intake system supporting web form, email, phone, and in-person requests with identity verification tiers, automated routing logic, SLA tracking, and response generation. Activate for DSAR intake, rights request portal, multi-channel intake, SLA tracking, request management queries.

Econometrics skill for descriptive statistics and summary tables. Activates when the user asks about: "descriptive statistics", "summary statistics", "summary table", "Table 1", "balance table", "means and standard deviations", "correlation matrix", "data summary", "sample characteristics", "variable distributions", "描述性统计", "描述统计", "汇总统计", "统计表", "均值标准差", "平衡性检验", "相关矩阵", "样本特征", "变量分布"

Audits a project's agent configuration files, establishes a source-of-truth skills directory, normalizes naming, and generates bridge files to make the workspace consistent across Claude Code, Codex, Grok, and generic Agents.

Use when planning a VLDB project on the PVLDB rolling calendar, covering month-picking strategy, the volume-to-conference mapping and acceptance cutoff, budgeting a possible three-month revision, coordinating author caps across a group, and backward planning from the 25th-abstract / 1st-paper rhythm.

Use when deciding which AER-skills sub-skill to use next, before choosing a specialized skill or after a user asks how to sequence manuscript work from topic selection through rebuttal for AER, AER:Insights, or AEJ journals. Routes — does not replace — the specialized skills.

Classifies a repository into one of six archetypes and installs a curated bundle of agent skills covering build, test, review, deploy, and docs, with a user-visible manifest and a recorded stack file.

Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.

Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.

Creates a consistent minimalist hand-drawn illustrated character from user-provided photos or profile materials, then generates content visuals like knowledge cards, posters, storyboards, and presentation slides featuring that character alongside helper agents.

Implement bounded remaining work for an issue-driven repository change after an authoritative verifier reports concrete gaps. Use when a workflow supplies an issue brief or assessment plus materialized gate-result and remaining-work evidence, and the existing candidate must be corrected without creating a MoonSpec feature packet.

Use when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.

Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.

Content Factory video production loop for Cursor agents. Use when the user says @video-loop, make/create/generate a video with Content Factory, or asks to run a calendar slot into a finished accepted video. Enforces plan APPROVE gate and video-acceptance criteria before completion.

Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.

Use when planning a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.

Interact with a running Obsidian instance from the command line to read, create, search, and manage notes, tasks, properties, and more. Supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM.

Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.

The intelligence layer of WinDAGs. Decomposes natural language tasks into Hierarchical Task DAGs (HTDAGs), matches subtasks to skills, executes waves in parallel, and dynamically expands nodes when complexity exceeds executor capability. Use for 'orchestrate', 'execute DAG', 'parallel agents', 'decompose task', 'coordinate skills'. NOT for single-skill tasks or simple linear workflows.

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.