Productivity

1t1scool Bundle

QA workflow for testing a feature or task implementation. Analyzes changes, produces test plans, and describes concrete test scenarios. Use when user says "test this", "write test plan", "what should I test", or "QA this branch".

1t1scool Bundle

Plan implementation for a feature or task. Two modes — fast (single quick plan) or full (richer plan with optional git branch/worktree flow). Use when user says "plan", "new feature", "start feature", "create tasks".

1t1scool Skill

Full task lifecycle — plan, implement, verify, review, qa, changelog, squash-commit. Use when user says "/aif-task", "новая таска", "сделай таску", "task flow".

s3yed Skill

Use when scripting Instagram reels or story sequences for a personal/founder brand, optimizing an IG bio for conversion, or building a content calendar that turns a cold audience into DM leads - the value/educational/credibility content system plus story-sequence frameworks. Source - Grow Acquisition 3.0 (Nikk Kleinherenbrink).

hibra999 Bundle

Use THUML Time-Series-Library for process-change event detection through its documented anomaly_detection task after validating prepared multivariate time-series data, including supported PSM/MSL/SMAP/SMD/SWAT loaders, run.py scripts, reconstruction-error thresholds, anomaly_ratio, event-level adjustment, Accuracy/Precision/Recall/F-score, and leakage-safe conversion of anomaly intervals to changepoint-like starts or ends.

mturac Skill

ecc用の証拠ベースのメールボックストリアージ、ドラフト作成、送信検証、および送信済みメールセーフフォローアップワークフロー。ユーザーがメールを整理したり、実際のメールサーフェスを通じてドラフトまたは送信したい、または送信済みメールに何が到着したかを証明したい場合に使用します。

mturac Skill

Gitワークフロー、ブランチ戦略、コミットメッセージ規約、およびプルリクエストプロセス。

jcdavis131 Skill

Run environmental recon at the start of a coding session before writing any code — disk space, blocker state, target path file count, and queue blockers. Use at session boot, when switching to a new task or target directory, or before any non-trivial change in an unfamiliar area.

jcdavis131 Skill

When live recon contradicts a prior assumption or a documented blocker, trust the live evidence, state the correction explicitly with the evidence, and update your plan. Use whenever you discover the environment differs from what you (or the docs, or the task notes) assumed — a service that's actually running, a port that's actually open, a blocker that's actually resolved, a dependency that's actually installed.

jcdavis131 Skill

When you deliberately choose not to do something that looks like it would be part of the task, state the non-action and its rationale explicitly so it isn't read as an oversight. Use whenever you skip a plausible-looking step on purpose — a file you didn't edit, a feature you didn't wire, an existing issue you didn't rework, a test you didn't add — because of a real constraint or a lane/spec boundary.

jcdavis131 Bundle

When a backgrounded command fails while the foreground lane is making progress, do not abort the foreground lane — log the failure, queue it for triage, and continue. Triage the failure at the next natural boundary. Use whenever a background shell task, background subagent, or parallel lane fails while you're mid-task on something independent.

kinkwanc22 Skill

Detect and rewrite AI-like Chinese text with a practical workflow for scoring, humanization, academic AIGC reduction, and style conversion. Use when the user asks to 去AI味, 降AIGC, 去除AI痕迹, 论文降重, 知网检测, 维普检测, humanize chinese, detect AI text, or make Chinese text sound more natural.

kaiohenricunha Skill

Project-aware git workflow: conventional commits, PR creation, safe pushes, PR merges, and branch naming suggestions. Triggers on: "conventional commit", "create PR", "push changes".

kaiohenricunha Bundle

