Loading...
Loading...
Found 6,175 Skills
Persist gotchas, preferences, or a repeated workflow from recorded agent history into AGENTS.md or a new skill. Use when the user asks to extract lessons from past sessions or turn prior agent work into a skill.
Conventions for authoring and maintaining GitHub Actions workflows. Pin each action to its latest version, read the Node version from .node-version (else latest LTS), and set up pnpm via the setup-pnpm action instead of corepack. Use when creating a workflow, adding or editing jobs or steps, or updating action versions in an existing workflow.
Coordinate a high-fidelity Figma-to-code workflow for screens, layouts, drawers, dialogs, or component groups. Use when Codex receives one or more Figma URLs or node IDs and must decide how to extract exact design intent, split work into reusable components, route implementation safely, and keep conversion and apply work aligned with the local design system and verification constraints.
Read, search, summarize, and triage AgentMail inboxes through the connected MCP server. Use for ANY request to look at, search, or process mail — even a simple 'search my inbox for X' or 'any new mail?'; the read workflow applies regardless of task size. Also use to summarize conversations, inspect attachments, manage read/unread labels, or find messages needing a reply; do not use for sending or drafting (agentmail-send-email), inbox administration (agentmail-manage-inboxes), or MCP connection setup (agentmail-mcp).
GH Actions workflow triggering/monitoring gotchas for any repo with multiple workflows (e.g. APK + AAB builds). Use when a push to main did not seem to trigger a workflow, when only .github/** changed (paths filters skip it, needs manual dispatch), when parallel runs need one cancelled, when a build failed and the job log must be pulled, or when checking run status/artifacts. For the end-to-end Expo APK/AAB build flow use gh-actions-expo-apk-build instead.
Use when symfony daily workflow
Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.
Claude Code workflow mastery for .NET developers. Covers parallel execution with git worktrees, plan mode strategy, verification loops, auto-formatting hooks, permission setup for dotnet CLI, prompting techniques, subagent patterns, and context discipline — token budget management, MCP-first navigation, lazy loading, and subagent isolation — all adapted for the .NET ecosystem. Load this skill when setting up Claude Code for a .NET project, optimizing workflows, running parallel sessions, when context is running low or sessions feel sluggish, when exploring a large codebase efficiently, or when the user mentions "productivity", "workflow", "parallel", "worktree", "plan mode", "permissions", "hooks", "10x", "setup Claude Code", "speed up development", "context", "tokens", "budget", "running out of context", "too many files", or "large codebase". Inspired by tips from Boris Cherny (creator of Claude Code) and the Anthropic team.
Bootstrap a repo for the strict development workflow: discover issue tracker, triage labels, and docs layout, then write docs/agents/*.
End-to-end Dynatrace alerting lifecycle — anomaly detector setup and model selection (static threshold, adaptive baseline, seasonal baseline), alert event storage in Grail, problem grouping and denoising by root cause analysis, and workflow-based notification routing (email, Slack, ServiceNow, webhook). Use when configuring alerting, choosing between detector types, querying alert event history, understanding why alerts merged into a problem, or setting up problem-triggered notifications.
As a standard S0 pre-skill for larger page workflows like `hiui-page-workflow`, it focuses on requirement refinement for B-end back-office systems and before HiUI page generation. It transforms vague or abstract back-office/management/operation/configuration/approval workflow requirements into executable product solutions, MVP scopes, user flows, business rules, traceable page inventories, product PRDs, global generation contexts, page-level prompts, and HiUI handoff packages. It is suitable for clarifying back-office product ideas, converting rough requirements into PRDs or product solutions, breaking down work surfaces such as lists/details/editing/configuration, defining role permissions/data permissions/state machines/audit rules, and supplementing permission matrices, state transition tables, field dictionaries, exception and audit matrices, batch/import-export specifications, and legacy system transformation and release strategies when needed; it also acts as a B-end product expert to provide judgments including business value decomposition, priority suggestions, solution trade-offs, multi-tenant/version/activation models, master data and system boundaries, anti-pattern identification and risk prompts, continuously turning vague B-end requirements into implementable inputs; when requirements arise in existing projects/repositories, it is also used to perform context-aware requirement refinement combining the current repository's pages, modules, interfaces, types, and documents.
Operational expert tools — used by domain specialists for hours every day — require a different design approach than consumer or occasional-use software. Information density, workflow linearity, and at-a-glance status take priority over whitespace and discoverability. Use when designing dispatch tools, warehouse management, logistics, scheduling, or any B2B tool whose primary users are trained specialists.