Pptx
PowerPoint processing. USE WHEN pptx, PowerPoint, slides. SkillSearch('pptx') for docs.
PDF processing. USE WHEN pdf, PDF file. SkillSearch('pdf') for docs.
install-backend
USE WHEN install backend skills, backend stack, setup backend, new backend project, api project setup, hono project, cloudflare workers project.
Council
USE WHEN council, debate, perspectives, agents discuss. SkillSearch('council') for docs.
BrightData
USE WHEN Bright Data, scrape URL, web scraping tiers. SkillSearch('brightdata') for docs.
Browser
USE WHEN browser, screenshot, debug web, verify UI, troubleshoot frontend.
CreateCLI
USE WHEN create CLI, build CLI, command-line tool. SkillSearch('createcli') for docs.
Aphorisms
USE WHEN aphorism, quote, saying. SkillSearch('aphorisms') for docs.
Apify
USE WHEN Twitter, Instagram, LinkedIn, TikTok, YouTube, Facebook, Google Maps, Amazon scraping.
Art
USE WHEN user wants to create visual content, illustrations, diagrams, OR mentions art, header images, visualizations, mermaid, flowchart, technical diagram, infographic, PAI icon, pack icon, or PAI pack icon.
BeCreative
USE WHEN be creative, deep thinking, deep thinking, extended reasoning. SkillSearch('becreative') for docs.
install-frontend
USE WHEN install frontend skills, frontend stack, setup frontend, new frontend project, react project setup.
Docx
Word document processing. USE WHEN docx, Word document. SkillSearch('docx') for docs.
CreateSkill
USE WHEN create skill, new skill, skill structure, canonicalize. SkillSearch('createskill') for docs.
AnnualReports
USE WHEN annual reports, security reports, threat reports, industry reports, update reports, analyze reports, vendor reports, threat landscape.
FirstPrinciples
USE WHEN first principles, fundamental, root cause, decompose. SkillSearch('firstprinciples') for docs.
otel-expert
Use this when working with OpenTelemetry, telemetry, observability, traces, spans, metrics, logs, OTLP, semantic conventions, or instrumentation. Triggers on questions like "what attributes should I use", "how do I configure the collector", "what's the semconv for X".
example-skill
Brief description of what this skill does. Use when [specific trigger situations].
hades
IF cleanup/elimination needed THEN use this. IF zero suppressions THEN this. IF dead code THEN this. IF duplication THEN this. IF frontend design quality audit THEN use this with --goggles. Smart-Hades: every session gets a Smart ID, deletion permit, and audit ledger. Team lead skill — spawns 4 debate teammates per phase (+3 goggles teammates when equipped). Ignores public API, semver, changelog. Pure functional destruction. Idempotent: same input, same output. Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1.
writing-rules
>
eight-gates
>-
ticket-edit-comment
Edit an existing comment on a Jira ticket. Use when the user wants to update, correct, or improve a comment they previously added.
ticket-delete-comment
Delete a comment from a Jira ticket. Use when the user wants to remove a comment they previously added or clean up outdated comments.
ticket-fields
Discover available Jira fields for a project and issue type. Use when the user needs to find field names, see what fields are available, or discover custom field values before creating or updating tickets.
ticket-search
Search Jira tickets using JQL queries. Use when the user wants to find tickets, search for issues, list their assigned work, or query the backlog.
ticket-create
Create a new Jira ticket. Use when the user wants to create a task, bug, story, or any other issue type in Jira.
pr-view
View pull request details including title, status, branches, and description. Use when the user asks about a PR, wants PR context, mentions viewing/checking a pull request, or needs to understand what a PR is about.
ticket-comments
Get comments from a Jira ticket to review discussion history. Use when the user wants to see ticket comments, check for updates, review feedback, or understand the discussion on an issue.
ticket-comment
Add a comment to a Jira ticket. Use when the user wants to post an update, ask a question, document a decision, or communicate status on a ticket.
ticket-attach
Manage Jira ticket attachments. Use when the user wants to list, upload, download, or delete attachments on a ticket.
ticket-transition
Change a Jira ticket's workflow status. Use when the user wants to move a ticket to a different status, start work, complete a task, or change workflow state.
ticket
View Jira ticket details to understand requirements and context. Use when the user mentions a ticket key, wants to understand a task, needs to load ticket context, or starts work on an issue.
ticket-update
Update fields on an existing Jira ticket. Use when the user wants to modify a ticket's summary, description, assignee, priority, labels, or custom fields.
pr-diff
View pull request diff and code changes. Use when the user wants to see what changed in a PR, review code changes, understand the scope of modifications, or examine specific file changes.
pr-update
Update an existing pull request. Use when the user wants to modify PR title, description, publish a draft, convert to draft, abandon, or reactivate a PR.
pr-create
Create a new pull request. Use when the user wants to open a PR, submit code for review, create a draft PR, or push changes for merge.
pr-list
List pull requests from the repository. Use when the user wants to see open PRs, find PRs to review, check their own PRs, or browse PR history.
pr-comments
Load PR comments and feedback for code review. Use when the user wants to see reviewer feedback, check for unresolved comments, understand what changes are requested, or review discussion on a PR.
pr-reply
Reply to an existing comment thread on a pull request. Use when the user wants to respond to reviewer feedback, continue a discussion, or acknowledge comments in an existing thread.
pr-comment
Post a comment on a pull request. Use when the user wants to add a comment to a PR, respond to feedback, request review, or document decisions.
writing-product-specs
Use when asked to design a new feature or project
summoning-the-user
Use when an agent encounters a blocking decision or when proceeding without user input could lead to wasted work - helps Claude determine when to block and request user input versus making reasonable assumptions
working-on-an-issue
Use when asked to work on, read, or implement a GitHub issue.
day-planning
Interactive daily planning ritual that guides the user through a reflective conversation across all life dimensions (work, fitness, relationship, social, adventure) and produces a holistic day plan. Use when the user requests to plan their day with phrases like "plan the day", "plan my day", "plan today", or similar variations.
setting-up-a-project
You MUST use this skill when the user asks you to setup a claude code project. You should also suggest it if there is no CLAUDE.md or when starting work on an empty codebase.
writing-verification-plans
Use when a project needs a verification plan for acceptance testing in real-world scenarios
writing-user-stories
Use when an agent needs to write user stories for a project
reduce-orchestrator
MapReduce root/orchestrator with a mandatory parallel Verify phase, narrative-first reduction, deterministic artifact lifecycle management (.rlm run/archives), and concurrency safety (per-run locks + cleanup lock). Use when coordinating many parallel map-worker tasks under optional hint_paths, then synthesizing narrative reports into a decision to iterate or finish.
map-worker
Contract-based MapReduce worker for executing a task (may be broad) under optional hint_paths, producing a narrative report. Use when an orchestrator invokes a map worker (llm_query role) many times in parallel and needs mergeable narrative reports.
orchestration
MANDATORY - Your default operating system. Adaptive workflow that routes simple tasks to direct execution and complex tasks to PRD iterations with agent swarms. Auto-creates skills when patterns emerge.
Page 1337 of 1579 · 78901 results
