Productivity

yiyousiow000814 Skill

Human-written economic calendar event descriptions for a global calendar with XAUUSD relevance and impact rules. Use when writing or reviewing event descriptions or notes for economic calendar entries, ensuring concise non-robotic language and conditional XAUUSD impact guidance.

geoffjay Bundle

Task management for AI agents across context windows. Use when agents need to track work, log progress, hand off state, and maintain context across sessions. Includes workflows for single-issue focus, multi-issue work sessions, and structured handoffs. Essential for AI-assisted development where context windows reset between sessions.

zaxbysauce Skill

End-of-session knowledge closeout for the zmem store. Recall what is already known, capture only generalizable lessons with honest signals, supersede anything this session proved WRONG, consolidate near-duplicates, and review skill-promotion candidates. Use when the user says "closeout", "wrap up", "end of session", "capture what we learned", or after finishing a substantial task whose lessons would otherwise be lost. Not for mid-task capture — the PostToolUseFailure and Stop hooks already handle that.

cynrath Bundle

Enforce the ACKit docs-first, task-first workflow with one active checklist item and evidence-based completion.

stepkar2004 Bundle

Publishing and discoverability - fire whenever the user wants to post, announce, launch, or promote anything (a LinkedIn post, an X thread, a Show HN, a launch/reflection draft), wants something findable (GitHub repo invisible in search, topics/description/social preview), or asks for a hook, post draft, or post image/GIF. Runs decide -> optimize -> draft -> post; the human always does the actual posting. Load references/linkedin.md, references/github.md, references/visuals.md on their triggers. Not for long-form video production, and not for in-repo docs (workflow step 4 owns those).

aishajv Skill

This skill should be used when the user says "push", "push to remote", "create PR", "create MR", "pull request", "merge request", "open PR", or when committing and pushing code to GitHub or GitLab. Covers git workflow rules, branch naming conventions, commit message format, and the push + PR/MR creation procedure.

mammadebastar Skill

Apply a sysi change in build phase using the native change workflow and Superpowers discipline.

muyen Skill

Git workflow management. Triggers when creating branches, preparing PRs, or managing merge decisions.

snyk Skill

Start an implementation task with proper planning, TDD workflow, and session hand-off. Use when beginning work on a Jira issue, starting a new feature, or resuming implementation work. Triggers on phrases like "start task", "begin implementation", "work on issue", or "implement feature".

snyk Skill

Create structured implementation plans for Jira issues using the project template. Use when starting a new task, implementing a feature, when asked to create a plan, or when the implementation skill detects no existing plan.

superclaude-org Skill

Project management with PDCA cycles, confidence checks, and context persistence. Auto-activates at session start to restore context. Use for task planning, progress tracking, and structured development.

akash-network Skill

Bootstrap context by reading the project's DESIGN.md and SPEC.md before starting any task

edward4226 Skill

Use this skill when the user gives a long, multi-step, or open-ended task without specifying how completion will be verified. It produces a goal card with an explicit oracle (test command, measurable criterion, or diff against baseline) and runs the oracle at the end to decide "done" objectively.

edward4226 Skill

Use this skill when the user wants persistent, cross-session, reviewable memory for an ongoing project, set of people, or domain knowledge. It initializes a versioned file vault (TODO.md + people/ + projects/ + notes/), defines maintenance rules so memory stays current at natural beats, and treats the vault's git diff as the periodic memory-review surface.

edward4226 Skill

Use this skill when the user wants periodic, lightweight monitoring of a source (an inbox, dashboard, repository, or feed) and conditional action when a defined trigger fires. It produces a heartbeat task configuration with explicit cadence, source, trigger, and action, and defaults the action to draft-only so the human confirms before anything externally observable happens.

eva813 Bundle

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

hahaknight Skill

Meeting minutes generator (会议纪要生成器). 从口述要点或速记直接产出可发群的结构化会议纪要：结论先行、行动项带负责人和日期。当用户说"整理会议纪要"、"刚开完会帮我记一下"时使用。（数字员工配置包免费样例；完整版 6 岗位技能+自动防护+3套SOP 仅 ¥19.9，购买/免费评审拷贝见 github.com/Hahaknight/digital-employee-pack）

