Productivity

rodri-oliveira-dev Skill

Author and review GitHub Actions workflow YAML safely, especially expression quoting and structural validation. Use for files under .github/workflows and workflow-load failures where no jobs start. Do not use for unrelated application YAML.

ix-infrastructure Skill

Route to the right Ix skill or tool for the current task. Route only; do not perform the task.

rcarmo Skill

workflow patterns for planning, subagents, self-improvement, and verification

thecraighewitt Skill

Produces a one-page brief before a meeting — who's attending, what's been discussed before, what to expect, what to ask. Pulls from calendar, email threads with the attendees, any prior meeting notes, and project context. Use when the user asks to prep for a meeting, get ready for a call, or brief me on an upcoming meeting.

srid Bundle

Do a task end-to-end — implement, PR, CI loop, ship

ory Skill

Set up a complete authentication system using Ory Network with Ory Elements as the UI layer. Use whenever the user wants to add login, registration, account recovery, email verification, account settings, or session management to a web app — even if they only mention "auth", "sign-in", or "users". Ory Elements is the default UI; only fall back to custom rendering when Ory Elements cannot be used.

packmindhub Bundle

Use when updating, adding, fixing, changing, or deprecating Packmind playbook artifacts (standards, commands, skills). Triggers on explicit phrases like "update packmind standard", "add a packmind skill", "fix packmind command", "change packmind playbook", "deprecate a standard". Also triggers when the conversation reveals an opportunity to update the playbook — e.g., a convention was established, a pattern emerged, a workflow changed, or an artifact is stale. This skill defines a mandatory workflow: do NOT edit artifact files directly — follow all phases (0→4) regardless of change size. Supports non-interactive mode via `CI=true` or `--non-interactive` for automated playbook updates from PR review findings.

zaxbyhub Skill

Apply when committing, pushing, opening a PR, writing a pull request, creating release notes, or updating a changelog. Enforces conventional commit format, mandatory release notes, 5-tier test suite, SHA-pinning for workflow changes, and correct PR body format.

0xlayerghost Skill

