user-interview
Requirements elicitation through structured interviewing. Use when: (1) User provides vague, ambiguous, or incomplete requirements, (2) Clarification is needed before building features or writing code, (3) User says 'build X' without specifying behavior, edge cases, or constraints, (4) Translating stakeholder requests into PRDs, specs, or user stories. Triggers on phrases like 'make it better', 'add a feature', 'fix this', 'I need something that...', or any request lacking concrete acceptance criteria.
workflow-create-plan
This skill should be used when generating a detailed implementation plan from an existing PRD and codebase research. It synthesizes requirements with codebase context into actionable, bite-sized TDD tasks suitable for junior developers.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
opentui
Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.
commit-work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
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).
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
agent-md-refactor
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
mr-tracker
Tracks and monitors GitLab merge request activity including comments, status, and real-time updates
obsidian-daily-note
Manage daily notes in Obsidian vault with consistent structure
obsidian-vault
Manage and navigate Obsidian vault with consistent structure, naming conventions, and linking patterns
opencode-command
Use this skill when creating, modifying, or understanding OpenCode commands stored in `~/.config/opencode/command/`.
opencode-plugin-builder
This skill should be used when creating, modifying, or debugging OpenCode plugins. It provides the complete plugin architecture, available hooks, event types, SDK client methods, and best practices learned from real-world plugin development.
humanizer
|
orchestrator-protocol
Shared orchestrator behavior for delegation-first agents. All specialized agents must follow this protocol when delegating work.
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
professional-communication
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.
remotion-best-practices
Best practices for Remotion - Video creation in React
ship-learn-next
Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
communication-style-preservation
|
dagster-local
Interact with Dagster data orchestration platform running locally or on Kubernetes. Use when Claude needs to monitor Dagster runs, get run logs, list assets/jobs, materialize assets, launch jobs, or debug pipeline failures. Supports both local Dagster dev server and Kubernetes deployments where each job run is a separate pod.
daily-wrapup
Automate daily note wrapup workflow. Interview for next episode, extract learning ideas, create concept notes. Use when daily wrapup, end of day or wrapup is mentioned by user.
duckdb-data-explorer
This skill should be used when performing local data exploration, profiling, quality analysis, or transformation tasks using DuckDB. It handles CSV, Parquet, and JSON files, provides automated data quality reports, supports complex JSON transformations, and generates interactive HTML reports for data analysis.
jira-ticket-creator
This skill should be used when users need to create Jira tickets for the RD (Research & Development) project. It supports creating features, bugs, and tasks with proper field mapping including assignee, team, sprint, and state. The skill uses Jira CLI commands and provides templates for different ticket types.
jira-ticket-fetcher
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sprint but can extend to all tickets when needed. The skill uses the Jira CLI to retrieve ticket details, status, assignee, and descriptions.
mr-generator
Generates intelligent GitLab merge request descriptions from git commits with automatic categorization and Jira integration
pyenv-activation
Guide for activating pyenv virtual environments with troubleshooting for common issues
python-dev-guidelines
Python conventions, patterns, and workflows. Use when writing code, reviewing PRs, or setting up new Python projects.
python-testing-guidelines
This skill should be used when writing or reviewing Python tests. It enforces a dummy-class pattern over unittest.mock, requiring all test dependencies to use explicit dummy classes instead of Mock, MagicMock, AsyncMock, or patch().
systematic-debugging
This skill should be used when encountering any bug, test failure, or unexpected behavior. It requires finding root cause before proposing fixes. Random fixes waste time and create new bugs.
systematic-thinking
Rigorous problem decomposition and evidence-based analysis methodology for software engineering tasks. Use to analyze situations, figure out concepts or investigations.
cortex
CLI for managing the Cortex email automation pipeline. Use this skill when the user wants to query emails, check queue status, trigger backfills, view classifications, or manage the email triage system. Triggers on keywords like "cortex", "email pipeline", "queue status", "classification", "backfill", "triage".
firecrawl-web
Fetch web content, take screenshots, extract structured data, search the web, and crawl documentation sites. Use when the user needs current web information, asks to scrape a URL, wants a screenshot, needs to extract specific data from a page, or wants to learn about a framework or library.
content-filter
Filter and classify AI research content for relevance. Use when processing raw content from Twitter, Substacks, blogs, or podcasts to determine if it's worth extracting claims from. Assigns relevance scores, topics, and author categories.
lecture-notes
Generate comprehensive undergraduate lecture notes for social sciences (especially economics) with mathematical foundations, daily-life examples, and practice questions. Use when user asks to create, generate, or write lecture notes, lecture materials, or teaching content. Supports Turkish and English output, Obsidian-compatible markdown with LaTeX/TikZ, and optional syllabus integration.
gmacko-dev-feature-plan
Use when (1) breaking down a feature request into implementable tasks, (2) creating a detailed feature specification, (3) preparing work for development. Generates feature plans with acceptance criteria and task breakdown.
gmacko-dev-issue-create
Use when (1) creating GitHub issues from feature plans or bug reports, (2) documenting bugs found during development, (3) managing the project backlog. Creates well-structured GitHub issues with templates and labels.
gmacko-dev-pr-review
Use when (1) reviewing a pull request against coding standards, (2) verifying PR meets acceptance criteria from feature plan, (3) checking for common issues before merge. Reviews PRs against plan and project standards.
gmacko-init-bootstrap
Use when (1) PROJECT_MANIFEST.json and INITIAL_PLAN.md exist, (2) ready to execute setup.sh to initialize the project, (3) renaming template to project name. Wraps setup.sh with preflight checks and validation.
gmacko-init-interview
Use when (1) starting a new project from the gmacko template, (2) user wants to create a fresh app without git history, (3) gathering requirements for PROJECT_MANIFEST.json. Conducts a guided interview to capture project goals, platforms, integrations, data model, and deployment preferences.
gmacko-init-orchestrator
Use when (1) user wants a complete project setup from scratch, (2) one-command initialization of a new Gmacko Ventures project, (3) orchestrating the full init workflow. Coordinates interview, plan, bootstrap, and provision skills.
gmacko-init-plan
Use when (1) PROJECT_MANIFEST.json exists and you need to generate INITIAL_PLAN.md, (2) user wants a detailed implementation roadmap, (3) translating manifest into actionable milestones. Generates comprehensive project plan from the manifest.
gmacko-qa-verify
Use when (1) verifying a feature is complete against acceptance criteria, (2) running QA checklist before release, (3) validating PR changes meet requirements. Performs systematic QA verification with documented results.
gmacko-release-close
Use when (1) release is deployed and verified, (2) closing related issues and PRs, (3) creating GitHub release with changelog, (4) finalizing release documentation. Completes the release lifecycle.
gmacko-release-deploy-mobile
Use when (1) building mobile app via EAS for distribution, (2) submitting to App Store or Google Play, (3) managing mobile release workflow. Handles Expo EAS build and submission process.
gmacko-release-deploy-web
Use when (1) deploying web application to Vercel staging or production, (2) monitoring deployment progress, (3) running post-deployment verification. Manages Vercel deployment workflow with safety checks.
gmacko-release-prepare
Use when (1) preparing a release for staging or production, (2) generating release notes and changelog, (3) verifying environment readiness before deployment. Prepares all artifacts needed for a release.
ai-creative-strategist
Research-powered creative strategy with visual previews. Use when you need to figure out WHAT to create before creating it. Researches competitors, captures references, generates visual direction previews, and outputs comprehensive briefs. Triggers on: creative strategy, what visuals should I create, creative brief, visual direction. Outputs briefs with actual preview images for feedback.
Page 1238 of 1665 · 83227 results