helloworldu Skill

Mandatory alignment gate before modifying code, files, or configuration — restate the requirement, surface assumptions, enumerate scenarios with expected outcomes, then STOP and wait for explicit user approval before writing any implementation code. Use at the start of any task that involves changing code, files, or configuration in a repository, especially multi-file or multi-step changes. Skip the gate only for pure Q&A, pure explanation, or tiny changes where the user explicitly said "just do it" — the implementation invariants still always apply. For vague greenfield ideas that are not yet concrete tasks, use idea-to-spec first; for triaging issues in unfamiliar codebases, use progressive-abstraction.

helloworldu Skill

Turn a vague idea into a concrete, actionable spec through structured dialogue — disambiguating requirements, surfacing decision points, and probing technical feasibility before any code is written. Use when the user brings an open-ended or half-formed idea ("I want to build...", "what if we...", "help me create...") and the shape of the thing is not yet clear. Converges into an approved spec, after which concrete modification tasks should go through task-intake, and unfamiliar-codebase investigation through progressive-abstraction. Do not write code inside this skill — producing the aligned spec and getting it approved is the entire deliverable.

helloworldu Skill

Three-layer issue triage methodology for unfamiliar codebases — never dive into implementation details before judging the fix at the architecture layer. Layer 1 identifies the owning layer and classifies the problem (correctness vs completeness vs product decision), Layer 2 traces the real data flow with verified file:line evidence and surfaces boundary semantics, Layer 3 proposes bounded solutions that declare what they deliberately do not do. Use when analyzing or triaging an issue/bug in an unfamiliar repository, deciding where a fix belongs before writing code, preparing an OSS contribution (issue comment / PR) that must survive maintainer review, or evaluating third-party and AI-generated review opinions against code evidence. For vague greenfield ideas use idea-to-spec first; for concrete modification tasks in a familiar repo use task-intake instead.

huangleyang125207 Bundle

Co-author doctrine for shared, half-hour-block daily schedules. Make sure to consult this skill whenever working in a dated daily log, journal, retro, or coordination file shared with a coworker — even if the user only says "log this at 11:00" or "what did we say last Tuesday." Default behavior of dumping procedural details, paraphrasing voice into corporate prose, or fragmenting one task across multiple cells must defer to this skill — entries distill to result + significance, and a cell is removed only when its time falls inside a verified-active task's span (never pre-merged on guess). TRIGGER when: user is in a file matching `daily/`, `journal/`, `schedule/`, `半小时复盘/`, or any file with H1 time-block headers like `# 7：30` or `# 09:00`; user says "create today's", "创建 今天的", "log at N o'clock", "补到 N 点那格", "morning brief", "晨会复盘", "what did we decide on X day"; user dictates an event with time anchor ("just now", "刚才", "yesterday", "上周三", explicit clock); user asks to reconstruct a past session; user referen

kelonwai Skill

Use when writing, editing, or reviewing a SKILL.md — before drafting the frontmatter description, or when an existing skill fails to auto-trigger at the right moment, gets ignored or rationalized away by agents mid-task, fires on trivial work, or reads like a feature announcement. Also use when extracting a skill from a pattern admired in someone else's repo.

kimyx0207 Skill

Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via SessionStart hook.

manzanita-research Bundle

Comprehensive artist name availability checker with parallel search agents that scan Spotify, Apple Music, Bandcamp, SoundCloud, Tidal, Subvert, YouTube Music, TikTok, Discogs, and MusicBrainz simultaneously. ALWAYS use this skill when a musician asks about a name — whether they say "is this name taken", "can I use this name", "check this band name", "would X be a good artist name", "any conflicts with this name", or anything about name availability, name conflicts, or choosing an artist/band/stage/project name. This skill has specialized subagents and a structured analysis workflow that produces much better results than ad-hoc searching. Use it even for indirect requests like "I'm thinking of calling my project X" or "we need a name for our band, what about X" — if there's a specific name mentioned and the user wants to know if it's safe to use, this skill applies.