[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review.

0xlayerghost Skill

[AUTO-INVOKE] MUST be invoked when debugging failed on-chain transactions. Covers transaction receipt analysis, gas diagnosis, calldata decoding, revert reason extraction, and state verification. Trigger: any task involving failed tx analysis, revert debugging, or on-chain transaction troubleshooting.

0xlayerghost Skill

[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.

0xlayerghost Skill

[AUTO-INVOKE] MUST be invoked at the START of each new coding session. Covers context management, task strategies, and Foundry-specific workflows. Trigger: beginning of any new conversation or coding session in a Solidity/Foundry project.

objectivlabs Skill

Evidence-grounded to-be design (ADRs + design doc) and an implementation orchestration plan (a machine-readable task ledger). Activates when the user asks to design a target state, plan the work, or produce a task plan for a goal.

open-horizon-labs Skill

Create GitHub issues from task descriptions or session context. Investigates when needed, skips when context exists.

aws-samples Bundle

AI-DLC workflow orchestrator. Reads manifest state, dispatches to phase skills, manages rollback and status. Executes phases by loading and following each skill's SKILL.md.

elsa-workflows Skill

Execute the implementation planning workflow using the plan template to generate design artifacts.

dyoshikawa Skill

Release a new ghactivities version end to end by drafting the release, waiting for green CI, merging the release PR, publishing the GitHub release, and verifying the npm release workflow. Use when asked to complete, finish, or publish a release through the goal-release workflow.

a5c-ai Skill

Orchestrate a babysitter run. use this command to start babysitting a complex workflow in a non-interactive mode, without any user interaction or breakpoints in the run.

bex-co Bundle

Safely bring main up to date, commit intended pending changes, and push to origin/main. Use when the user explicitly asks to ship the current main branch or invokes the repository's ship workflow.

cwijayasundara Skill

Standard GitHub issue workflow. Branch, reproduce, fix, test, PR.

dansnow Skill

Systematically debug a problem using a four-phase workflow

ipea Skill

Stage, commit, push, open a PR, and merge to main. Use ONLY on explicit commit intent — user says "commit", "ship it", "push this", "open a PR", "merge to main", "let's commit this", or prefixes with `/commit`. Do NOT auto-invoke on vague end-of-task phrases ("we're done", "wrap up") — those require explicit confirmation first. Runs the standard commit-PR-merge cycle; never force-pushes or skips hooks.

dojogenesis Skill

Context Ingestion Workflow

qodo-ai Bundle

Understand how code works, how a change was done before, and which repos are coupled — to answer a question, plan a code change, debug a regression, or scope a fix, using the qodo CLI's managed tools. Use when a task needs to understand a codebase, its history, or how its repos relate — especially for a repo you don't have checked out or work spanning repos — "how does X work", "where is X defined", "who changed X", "explain this service", "plan the change for X", "what would changing X affect", "which repos depend on X", "why did X regress / when did it break", "has this been fixed before", "how did we solve X".

qodo-ai Bundle

Load the coding rules from Qodo most relevant to the current coding task, using the qodo CLI's managed rules search — generate structured semantic queries from the assignment, retrieve the workspace's matching rules ranked by relevance, and apply them while writing the code. Use when the user asks to write, edit, refactor, or review code, when starting implementation planning, or on "get rules", "load qodo rules", "fetch coding rules", "relevant rules", "search rules"; skip if rules are already loaded in this conversation.

haowjy Skill

Dispatch reference for composing writing teams. Teaches which skills to load for each subagent, which resources to reference, and when to fan out versus run parallel lanes. Load when staffing a workflow.

civitai Bundle

Interact with ClickUp tasks - get task details, view comments, create and manage tasks. Use when working with ClickUp task URLs or IDs.

fandhe-ai-agent-reference-skil Bundle

親イシュー配下のサブイシュー（孫含む）を依存順を保ちつつ worktree で並列に自動実装・push 前 review・PR 作成・CI 監視・マージ可能状態化まで一括自動化。 「イシューツリーを並列実装」「配下のサブイシューをまとめて実装」「ツリー全体を並列で実装して」「イシュー階層を自動開発」で使用。 per-issue 計画立案（Plan: セッション継承モデル）→実装（Implement: sonnet）の分業。push 前 review（Review 通過後にのみ push・PR 作成して CI を 1 回だけ起動）。 外部チェック構成は args の externalChecks で明示（{"app", "context"} の組で宣言。[] で「なし」を確定して不要待機なし・未指定なら自動マージ停止・slug のみの旧形式は自動マージ fail-closed）。 自動 squash merge は autoMerge: true + externalChecks 明示（全 App の信頼済み context 宣言込み）の opt-in で実行（merge-exec の自己取得再検証 + サーバー側 branch protection 実測が前提。既定 false はマージ可能状態で停止し人間がマージ。サーバー側 workflow サンプル（upstream の docs/implement-issue-tree/auto-merge-sample.yml 参照）+ branch protection への委譲も可）。並列度（parallel）と依存（dependsOn）で実行順を制御。 単一イシューの実装は implement-issue、PR レビューは implement-review-pr を参照。

malue-ai Skill

Create new skills and improve existing skills. Use when users want to create a skill from scratch, capture a workflow as a skill, update or optimize an existing skill, improve a skill's description for better triggering accuracy, or ask anything about how skills work in this system.

google Bundle

Aligns a Python recipe's pyproject.toml with the repo's standards enforced by .github/workflows/python-validate-recipe.yml, plus one critical [build-system] presence check. Scope is pyproject.toml only — standalone ruff.toml / .ruff.toml files (also forbidden in recipes) are caught by the CI workflow instead, not by this skill. Runs in two modes: a read-only --dry-run that reports what needs alignment, and an apply mode that rewrites pyproject.toml (and optionally manifest.yaml) using comment-preserving TOML/YAML editors. Use when the user wants to "align the recipe's pyproject.toml", "fix pyproject to match the repo standard", "check what needs changing in a recipe's pyproject", or clean up a recipe before submitting a PR.

dmitryprg-ai Skill

Test-Driven Development workflow with strict Red-Green-Refactor cycle. Use when developing features with TDD, writing tests before code, or when test-driven approach is needed. MANDATORY order - test cases table BEFORE code, failing tests BEFORE implementation.

zipperbagcoffee Bundle

Record directly-performed work in a Crabshell H hotfix document. Use for any task done in one pass that does not need a D/P/T workflow.

zipperbagcoffee Bundle

Create a Crabshell P plan document from Codex. Use when a task needs an implementation plan before tickets.

zipperbagcoffee Bundle

Run a Codex-compatible D/P/T iterative improvement workflow. Use when the task needs repeated plan-execute-verify cycles rather than a one-shot worklog.

mcouthon Skill

Review implementation plans from the .tasks/ directory for flaws before committing — either a single phase (phase mode) or across all phases of a task for consistency (cross-phase analyze mode). Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase', 'validate phase', 'review phase N', 'check the plan for phase', 'analyze phases', 'cross-phase review', 'check consistency across phases', 'analyze the task plan'.

ahmedkhaledmohamed Skill

Meeting preparation assistant for Product Managers. Use when the user needs to prepare for a meeting, create talking points, anticipate questions, or structure a discussion. Triggers include "prepare for meeting", "meeting prep", "talking points", "get ready for", "1:1 prep", or when preparing for any scheduled conversation.