jira-cli
Interactive command-line tool for Atlassian Jira. This skill should be used when users want to interact with Jira issues, epics, sprints, or when they mention Jira workflows, issue management, or need help with jira-cli commands and workflows.
invoicing
Interact with the Eenvoudig Factureren API to manage clients, invoices, quotes, orders, and more. Use me when dealing with invoicing, clients, quotes, orders, deliveries, receipts, payments, stock items, or subscriptions.
shell-scripting
Guide for writing robust shell scripts following best practices to use bash with proper options, quote variables, use modern syntax, include debugging support, and provide help.
opencode-authoring
|
MudNeatoo
This skill should be used when writing or modifying .razor files that bind to Neatoo entities, when using MudBlazor components with Neatoo domain models, when the user mentions "MudNeatooTextField", "MudNeatooSelect", "MudNeatooDatePicker", "MudNeatooNumericField", "MudNeatooCheckBox", "NeatooValidationSummary", "EntityProperty", "@bind-Value with Neatoo", "form binding", "Blazor form", "LazyLoad databinding", "LazyLoad in Razor", "LazyLoad Blazor pattern", "lazy load spinner", or asks to build a form, page, or dialog that edits a Neatoo entity. Also triggers when reviewing .razor files for correct Neatoo integration patterns, including LazyLoad rendering. Assumes the Neatoo skill is also loaded for domain model concepts.
project-todos
RETIRED. Do not use. The iterative-todo skill replaces this entirely. If a user mentions "project-todos", redirect them to /iterative-todo. This skill folder will be deleted once the runtime releases the lock.
Neatoo
This skill should be used when working with Neatoo domain models, ValidateBase, EntityBase, ValidateListBase, EntityListBase, partial properties, property change tracking, validation rules, business rules, aggregate roots, entities, value objects, lazy loading, EntityLazyLoad, IEntityLazyLoadFactory, or any .NET DDD domain model framework work. Also triggers for IsValid, IsSelfValid, IsSavable, IsModified, IsNew, IsDeleted, RuleManager, AddActionAsync, AddValidationAsync, AddAction, AddValidation, IsBusy, WaitForTasks, IsLoaded, IsLoading, and base class behavior. This skill also provides guidance on where business logic belongs -- computed properties, conditional visibility, reactive behavior, and validation should live in the domain model (not the UI). Consult this skill when writing .razor files that bind to Neatoo entities to ensure logic stays in the domain layer. Neatoo is the domain model framework -- it does NOT include factory generation. For factory attributes ([Factory], [Create], [Fetch], [Remote], [Service], [AuthorizeFactory]) see the RemoteFactory skill, which is independent and works with any .NET class.
knockoff
>-
iterative-todo
This skill should be used when the user asks to "create a todo", "create an iterative todo", "iterate on this", "start a small plan", "plan this work", "design this feature", "abandon this plan", "next plan in <todo>", "log a discovery", "resume the todo", or "run the close-out audit". Use for multi-session, design-heavy work where the plan needs to outlive the conversation — bounded or exploratory. Plans are small working hypotheses; the todo is the durable container with a Discovery Log and Plan Index. Skip for single-session tasks, trivial fixes, or work that fits in built-in plan mode (Shift+Tab).
AllRecursiveReposClean
Check if all git repositories in subdirectories are fully committed to main/master with no pending changes or worktrees.
RemoteFactory
|
design-audit
Use when reviewing frontend design quality without a reference. Identifies UX issues, accessibility problems, and visual inconsistencies with actionable fix suggestions.
design-compare
Use when comparing a frontend implementation against a reference design (Figma, mockup, screenshot). Performs pixel-level and structural analysis to identify discrepancies.
design-report
Use when conducting comprehensive design review before launch, for stakeholder presentation, or when user requests expert-level design analysis. Produces detailed report from senior Apple product designer perspective.
frontend-styleguide
Use when asked to create or edit style guides, design systems, component libraries, or update existing frontend components for web projects
test-execution-manager
Use when running tests via test-runner subagents - delegates test execution to background agents with incremental timeout escalation
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
plone-frontend-developer
Senior Plone Volto frontend engineering for debugging Volto add-ons, fixing UI bugs, adjusting blocks/components, and handling all Plone 6.1 + Volto 17/18 frontend tasks (theme, routing, tokens, build/test issues). Use when the request involves Volto/Plone frontend behavior, add-on code, or UI fixes.
volto-cypress-writer
Cypress E2E writing and maintenance for Plone Volto add-ons under frontend/src/addons, including UI-first setup, selectors, helpers, flake reduction, and add-on Cypress commands.
plone-backend-developer
Senior Plone backend development for the EEA website. Use when working on Plone 6.1 server behavior, backend add-ons, Python code, configuration in `backend/develop/`, or when debugging backend bugs and tests.
handoff
Compact the current conversation into a handoff document for another agent to pick up.
caveman
>
digest
Extract insights from transcripts into actionable artifact files.
inspector-signoff
Mandatory final handoff procedure for Inspector (public output + inspector_result.json + validation).
greeter
I greet politely.
builder-checklist
Builder implementation checklist used to drive todowrite and execution order.
inspector-checklist
Inspector review checklist used to drive todowrite and review order.
builder-signoff
Mandatory sign-off procedure for Builder (public output + builder_result.json + validation).
n8n
Dashboard-first journey guidance for n8n. Use when a user connected n8n and wants a Workflow Activity Dashboard (default) with auto-mapping and live preview, and optionally to turn a workflow into a product.
data-dashboard-intelligence
Universal intelligence for turning normalized event data into premium, story-driven dashboards. Covers field-to-component mapping, aggregation selection, dashboard story structure, hero stat detection, and graceful degradation. Use this skill whenever generating a dashboard spec, editing dashboard components, choosing chart types, deciding aggregation methods, handling empty or sparse data, writing component headlines, ordering components on a dashboard, or picking which metric should be the hero stat. Even if the user doesn't say "dashboard intelligence", use this skill for ANY dashboard generation or editing task.
retell
Mapping guidance for Retell AI voice agent events. Covers call metrics, agent performance, disconnect reasons, and conversation analytics.
make
Mapping guidance for Make.com (Integromat) scenario events. Covers execution metrics, scenario performance, operation counts, and module analytics.
business-outcomes-advisor
Skeleton-intelligent revenue strategy for AI automation agencies. Frames proposals through monetization lenses across all UI types — dashboards, product pages, and admin panels. Knows the full skeleton catalog, SaaS wrapper productization flow, and enrichment boundaries. Active in propose phase only. Max 1-2 questions, plain language, agency-native vocabulary.
vapi
Mapping guidance for Vapi voice AI events. Covers call metrics, assistant performance, cost tracking, and transcript handling. Use for any Vapi-connected dashboard generation or editing task.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
todo
Planning and progress tracking skill for agent's internal reasoning. Use when an agent needs to create, track, and complete tasks across its own multi-step operations and maintain state persistence.
git-master
MUST USE for ANY git operations. Atomic commits, rebase/squash, history search (blame, bisect, log -S). STRONGLY RECOMMENDED: Use with sisyphus_task(category='quick', skills=['git-master'], ...) to save context. Triggers: 'commit', 'rebase', 'squash', 'who wrote', 'when was X added', 'find the commit that'.
frontend-ui-ux
Designer-turned-developer who crafts stunning UI/UX even without design mockups
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
next-best-practices
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
humanize-as-kevin-xiao
|
linear-issues
Manage Linear issues - list, create, update, start/stop work, assign, comment, set priority/labels. Use when working with Linear issues, viewing tasks, creating bugs, updating issue status, adding comments, or changing assignments.
linear-fix
Autonomously completes Linear tickets via git worktrees. Use when user says "fix ENG-123", "complete LIN-456", "work on linear ticket", provides a linear.app URL, or mentions a ticket ID pattern like ABC-1234. Creates git worktree, implements fix via autonomous planning/review loop, opens GitHub PR with full reasoning.
linear-search
Search Linear issues and projects by text. Use when finding issues, looking up bugs, searching the backlog, querying "what tickets mention X", or finding issues by keyword like "find ENG-" or "search for login bug".
completion-check
Run a completion checklist over the current change set when work is considered done and ready to commit. Checks for correctness, simplification candidates, comment and prose audits, and repository-specific checks. Use before marking a task complete, e.g. before committing or pushing to open a PR, or when the user says "commit for me", "open a PR", "are we done".
Page 1549 of 1700 · 84990 results
