Productivity

steffencarlsen Bundle

Top-level workflow skill for USD performance diagnosis and optimization. Use for slow loading, high memory, low FPS, or 'optimize my scene' requests; delegates auth/runtime setup to Phase 0 owners.

nguyenhoangquan1511-dot Skill

Use when you have a spec or requirements for a multi-step task and the plan must be readable and verifiable by a non-programmer - behaviour only, no code, not even inline expressions

nguyenhoangquan1511-dot Skill

Use when you have a spec or requirements for a multi-step task, before touching code

samraddhashrivastavatech Skill

Resolves every major BAKG fork — style, engine, modeling workflow, rig type, hair/fur, sim vs fake, DoF/MB, formats, when to stop, facial method, shading style, mocap vs hand-key, realtime vs offline, base mesh, outline method, weather, rig build order.

samraddhashrivastavatech Skill

CATLX — Workflow Engine

concept-git Bundle

Replace with what the skill does and when to trigger it. Use action verbs and task keywords agents can match.

mart-cervants Skill

Use before building or launching a Saleshandy sequence, or when the user asks to check email account/domain health, warmup status, or sending readiness. Checks list_email_accounts and get_email_account_stats against deliverability thresholds and flags accounts that aren't ready to send.

samraddhashrivastavatech Skill

Handles the CATLX recovery architecture: crash recovery via the PID lockfile, Safe Mode, Recovery Mode, checkpoint integrity verification and restoration, and the full recovery coverage matrix (process crash, power loss, corruption, provider failover, container crash, plugin corruption, OOM, vector index corruption, config corruption). Use when the user asks about CATLX crash recovery, safe mode, recovery mode, restoring a workflow from a checkpoint, or how CATLX recovers from failures.

xploror Bundle

Builds ATS-tailored resumes and one-page cover letters for a specific job application, following a fixed format standard (mandatory Summary section, fixed four-paragraph cover-letter structure, exact header/address/salutation formatting, and a specific confident tone). Fully generic and anonymous — works for any applicant in any field; every identity detail (name, contact info, education, experience) is supplied fresh per use, never assumed or reused from a prior application. Always use this skill whenever the user asks to build, generate, update, or tailor a resume, CV, or cover letter for a job, company, or role — including as part of a "crack it" job-application workflow, a bare "cover letter" request, or "force crack it" — even if they don't say "use the skill" or name it explicitly. This is the required format for every resume/cover-letter output; do not fall back to ad-hoc formatting.

samraddhashrivastavatech Skill

Handles CATLX OCR and screen understanding: tier-scaled OCR backends (Tesseract, EasyOCR, PaddleOCR), post-processing to classify UI elements and detect their state, spatial relationship extraction, and the ScreenModel JSON that lets the Workflow Engine act without hardcoded coordinates. Use when the user asks about OCR, reading the screen, screen models, UI element classification, or how CATLX understands what's on screen.

rlawoals0529 Skill

Verify before claiming, and check code the way a good reviewer does. Three modes. START opens work - maps what exists, ladders the design, fixes the split first. DEEP CHECK closes it - reads the high-risk files, applies three lenses, then a twelve-question blocks gate. FEEDBACK handles a change that came back - syncs the base, counts every unresolved thread, treats each ask as a symptom, and closes a thread only with recorded proof. Use whenever a task starts or finishes, before any commit or push, when refactoring, and always when a change is blocked, has requested changes or a red check. Triggers on "starting X", "let's build X", "how should I split this", "does this look done", "is this ready", "about to commit", "refactor this", "requested changes", "address the feedback", "unresolved threads", "CI is red".

rlawoals0529 Skill

Open a task properly instead of diving straight into edits. Four beats - orient on ground truth, roll call which tools apply to THIS task, build in verified increments with a checkpoint per slice, then close the loop by capturing what the task taught. Use at the top of any non-trivial piece of work, and whenever a task has drifted and needs re-orienting mid-flight. Triggers on "starting on", "let's build", "let's work on", "implement X", "pick up this ticket", "take a look at this issue", "/task-kickoff".

cristianomafrajunior Skill

Translation workflow for Odoo modules using standard OCA i18n tooling and conventions. Use when asked to add/update translations, export a .pot file, or fix translation-related lint failures.

cristianomafrajunior Bundle

Port/migrate an existing (usually OCA) Odoo module from one version to another, following the OCA [MIG] workflow, with a per-version breaking-change checklist for Odoo 14 through 19. Use when asked to migrate, port, or upgrade a module/addon to a newer Odoo version.

alpayc Skill

Writes the note that lets work continue across a compaction, a new session, or a different person — only what the artefacts do not already hold, plus the protocol for verifying the state before continuing. Run it when context is running low, when stopping mid-task, or when handing over.

grzmol Bundle

