youtube-rl-tracker
Track YouTube video performance for "poor man's reinforcement learning" - learn what thumbnails, titles, and hooks work
company-admin
Access and update company administrative information stored in Notion
ben-agent-email
Canonical Resend inbox for ben-agent@zerofinance.ai
aws-ses-inbound
Set up AWS SES for receiving inbound emails with SNS webhook delivery
video-subtitle-cutter
Transcribe video, analyze subtitles with AI, and cut video by removing filler words, pauses, and mistakes
vercel-dns
Manage DNS records for domains hosted on Vercel using the Vercel CLI
tweet-rl-tracker
Create and manage a Notion-based tweet performance tracking system for "poor man's reinforcement learning"
testability
Make features testable by design. Testing pyramid from fast (local) to slow (UI). Expose APIs securely for testing.
0-finance-cli
Keep the 0 Finance CLI aligned with product capabilities.
design-motion-principles
Expert motion and interaction design auditor based on Emil Kowalski, Jakub Krehel, and Jhey Tompkins' techniques. Use when reviewing UI animations, transitions, hover states, or any motion design work. Provides per-designer perspectives with context-aware weighting.
wp-performance-review
WordPress performance code review and optimization analysis. Use when reviewing WordPress PHP code for performance issues, auditing themes/plugins for scalability, optimizing WP_Query, analyzing caching strategies, checking code before launch, or detecting anti-patterns, or when user mentions "performance review", "optimization audit", "slow WordPress", "slow queries", "high-traffic", "scale WordPress", "code review", "timeout", "500 error", "out of memory", or "site won't load". Detects anti-patterns in database queries, hooks, object caching, AJAX, and template loading.
maestro-card
Card work in a project using Maestro after design approval: use for implement, fix, verify, QA, close, release, continue, or unattended prompts like use loop, keep looping, work while away/asleep.
cli-for-agents
>-
prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Amp, Claude Code, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
mcp-for-agents
>-
maestro-witness
Witness feature close: use after Maestro feature proof and QA pass, before feature close, to write current witness.md/advisor.md receipts, auto-invoke an independent advisor when allowed, apply risk-tier and human-demo policy, and emit Gate: APPROVED.
maestro-setup
Setup Maestro in a project using or adopting Maestro: use for init/install/sync/doctor, global skills, hooks, harness setup, or agent integration diagnosis/repair.
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"
docs
>-
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\"
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\"
maestro-design
Design in a project using Maestro before implementation: use for brainstorm, plan, PRD synthesis, grilling/stress-test, domain model, deepening candidate, wording, workflow, skill/harness, card/task/feature, architecture, UX, or agent-process decisions.
maestro-research
Pre-design research for Maestro cards: creates or validates a same-card research.md receipt, maps context, stakeholders, hosting, unknowns, and the first design fork. Use before maestro-design when the user brings a new idea, zero-context feature, external/pasted plan, unfamiliar domain, stakeholder-heavy request, hosting-unclear work, or when research is missing, stale, skipped-risky, or needed for READY_FOR_DESIGN.
maestro-audit
Audit a project using Maestro read-only: use for code review, architecture review, deepening opportunities, backlog proposals, harness-improvement findings, or repo-wide improvement audits without fixes.
ask-maestro
Router for choosing the next Maestro skill or lifecycle recipe.
grafana-logs
>
weekly-report
Use when the user asks for a weekly report, activity summary, or wants to review what was done in a GitHub org over a time period — searches issues and PRs, filters by author, groups by repo, and formats for Slack
golangci-lint
When linting is failing.
git-commit
>-
gh-pr
>-
neovim
Interact with the user's running Neovim instance via RPC. Use this skill when you need to execute Lua or Vimscript inside Neovim, query buffer state, send commands, or interact with the Neovim runtime in any way. Triggers when the user asks about their current Neovim session, wants to run something inside Neovim, or when you need to inspect Neovim state (buffers, windows, options, LSP, etc.). Also use when running inside a Neovim terminal and needing to communicate with the parent editor.
gh-cli
GitHub CLI (gh) command reference. Use when working with GitHub repositories, PRs, issues, actions, `gh api`, or any GitHub operations from the command line.
aip
Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
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.
svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
svelte-core-bestpractices
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
git-commit-guide
Git 提交规范（Conventional Commits）
api-design
RESTful API design best practices and conventions guide
code-quality-suite
代码质量综合技能包（代码审查 + 单元测试）
unit-testing
Java单元测试编写指南（基于JUnit和Mockito）
weather
Get current weather and forecasts (no API key required).
database-design
数据库设计规范与优化指南
java-best-practices
Java 编码最佳实践与设计模式
code-review
代码审查最佳实践指南
use-railway
>
testing-orcaq
>
Page 516 of 1725 · 86239 results