martin-kocev Bundle

Use when making code or versioning changes in a repository that uses master and develop branches, including features, non-urgent bug fixes, production hotfixes, releases, or semver bumps.

maxmedawar Skill

Engineering discipline for development work orchestrated through Tandem, regardless of whether the worker is Claude, Codex, or another supported engine. Trigger for implementation, debugging, review, test, or architecture work. Begin the first response with 📋📋📋📋📋 when active.

mfrostbutter Bundle

Crystallize a captured workflow journal into a validated Claude skill. Use this whenever the user says "turn this into a skill", "make this repeatable", "build a skill from this", or when a workflow-capture worklog is ready to become a skill. Also use to improve or extend an existing produced skill from a new worklog.

4xiaxia Bundle

Use when the user wants one stable entrypoint for conversation continuity, last-window baton summaries, memory retrieval, or packaging scattered memory/context/cache skills into a single reusable workflow.

nazmussayad Skill

Installs, upgrades, and removes Node.js/npm dependencies, runs scripts, executes packages, and manages package workflows. MUST USE for any task involving npm, npx, pnpm, yarn, or bun, including package.json dependency changes, lockfile updates, install/update/uninstall actions, and script execution.

sube-py Bundle

Determine whether today (or a given date) is a working day in mainland China by querying holiday-cn yearly JSON from jsDelivr and applying holiday/makeup-workday rules. Use when users ask questions like "今天是不是工作日", "这天要不要上班", "是不是节假日/调休补班", or when a workflow needs a reliable workday boolean.

virajmishra1 Skill

A focused local development workflow skill

alexcassol Bundle

Applies the manual stack-trace pattern for Visual Basic 6 based on EnterMethod/ExitMethod calls that push and pop method names from a module-level array. This pattern compensates for the absence of a native call stack in VB6, enabling rich production logs with call depth, parameter serialization, and on-demand stack inspection in error handlers. Covers when to instrument procedures (every non-trivial function), placement rules (EnterMethod in EhHeader, ExitMethod in both success and error paths), optional parameter serialization, the TraceMethod function for inserting the current stack into error messages, log file management (rolling daily logs with retention), activation gating (only logs when explicitly enabled or running in the IDE), and automatic process dumping via WMI when automation errors are detected. Activates whenever working with EnterMethod, ExitMethod, LogMsg, TraceMethod, manual stack trace, or any VB6 task involving production diagnostics, error logging, debugging, or fault investigation.

assistant-ui Skill

Update dependencies across the assistant-ui monorepo (npm via pnpm + taze, Expo SDK-pinned packages, Python packages via uv, and GitHub Actions). Use when the user asks to bump, upgrade, or update dependencies (root, packages, examples, templates, python/*, .github/workflows/*), refresh the pnpm lockfile or uv.lock files, repin GitHub Actions, or run the dependency-update workflow before a release.

davideast Bundle

Enforces a disciplined Red-Green-Refactor (TDD) workflow in TypeScript with Vitest. Use when creating new features, fixing bugs, or migrating logic to ensure high-quality, verifiable implementations. Pairs with the typed-service-contract skill.

dmccreary Bundle

This skill generates Python scripts and shell scripts to control RGB LEDs on the Raspberry Pi 500+ keyboard. Use this skill when the user asks to create keyboard lighting effects, animations, color patterns, notification systems, or any program that controls the Pi 500+ keyboard LEDs. This skill should be used for requests like "turn F1-F12 keys blue", "create a typing speed indicator", or "make an email notification effect".

elliothux Bundle

Delegate a concrete, locally authorized implementation task from Codex as planner and reviewer to the official Grok Build CLI as executor. Use when the user explicitly asks Codex to have Grok, SuperGrok, or Grok CLI implement, fix, test, or modify code, or asks for a Codex-planner/Grok-executor workflow. Do not trigger for ordinary coding tasks that do not request Grok, or for external commits, pushes, deployments, publication, or production mutations.