Post AI-generated review findings on a GitHub PR as inline review comments via the gh CLI — the bot-style review-comment workflow GitHub Copilot used to provide before it got rate-limited. Idempotent (hidden marker dedup), rate-limit conscious (respects GitHub's 80/min secondary limit), and dry-run by default in interactive mode. Pairs with `review-pr`, which consumes the comments this skill produces and applies fixes. Triggers on: "post PR review", "leave inline comments on PR", "AI review and comment on PR", "Copilot-style PR review".

thearchitectit Bundle

Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. This skill should be used when Cline needs to identify conflict avoidance, filler words, speaking patterns, leadership tendencies, or communication improvement opportunities from meeting transcripts for professional development and coaching.

jorgeasaurus Skill

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

jorgeasaurus Skill

Use this skill whenever the user asks to brainstorm, draft, edit, review, or publish a Jorgeasaurus blog post, especially posts about PowerShell, Intune, Microsoft Graph, endpoint management, automation, scripting patterns, or engineering practice. This skill captures Jorge's practical field-note style, MDX post structure, code-example standards, release checklist, social card expectations, and verification workflow.

devguyrash Bundle

Shape vague intent into clearer product decisions before execution. Use when the task involves: (1) exploring ambiguous product, design, or implementation directions with an Option Map, (2) converging on a chosen direction before writing durable context/docs artifacts, (3) generating Probe Packs with acceptance examples, adversarial checks, non-goals, and final source review prompts before handoff, or (4) reviewing planning output for premature docs, false blockers, HOW leakage, weak probes, and lost source nuance. Do not use for direct execution unless a probe note or handoff is needed first.

devguyrash Bundle

Detects repo languages, frameworks, task runners, distribution shape, and CI surface, then scaffolds or updates a repo-level harness: justfile, GitHub Actions CI/dist workflows, .gitignore/.gitattributes support files, and local state under .local/harness/. Use when the task involves: (1) Bootstrapping a new or existing repo with a standardized command surface, (2) Creating or updating a justfile with build, test, lint, fmt, ci, dev, or dist recipes, (3) Scaffolding GitHub Actions CI or distribution workflows, (4) Configuring .gitignore, .gitattributes, or Git LFS for a project, (5) Standardizing or updating a project command surface without rewriting build system internals, or (6) Any task requiring repo-level harness scaffolding or project command surface management.

devguyrash Bundle

REQUIRED for Rust async runtime, task-lifecycle, cancellation, backpressure, Send-boundary, or pinning work—do not write, review, debug, or scaffold those surfaces without this skill. Always compose with rust-development; exclude synchronous-only work. If Rust work is asynchronous, use this skill.

devguyrash Bundle

Use for substantive Go source, modules, or tooling. Covers APIs, errors, context, concurrency, resources, and tests; exclude framework-only and workflow-only work.

devguyrash Bundle

Design durable, outcome-oriented Playwright and browser e2e tests that prove product behavior instead of recording today's DOM. Use when the task involves: (1) Creating, reviewing, or refactoring Playwright tests, (2) Designing selector strategies, page objects, fixtures, e2e assertions, or trace/artifact capture, (3) Reducing brittle selectors, fixed waits, layout assertions, or flaky authenticated flows, (4) Testing third-party, authenticated, frequently changing, or browser-extension UIs, or (5) Any task involving Playwright e2e test design or brittle-test cleanup.

devguyrash Bundle

Use for substantive C# source, projects, or .NET tooling. Covers nullability, disposal, async, APIs, and targets; exclude framework-only ASP.NET/EF and workflow-only work.

devguyrash Bundle

Build portable dynamic Espanso forms where a script or binary generates form layouts at runtime. Use when the task involves: (1) Creating or modifying Espanso form triggers or match files, (2) Building dynamic Espanso forms with runtime-generated layouts or choices, (3) Scaffolding a new Espanso form provider pattern, (4) Configuring Espanso YAML for scripted fields or runtime-generated options, (5) Debugging or linting Espanso form configurations, (6) Implementing clipboard or output patterns for Espanso expansions, or (7) Any task involving Espanso text expansion with dynamic or scripted form UIs.

devguyrash Bundle

Use when task, thread, actor, worker, callback, cancellation, backpressure, synchronization, or parallel-execution contracts materially shape software behavior. Compose with language/runtime and performance skills; exclude trivial async syntax and Rust-runtime work owned by async-rust.

hhqc-369 Skill

Route generative image, video, audio, creative-ad, UGC, product-video, and multimodal workflow requests to SamurAIGPT/Generative-Media-Skills.

izzyfresh Bundle

End-to-end AlphaEvolve experiment orchestrator. Chains the Design, Runner, Monitor, and Post-Experiment skills into a seamless workflow. Detects where the user is in the experiment lifecycle and picks up from there. Triggers on: "evolve this function", "optimize with AlphaEvolve", "set up an AlphaEvolve experiment", "make this faster", "improve performance", "find a better algorithm", "optimize this function", "use evolutionary search", "AlphaEvolve this", "run AlphaEvolve end to end".

josstei Skill

Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved implementation plan, and then execution with shared session state

stacksjs Skill

Use when implementing authentication, authorization, passkeys, TOTP/2FA, RBAC, gates, policies, session auth, token management, email verification, password resets, or rate limiting in a Stacks application. Covers the @stacksjs/auth package, config/auth.ts, app/Gates.ts, and app/Middleware/.

stacksjs Skill

Use when working with the Stacks CLI (buddy/bud/stacks/stx) — understanding all 50+ commands with their flags and options, adding custom commands, the make:* scaffolding commands, development server commands, build commands, deployment commands, email/mail commands, environment management, or domain/DNS commands. Covers @stacksjs/buddy and all CLI command files.

stacksjs Skill

Use when working with email in a Stacks application — sending emails via SES/SendGrid/Mailgun/Mailtrap/SMTP, email templates with STX, email drivers, the Mail singleton, the EmailSDK for inbox management, or email configuration. Covers @stacksjs/email, config/email.ts, and app/Mail/.

stacksjs Skill

Use when setting up or configuring the Stacks development environment — dev server, hot reload, development utilities, or IDE configuration. Covers the @stacksjs/development package, the dev server, CLI commands, reverse proxy, SSL, and dev workflow.

stacksjs Skill

Use when setting up or modifying Stacks project-level configuration — bunfig.toml preload order, the tsconfig chain and TypeScript 7 / tsgo type checking, workspace configuration, .env setup, package.json scripts, system requirements (Bun >= 1.3.0, SQLite >= 3.47.2), or the project bootstrap process. For individual feature configs (database, email, auth, etc.), see the specific package skills instead.

stacksjs Skill

Use when implementing notifications in Stacks — multi-channel notifications (email, SMS, push, chat, database), the database notification driver with read/unread tracking, notification factories (useEmail, useSMS, useChat, useDatabase), or notification configuration. Covers @stacksjs/notifications and config/notification.ts.

skywatch-bsky Skill

Use when fixing Osprey SML validation errors or reviewer-identified issues. Contains error categories, fix patterns, and debugging workflow. Not triggered on general coding tasks — only when resolving specific SML errors.

skywatch-bsky Skill

Queue-workflow triage with Ozone-comment output mode. Use when the user asks to review Ozone reports and post evidence/recommendations directly as Ozone comments for later human review, rather than presenting the batch in chat. Covers the full per-subject evidence workflow — ClickHouse rule hits, content context, profile, moderation history, reply threads — with output written as Ozone comments and account escalations instead of in-chat detail blocks.