Trending Skills
The hottest skills gaining momentum in the community right now.
github-actions-expert
by testacode
Experto en GitHub Actions para CI/CD. Usa cuando el usuario diga "agregar CI", "configurar GitHub Actions", "crear workflow", "workflow de deploy", "automatizar tests", "CI/CD pipeline", "add CI", "setup GitHub Actions", o cuando el proyecto no tenga .github/workflows/.
query
by Barneyjm
"Search for places using natural language with Camino AI's location intelligence API. Returns relevant results with coordinates, distances, and metadata. Use when you need to find real-world locations like restaurants, shops, landmarks, or any point of interest."
hotel-finder
by Barneyjm
"Search for hotels, hostels, and lodging near landmarks, conference venues, or neighborhoods using Camino AI's location intelligence with AI-powered ranking."
route
by Barneyjm
"Get detailed routing between two points with distance, duration, and optional turn-by-turn directions. Use when you need navigation instructions or travel time estimates between locations."
travel-planner
by Barneyjm
"Plan complete day trips, walking tours, and multi-stop itineraries with time budgets using Camino AI's journey planning and route optimization."
places
by Barneyjm
"Locate places using flexible query formats - free-form search or structured address components. Returns coordinates, addresses, and optional street-level photos. Use for geocoding addresses or finding specific named places."
context
by Barneyjm
"Get comprehensive context about a location including nearby places, area description, and optional weather. Use when you need to understand what's around a location or provide location-aware recommendations."
QA
by petestewart
This skill should be used when the user asks to "run QA", "test the changes", "create a test plan", "verify the implementation", "QA the work", "check if it works", or needs to validate that completed work functions as expected. Generates TEST_PLAN.md and orchestrates test execution with bug fixing.
file-todos
by 8b-is
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
orchestrator
by petestewart
Drive a project from PLAN.md to completion by coordinating work, spawning focused subagents, and maintaining plan accuracy. You coordinate, prioritize, verify, and keep the plan accurate—not implementing large tasks yourself.
subagent
by petestewart
Execute a single ticket from PLAN.md with precision. You are a focused implementation agent—receive a ticket, implement it, validate it, report results, then stop. Works with the orchestrator skill. (user)
typora-markdown
by petestewart
Open markdown content in Typora for enhanced viewing. Use when creating plans, PR reviews, analysis reports, or substantial markdown content. Triggers on: plan files, /review-pr output, codebase analysis, documentation generation, or explicit user request to view in Typora.
explain-project
by petestewart
Generate a detailed, engaging FOR[name].md document that explains an entire project in plain language. Covers technical architecture, codebase structure, technology choices, and lessons learned (bugs, pitfalls, best practices). Written in a conversational, memorable style with analogies and anecdotes. Use when the user invokes "/explain-project" or asks to "explain this project", "write a project explainer", "write a FOR[name].md", "document this project for me", or "help me understand this codebase". Accepts an optional name argument (e.g., "/explain-project Pete").
article-add
by petestewart
Add a topic to the article queue for later generation. Use when the user invokes "/article-add <topic>" or says "add to article queue", "queue up an article about", or "save this topic for an article later".
brn:workflow
by zfael
Orchestrate the complete development workflow from ticket to PR. Use when: (1) Starting work on a JIRA ticket, (2) Following the planning-coding-review cycle.
project-planner
by petestewart
Generate a comprehensive PLAN.md file for a new project. Creates structured plans with tickets that an Orchestrator can execute.
specs
by petestewart
Create technical specifications from PRD.md and PROBLEM.md. Use when the user has a PRD and wants detailed technical specs for implementation. Also use when the user says "/specs", "create specs", "technical specifications", or "spec it out".
dspy-ruby
by 8b-is
This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications. Use this when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers (OpenAI, Anthropic, Gemini, Ollama), building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.
problem-statement
by petestewart
Create a structured problem statement document for a feature, bugfix, or project. Use when starting a project, adding a feature, or fixing a bug and you need to clearly define the problem, context, desired outcome, and success criteria. Accepts input from Jira tickets (via MCP), document links, or text descriptions.
brn:jira
by zfael
Interact with JIRA API for ticket management and tracking. Use when: (1) Listing assigned tickets, (2) Getting details, (3) Updating status.
review-as
by petestewart
Review a PR or branch using a specific reviewer's technical preferences. Use when the user says "/review-as <name> <pr-number-or-branch>", "review this as matt", "what would matt say about this PR", or needs code reviewed against a particular person's standards.
article
by petestewart
This skill should be used when the user asks to "write an article", "create an article", "explain this topic", or invokes "/article <subject>". Generates self-contained HTML articles with inline SVG diagrams, proper structure, and polished styling. Handles plain text subjects, file paths (.md, .txt), and URLs as input.
dhh-rails-style
by 8b-is
This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.
prd
by petestewart
Expand a problem statement into a Product Requirements Document (PRD). Use when the user has a PROBLEM.md and wants to create a fuller PRD.md with technical approach, dependencies, affected systems, and open questions. Also use when the user says "/prd", "create a PRD", "expand to PRD", or "product requirements document".