Productivity

Systematic workflow for verifying bug fixes to ensure quality and prevent regres...

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents

Update GSD to latest version with changelog display

Validate built features through conversational UAT

Reapplies locally saved modifications to GSD workflow files after an update has wiped and reinstalled them, using intelligent merging to handle upstream changes.

Load bounded working context at the start of a coding session. FIRES ON EVERY FIRST USER MESSAGE in a fresh session, regardless of content — including bare greetings ("hi", "hello", "hey"), task-only openers, or "let's start". Also triggers on: "fresh session", "session start", "first message in a new thread", "new chat", "cold start", "begin work in this repo", "starting work", "continue from prior session", "what were we working on", "resume", "what happened last time", "load memory", "recall context", "create a handoff", "prior session context", "latest handoff", "current state", "decision context". Skip ONLY if the user explicitly says "fresh start" or "ignore prior context". Self no-ops if invoked mid-session when context is already loaded.

Best practices and patterns for C# async/await programming including Task and ValueTask usage, CancellationToken propagation, IAsyncDisposable and await using, ConfigureAwait, async streams (IAsyncEnumerable), parallel task execution, and common pitfalls like deadlocks and async void. Use this skill whenever writing, reviewing, or refactoring asynchronous C# code — including when the user mentions async methods, Task-returning APIs, cancellation, deadlocks, blocking on async code, or resource disposal in async contexts, even if they do not explicitly say "async best practices."

Repurpose one piece of content into platform-native formats across short-form, social, and email without copy-pasting.

Turn a raw transcript or scribble into decisions, action items with owners and dates, and open questions - so nothing agreed in the room evaporates afterwards.

Full autonomous engineering workflow

This skill should be used when searching, fetching, or downloading emails from Gmail. Use for queries like "search Gmail for...", "find emails from John", "show unread emails", "emails about project X", or "download attachment from email".

Use when the user wants to build a content strategy, content calendar, editorial plan, or pillar content architecture using Gemini CLI. Trigger phrases: Gemini CLI content strategy, build content calendar via CLI, content plan with Gemini, content pillars generator CLI. For individual posts see gemini-cli-social.

ALWAYS use this skill when committing code changes — never commit directly without it. Creates commits following Sentry conventions with proper conventional commit format and issue references. Trigger on any commit, git commit, save changes, or commit message task.

Use when creating or editing a macOS LaunchAgent for a recurring or scheduled script. Covers plist structure, PATH resolution, multiple trigger times, the reload workflow, and which behaviors launchd already handles so they don't need to be rebuilt.

Runs repeatable AI work as checked, budgeted workflow files.

Create asana task creator operations. Auto-activating skill for Enterprise Workflows. Triggers on: asana task creator, asana task creator Part of the Enterprise Workflows skill category. Use when working with asana task creator functionality. Trigger with phrases like "asana task creator", "asana creator", "asana".

Cut releases, validate changelogs, and manage git hooks for a project.

Start-of-session routine — load context, check state, suggest next task. Use at the beginning of a fresh session or after a context reset.

Composite skill — land a safe first PR in an unfamiliar repo without rediscovery loops or guessing at conventions. Chains onboard-new-repo (architecture + scripts + CI scan) → context-pack (relevant files + standards + ADRs for the scoped change) → scope-and-execute (narrow the task) → test-driven-development (write failing test first) → pr-to-release (open the PR). Use the first time you contribute to a repo OR when an unfamiliar contributor needs a guided first change.

Composite skill — configure a fresh or under-configured repo for the release-branch workflow in one pass. Creates the `release` branch on origin, seeds `CHANGELOG.md` (Keep-a-Changelog format), drops in `.claude/dep-sweep-config.json` + `.claude/branch-hygiene-config.json` + a `release-cadence.md` standard stub, opens a `chore/repo-bootstrap` PR to main. Use instead of manually setting these up before the first `/pr-to-release` — without this, none of the release-branch composites can fire. Idempotent: skips any artifact that already exists. Replaces ad-hoc "set up the new repo" scripts.

Daily live-trend scan for any active brand — surfaces timely topics, launches, news, and community pain points in the brand's niche, scored for relevance and timeliness, deduplicated against a rolling log, and written as candidate topics the social calendar can pull.

Assign a task to a specific role on your team.

Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.

Resume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.

Use when the user explicitly asks for HOTL routing or needs guidance choosing the right HOTL workflow skill.

Generate a map of all files relevant to a task before making changes

Proposal pricing workflow producing defensible line-item, tiered, or value-based pricing with calibration and sanity checks. Use when the user needs a quote, estimate, tier packages, pricing strategy, rate calibration, or discount modeling for a proposal brief. Triggers: 'price this proposal', 'build tiered pricing', 'line-item estimate', 'value-based price', 'calibrate rates', 'sanity check this quote'.

Write a 5-part mini spec (goal, constraints, acceptance criteria, verification, done gate) before starting any multi-step, externally-delivered, or risky task. Triggers when: a request has 3+ steps, touches external delivery, or is easy to declare done too early. NOT for: single lookups, one-line edits, routine acks, or simple factual answers.

4-layer recall procedure (durable → semantic → PostgreSQL → daily notes) before claiming "no context". Invoke when user explicitly asks "do you remember", "what did we discuss about X", "search history". NOT a general assistant — only fires when recall is the explicit task. Drop the prior "use proactively" rule. Triggers: "do you remember", "what did we discuss", "when did", "find that conversation about".

Automatically creates new skills from complex problem-solving sessions. Triggers at the end of multi-step tasks that required novel approaches, debugging sessions, or workflow creation. Use when: a task took 3+ tool calls, involved a non-obvious solution, or established a pattern likely to recur. Also triggers on: "create a skill from this", "save this as a skill", "this should be a skill".

Generate implementation plans from approved designs — plan-generator, phase-based plans, parallel batch execution, task dependency graph, owner skill routing, acceptance criteria, global done criteria, plan frontmatter, layout contract, interaction contract, anti-drift rules, plan format, AD-2 byte-for-byte gate, scope definition, execution plan, phases and batches, task anatomy, plan file format

Skill for the Workflow-contracts area of paddock. 51 symbols across 11 files.

General implementation only when no narrower task or ecosystem skill fits. Do not combine with a clear specialist skill.

当用户已有确认过的行为规格（理想来自 write-spec），要在编码前把技术问题问清楚、比较方案、锁定技术决策——技术选型、架构、数据模型、接口契约、错误处理、测试策略——并沉淀成可 review 的技术设计依据时使用。不要用于：行为/需求还没钉死（先 write-spec）、想法还模糊（先 refine-idea）、任务拆解或实现计划（那是下游 split-task）、调试或代码评审。

当要在开始一段开发、或并行多个任务前，建立隔离的 git 工作区（worktree）以免污染当前工作区时使用——如"开个 worktree、隔离工作区、并行任务各自隔离"。通常由 execute-task 在执行前调用。先锁定 expected base，再选择能保证该基线的创建方式，并在创建后验证 HEAD。不要用于：不需要隔离的小改动、收尾/合并/清理（那是 finish-branch）、非 git 仓库。