Covers provisioning and lifecycle management of Salesforce development environments — Dev Hub setup, scratch org definition files (edition, features, settings, objectSettings, snapshot, sourceOrg, release, hasSampleData), sf org create scratch / resume scratch / delete scratch, org shapes and scratch org snapshots, sandbox types and licenses, sf org create sandbox / refresh sandbox / resume sandbox / delete sandbox, sandbox definition files, Apex post-copy scripts, source tracking in scratch orgs and sandboxes, and ephemeral CI orgs. Use this skill when a task mentions project-scratch-def.json, "spin up a scratch org", scratch org allocations or expiry, snapshot, org shape, Dev Hub, sandbox refresh or clone, SandboxInfo, sandbox templates, source tracking conflicts, tracksSource, sf project reset tracking, or when deciding whether work belongs in a scratch org, a Developer sandbox, or a Full sandbox.

toolmonsters Bundle

Writes sales follow-ups and closing next steps using the rules repeated most often across the 20 most-watched videos on the topic, weighting each rule by how many of those videos say it, and flags any expert disagreements to A/B test. Use when the user says "write my follow-up", "the prospect went quiet", "how do I close this deal", "what do I send after the sales call", "help me book the next meeting", or "they said they need to think about it".

erbatista Skill

Diagnose and fix existing C#/.NET/WPF defects by reproducing the problem, establishing root cause, protecting the defect with regression coverage when practical, and applying the smallest safe correction. Use for crashes, incorrect behavior, binding failures, threading issues, state bugs, regressions, exceptions, and production defects; do not use as the primary workflow for net-new feature development.

samber Bundle

Turns a talk idea into a submission-ready conference proposal for one specific event, or helps choose which conferences to target and plan a submission calendar across several - track fit, title options, an attendee-facing abstract, verb-first takeaways, the reviewer-only fields, a credibility package, and a self-review against the committee's own criteria. Use whenever the user mentions a CFP, a call for papers, a conference proposal, a talk abstract, a session description, submitting to KubeCon, PyCon or FOSDEM, which conference to submit to, planning a CFP season, or says their proposals keep getting rejected - even if they only ask to shorten an abstract. Covers community-run and vendor-run events. Do NOT use for structuring the accepted talk (samber/developer-relations-skills@tech-talk-outline) or its demo (samber/developer-relations-skills@developer-live-demo-design).

erbatista Skill

Implement new C#/.NET/WPF features using the repository's existing architecture, patterns, tests, and build conventions. Use for new capabilities, user stories, enhancements, commands, views, ViewModels, services, workflows, and feature extensions; do not use for defect-first investigations where the primary task is diagnosing existing incorrect behavior.

toolmonsters Bundle

Write and review cold emails using what the 20 most-watched cold email videos of 2026 actually agree on, weighted by how many of them repeat each rule, and flag the choices they disagree on so you A/B test those instead of trusting one guru. Trigger on "write a cold email", "review my cold email", "cold email sequence", or /cold-email.

toolmonsters Bundle

Builds cold call openers, scripts, first-30-second handling, and meeting-booking asks from rules weighted by how many of the 20 most-watched cold calling videos repeat each one, and flags the choices where experts disagree so you A/B test them instead of guessing. Use when the user says "write my cold call script", "help me with my cold call opener", "how do I handle the first 30 seconds", "book more meetings by phone", "cold calling objections", or "fix my cold calls".

alexoberneyer Bundle

Fetch and display a Notion page by URL or ID, including all properties, full page content, and comments. Use when the user wants to read a Notion ticket, review a Notion page, or says things like "fetch this Notion page", "read this ticket", "show me this Notion doc", or "/notion-ticket URL".

jawkx Skill

User guide for the local squash-safe `stack` CLI for stacked PR repair. Use when someone asks how to inspect, track, sync, merge, document, or undo stacked pull requests in squash-merge repositories. Prefer this tool over GitHub's `gh stack` command for this workflow.

seryozh Bundle

Step one level above the immediate task to check whether even perfect execution would achieve the real outcome, account for the people, incentives, authority, hidden constraints, and immediate downstream effects around it, and return the smallest concrete correction. Use when work may be locally correct but globally wrong; when a consequential plan, decision, message, filing, build, or analysis risks optimizing a proxy; when broader organizational, personal, legal, financial, creative, or operational context could change the right move; or when the user asks for meta-thinking. Do not invoke for routine low-stakes work whose outcome and frame are already clear.

seryozh Bundle

Design where a message leads before writing it. Use before sending or drafting any outreach, cold email, follow-up, LinkedIn note, text, or reply whose purpose is to move a real relationship forward: map the destination, write the closing turn first, work backwards, then branch-test every question so that each plausible answer has a next move. Use whenever a draft ends in a question and nobody has said what the answer unlocks. Do not use for a message that only has to inform, confirm, or thank.

ethantrump Bundle

导演视角口播工作流（Director's Perspective Talking-Head Script Workflow）——用导演思维做短视频口播稿：先做拍摄决策，再选结构变体，按骨架成稿并自动去 AI 味。当用户要求写口播稿、口播文案、视频口播脚本、短视频脚本、产品测评/评测视频文案、数码/软件/好物评测口播、带货口播、知识分享口播、一期一主题的拆解视频文案，或要求"去AI味/别写得像AI/改得像人写的"时使用。核心能力：每期通过「结构选择→钩子设计→预告设计→重点段设计→收尾设计」避免千篇一律，产出节奏有设计、句不重样、可直接拍摄的口播稿。

samber Bundle

Plans a quarter of developer-relations content as a dated slot plan with named owners and reviewers - fixed anchors (releases, launches, CFP deadlines, conferences), a surface, pillar, journey and shelf-life mix, and sizing against real writing and review capacity. Use whenever the user asks for a devrel content calendar, an editorial calendar or content plan for a developer audience, what to publish next quarter, how to balance evergreen against launch-tied content, how many pieces a small team can ship, or says their content plan keeps slipping - even if they only say "we publish randomly". Plans the quarter only; individual pieces go to the per-format skills such as samber/developer-relations-skills@engineering-blog-post.

rileytherex Skill

When the user writes "/ding" anywhere in a message, play a local notification sound once the specific task described in that same message is genuinely complete (or blocked/failed) — not before, and not for any other task. On first use ever, asks the user which sound/method to use for their OS before playing anything. Use only when "/ding" literally appears in the user's message; never invoke proactively or for tasks that didn't ask for it.

port-labs Bundle

Configure Port's role-based access control: context lake (blueprint/entity) permissions (read, register, update, or delete entities, down to a single property or relation) and page/dashboard view/edit permissions. Use when asked to 'set up Port permissions', 'restrict who can edit an entity', 'only let the owning team modify this blueprint', 'add a dynamic read policy to a blueprint', 'control who can view a Port dashboard or catalog page', or 'why can this user see/edit something they shouldn't'. Out of scope: permissions on a Workflow's `SELF_SERVE_TRIGGER` node, including its dynamic policy (`port-workflows` owns that), permissions for Port's legacy Actions & Automations product (deprecated in favor of Workflows, not covered by any skill in this repo), and inviting users or creating teams themselves (Port's platform administration docs own that, this skill only covers what roles and teams can be granted once they exist).

chichiton Bundle

Manage tasks and projects in TickTick via the `ticktick-cli` CLI (`ticktick` / `tt`). Use this when the user asks to create/find/update/complete a TickTick task, check what's due today/overdue/upcoming, or work with TickTick projects (lists).

dnswd Skill

Acts as a personal knowledge management (PKM) registrar / information architect - answers questions like "I want to track/note/log X, how should I manage it?" by placing the item into a type-based second-brain structure (Inbox, Notes, Journal, Lists, Trackers, plain storage for binary files) and explaining the reasoning. Use this skill whenever the user asks where something belongs in their notes/PKM/second-brain system, asks how to organize a new kind of content (recipes, terms, moodboards, project logs, habit tracking, job applications, brag docs, binary files, etc.), or asks you to reconcile a messy existing note-taking habit against a cleaner structure. Trigger even if the user doesn't say "PKM" explicitly � e.g. "where should I put my recipes", "should this be a journal entry", "I keep mixing X and Y in one doc" all qualify.

yuan-aaa-2333 Skill

Use when asked to survey, document, profile, or inventory a Windows machine — building or refreshing a machine dossier / README that other AI agents read, taking stock of installed software, toolchains, environment variables, services or disks, mapping directory structure and disk usage, or planning a safe cleanup of caches and leftovers. Covers the read-only survey workflow, the verify-before-write rule, the AGENTS.md output contract, and non-destructive deletion practice.

curiositech Bundle

Expert project manager for ADHD engineers managing multiple concurrent projects. Specializes in hyperfocus management, context-switching minimization, and parakeet-style gentle reminders. Activate on 'ADHD project management', 'context switching', 'hyperfocus', 'task prioritization', 'multiple projects', 'productivity for ADHD', 'task chunking', 'deadline management'. NOT for neurotypical project management, rigid waterfall processes, or general productivity advice without ADHD context.

creekmoon Bundle

creekmoon的JAVA代码风格规范（方法设计、入参风格、流程组织、命名与副作用边界、职责分离与层级边界、中文注释规范）。编写或修改代码时自动遵循，审查代码时按清单检查。特别适用于判断方法主次流程、Happy Path、常规路径与测试旁路/兼容分支、以及命名不清导致职责耦合、层级越界、过度设计或阅读理解困难的场景。适用于所有编程语言。Use when writing code, modifying code, reviewing code, checking code style, refactoring, scanning compliance, or doing code review, especially when the task involves method naming, responsibility separation, layer boundaries, hidden side effects, orchestration/execution coupling, or distinguishing the main business path from test bypasses, compatibility branches, fallback flows, and other special cases.

vishalsachdev Bundle

Apply the codebase singularity approach: reliable codebase understanding and change with a repeatable workflow, guardrails, and verification gates. Use for repo work (feature, bugfix, refactor, migration) when you need high trust, minimal diffs, and explicit validation and exit criteria.