New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jira Expert

by alirezarezvani in alirezarezvani/claude-skills

Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features.

MITAuto-check passedProduct & Project Management

Install Jira Expert

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill jira-expert -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills jira-expert --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/skills/jira-expert .claude/skills/jira-expert && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jira-expert
GitHub stars
28k
Token cost
~3.2k tokens
SKILL.md length
1,261 words
Files
7 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features.

  • Works in 7 steps: Determine project type (Scrum, Kanban,… → Create project with appropriate template… → Configure project settings → …
  • Configuring Jira projects
  • SKILL.md covers Quick Start — Most Common…, Workflows, Advanced Features and JQL Functions Reference, plus 6 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Jira Expert is an agent skill from alirezarezvani/claude-skills. Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/AUTOMATION.md`, `references/WORKFLOWS.md` and `references/automation-examples.md`).

It sits in Product & Project Management. It works with Jira and Model Context Protocol. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Configuring Jira projects
  • Writing JQL and advanced searches
  • Creating dashboards
  • Designing workflows

Example prompts

  • “/jira-expert”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Determine project type (Scrum, Kanban, Bug Tracking, etc.)
  2. Create project with appropriate template (web UI / REST)
  3. Configure project settings
  4. Set up issue types and workflows
  5. Configure custom fields if needed
  6. Create initial board/backlog view
  7. HANDOFF TO: Scrum Master for team onboarding

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jira Expert loads about 3.2k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 1,261 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,261 words, ~3,157 tokens.

Download SKILL.mdSave it as .claude/skills/jira-expert/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
jira-expert
description
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations.

Atlassian Jira Expert

Master-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles all technical and operational aspects of Jira.

Quick Start — Most Common Operations

All MCP examples in this skill use the real Atlassian Remote MCP tools (camelCase, surfaced as mcp__atlassian__<toolName>). The canonical tool list is project-management/references/atlassian-mcp-tools.md — never invent tool names; if a capability isn't listed there, it is not available via MCP.

Create an issue (call getAccessibleAtlassianResources once first to obtain cloudId):

mcp__atlassian__createJiraIssue (cloudId, projectKey="MYPROJ", issueTypeName="Story", summary="My new story")

Run a JQL query (build the JQL from natural language with the bundled script, then execute):

bash
python3 scripts/jql_query_builder.py "high priority bugs assigned to me"
# → emits validated JQL, e.g.: assignee = currentUser() AND type = Bug AND status != Done
mcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql="project = MYPROJ AND status != Done AND dueDate < now()")

Create a project: NOT available via MCP. Use the Jira web UI (Projects > Create project) or REST API (POST /rest/api/3/project).

For the full tool reference, see Atlassian MCP Integration. For JQL functions, see JQL Functions Reference. For report templates, see Reporting Templates.

Workflows

Project Creation

Project creation is not available via MCP — perform steps 2-6 in the Jira web UI (Projects > Create project) or via REST API (POST /rest/api/3/project). After creation, verify visibility with mcp__atlassian__getVisibleJiraProjects and inspect issue types with mcp__atlassian__getJiraProjectIssueTypesMetadata.

  1. Determine project type (Scrum, Kanban, Bug Tracking, etc.)
  2. Create project with appropriate template (web UI / REST)
  3. Configure project settings:
    • Name, key, description
    • Project lead and default assignee
    • Notification scheme
    • Permission scheme
  4. Set up issue types and workflows
  5. Configure custom fields if needed
  6. Create initial board/backlog view
  7. HANDOFF TO: Scrum Master for team onboarding
Workflow Design

Workflow/scheme editing is not available via MCP — configure in Jira Settings > Issues > Workflows. Use the bundled validator to catch anti-patterns before deploying.

  1. Map out process states (To Do → In Progress → Done)
  2. Define transitions and conditions
  3. Lint the design before building it in Jira:
    bash
    python3 scripts/workflow_validator.py workflow.json --format json
    Input: a JSON file with the workflow's states and transitions. Consume the output: fix every reported anti-pattern (dead-end states, unreachable states, missing transitions) in the design before touching Jira.
  4. Add validators, post-functions, and conditions; configure the workflow scheme (web UI)
  5. Validate: Deploy to a test project first; verify all transitions, conditions, and post-functions behave as expected before associating with production projects
  6. Associate workflow with project
  7. Test workflow with sample issues — via MCP: mcp__atlassian__getTransitionsForJiraIssue on a sample issue to confirm expected transitions surface, then mcp__atlassian__transitionJiraIssue to walk it through the flow
JQL Query Building

Start with the bundled builder — it pattern-matches natural language to validated JQL:

bash
python3 scripts/jql_query_builder.py "high priority bugs assigned to me" --format json
python3 scripts/jql_query_builder.py --patterns   # list all supported query patterns

Consume the output: take the jql field from the JSON result (or the GENERATED JQL block in text mode) and execute it with mcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=<generated>). If the builder reports no pattern match, compose JQL manually using the reference below.

Basic Structure: field operator value

Common Operators:

  • =, != : equals, not equals
  • ~, !~ : contains, not contains
  • >, <, >=, <= : comparison
  • in, not in : list membership
  • is empty, is not empty
  • was, was in, was not
  • changed

Powerful JQL Examples:

Find overdue issues:

jql
dueDate < now() AND status != Done

Sprint burndown issues:

jql
sprint = 23 AND status changed TO "Done" DURING (startOfSprint(), endOfSprint())

Find stale issues:

jql
updated < -30d AND status != Done

Cross-project epic tracking:

jql
"Epic Link" = PROJ-123 ORDER BY rank

Velocity calculation:

jql
sprint in closedSprints() AND resolution = Done

Team capacity:

jql
assignee in (user1, user2) AND sprint in openSprints()
Dashboard Creation
  1. Create new dashboard (personal or shared)
  2. Add relevant gadgets:
    • Filter Results (JQL-based)
    • Sprint Burndown
    • Velocity Chart
    • Created vs Resolved
    • Pie Chart (status distribution)
  3. Arrange layout for readability
  4. Configure automatic refresh
  5. Share with appropriate teams
  6. HANDOFF TO: Senior PM or Scrum Master for use
Automation Rules
  1. Define trigger (issue created, field changed, scheduled)
  2. Add conditions (if applicable)
  3. Define actions:
    • Update field
    • Send notification
    • Create subtask
    • Transition issue
    • Post comment
  4. Test automation with sample data
  5. Enable and monitor

Advanced Features

Custom Fields

When to Create:

  • Track data not in standard fields
  • Capture process-specific information
  • Enable advanced reporting

Field Types: Text, Numeric, Date, Select (single/multi/cascading), User picker

Configuration:

  1. Create custom field
  2. Configure field context (which projects/issue types)
  3. Add to appropriate screens
  4. Update search templates if needed
Issue Linking

Link Types:

  • Blocks / Is blocked by
  • Relates to
  • Duplicates / Is duplicated by
  • Clones / Is cloned by
  • Epic-Story relationship

Best Practices:

  • Use Epic linking for feature grouping
  • Use blocking links to show dependencies
  • Document link reasons in comments
Permissions & Security

Permission Schemes:

  • Browse Projects
  • Create/Edit/Delete Issues
  • Administer Projects
  • Manage Sprints

Security Levels:

  • Define confidential issue visibility
  • Control access to sensitive data
  • Audit security changes
Bulk Operations

Bulk Change:

  1. Use JQL to find target issues
  2. Select bulk change operation
  3. Choose fields to update
  4. Validate: Preview all changes before executing; confirm the JQL filter matches only intended issues — bulk edits are difficult to reverse
  5. Execute and confirm
  6. Monitor background task

Bulk Transitions:

  • Move multiple issues through workflow
  • Useful for sprint cleanup
  • Requires appropriate permissions
  • Validate: Run the JQL filter and review results in small batches before applying at scale
Show full SKILL.md (497 more words)Show less

JQL Functions Reference

Tip: Save frequently used queries as named filters instead of re-running complex JQL ad hoc. See Best Practices for performance guidance.

Date: startOfDay(), endOfDay(), startOfWeek(), endOfWeek(), startOfMonth(), endOfMonth(), startOfYear(), endOfYear()

Sprint: openSprints(), closedSprints(), futureSprints()

User: currentUser(), membersOf("group")

Advanced: issueHistory(), linkedIssues(), issuesWithFixVersions()

Reporting Templates

Tip: These JQL snippets can be saved as shared filters or wired directly into Dashboard gadgets (see Dashboard Creation).

ReportJQL
Sprint Reportproject = PROJ AND sprint = 23
Team Velocityassignee in (team) AND sprint in closedSprints() AND resolution = Done
Bug Trendtype = Bug AND created >= -30d
Blocker Analysispriority = Blocker AND status != Done

Decision Framework

When to Escalate to Atlassian Admin:

  • Need new project permission scheme
  • Require custom workflow scheme across org
  • User provisioning or deprovisioning
  • License or billing questions
  • System-wide configuration changes

When to Collaborate with Scrum Master:

  • Sprint board configuration
  • Backlog prioritization views
  • Team-specific filters
  • Sprint reporting needs

When to Collaborate with Senior PM:

  • Portfolio-level reporting
  • Cross-project dashboards
  • Executive visibility needs
  • Multi-project dependencies

Handoff Protocols

FROM Senior PM:

  • Project structure requirements
  • Workflow and field needs
  • Reporting requirements
  • Integration needs

TO Senior PM:

  • Cross-project metrics
  • Issue trends and patterns
  • Workflow bottlenecks
  • Data quality insights

FROM Scrum Master:

  • Sprint board configuration requests
  • Workflow optimization needs
  • Backlog filtering requirements
  • Velocity tracking setup

TO Scrum Master:

  • Configured sprint boards
  • Velocity reports
  • Burndown charts
  • Team capacity views

Best Practices

Data Quality:

  • Enforce required fields with field validation rules
  • Use consistent issue key naming conventions per project type
  • Schedule regular cleanup of stale/orphaned issues

Performance:

  • Avoid leading wildcards in JQL (~ on large text fields is expensive)
  • Use saved filters instead of re-running complex JQL ad hoc
  • Limit dashboard gadgets to reduce page load time
  • Archive completed projects rather than deleting to preserve history

Governance:

  • Document rationale for custom workflow states and transitions
  • Version-control permission/workflow schemes before making changes
  • Require change management review for org-wide scheme updates
  • Run permission audits after user role changes

Atlassian MCP Integration

Primary Tool: Atlassian Remote MCP server (bundled .mcp.json, server key atlassian). Tools surface as mcp__atlassian__<toolName>. Canonical tool list: project-management/references/atlassian-mcp-tools.md. Never invent tool names — if a capability isn't in that list, route to the web UI/REST API.

Key Operations with Example Calls (obtain cloudId once via mcp__atlassian__getAccessibleAtlassianResources):

Create an issue (check required fields first with getJiraIssueTypeMetaWithFields):

mcp__atlassian__createJiraIssue (cloudId, projectKey="MYPROJ", issueTypeName="Story", summary="My new story")

Execute a JQL query:

mcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql="project = MYPROJ AND status != Done AND dueDate < now()")

Update an issue field:

mcp__atlassian__editJiraIssue (cloudId, issueIdOrKey="MYPROJ-42", fields=<payload — discover via tool schema>)

Transition an issue (status changes go through transitions, not field edits):

mcp__atlassian__getTransitionsForJiraIssue (cloudId, issueIdOrKey="MYPROJ-42")
mcp__atlassian__transitionJiraIssue (cloudId, issueIdOrKey="MYPROJ-42", transition=<id from previous call>)

Comment / log work / link issues:

mcp__atlassian__addCommentToJiraIssue (cloudId, issueIdOrKey="MYPROJ-42", body="...")
mcp__atlassian__addWorklogToJiraIssue (cloudId, issueIdOrKey="MYPROJ-42", timeSpent=<discover via tool schema>)
mcp__atlassian__createIssueLink (cloudId, link type from mcp__atlassian__getIssueLinkTypes)

Not available via MCP — use the web UI or REST API instead:

  • Create a project → Jira UI Projects > Create project or POST /rest/api/3/project
  • Create a sprint or configure boards → Jira Software UI or POST /rest/agile/1.0/sprint
  • Create/share a filter → Jira UI Filters > Save as or POST /rest/api/3/filter
  • Custom fields, screens, workflow/permission schemes → Jira admin UI

Integration Points:

  • Pull metrics for Senior PM reporting
  • Configure sprint boards for Scrum Master
  • Create documentation pages for Confluence Expert
  • Support template creation for Template Creator
  • Confluence Expert (project-management/confluence-expert/) — Documentation complements Jira workflows
  • Atlassian Admin (project-management/atlassian-admin/) — Permission and user management for Jira projects

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (scripts, references) in project-management/skills/jira-expert of alirezarezvani/claude-skills.

  • SKILL.md
  • references/AUTOMATION.md
  • references/WORKFLOWS.md
  • references/automation-examples.md
  • references/jql-examples.md
  • scripts/jql_query_builder.py
  • scripts/workflow_validator.py

Open the folder on GitHubat commit 19392f7

Compare with similar skills

Jira Expert next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jira Expert compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jira Expert this skillalirezarezvani/claude-skills28k—~3.2kAutomated safety check: PassMIT
Jira Natural Language Interfacejjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT
JiraVixenLights/Vixen114—~3.4kAutomated safety check: PassCustom licence
Daily Meeting Updatedavila7/claude-code-templates33k2 repos~3kAutomated safety check: PassMIT
Piv Slice Epiccoleam00/skills676—~1.5kAutomated safety check: PassMIT
Integration Orchestratorrampstackco/claude-skills945—~5.3kAutomated safety check: PassMIT

Similar skills

  • Jira Natural Language Interface

    jjmartres/opencode

    Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

    133 GitHub starsUsed in 3 repos~1.7k tokens
    Product & Project ManagementAuto-check passed

  • Jira

    VixenLights/Vixen

    Manages JIRA issues, projects, and workflows using Atlassian MCP.

    114 GitHub stars~3.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Daily Meeting Update

    davila7/claude-code-templates

    Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.

    33k GitHub starsUsed in 2 repos~3k tokens
    Product & Project ManagementAuto-check passed

  • Piv Slice Epic

    coleam00/skills

    Slice an epic (with its architecture decisions) into PIV-sized tickets with a dependency graph, then create them in your tracker (Jira via the Atlassian MCP, or GitHub/Linear/local).

    676 GitHub stars~1.5k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

  • Integration Orchestrator

    rampstackco/claude-skills

    Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's…

    945 GitHub stars~5.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed

  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Works with

Categories

Questions about Jira Expert

What does Jira Expert do?

Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Jira Expert is an agent skill from alirezarezvani/claude-skills. Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features.

When should I use Jira Expert?

Jira Expert fits situations like: configuring Jira projects; writing JQL and advanced searches; creating dashboards; designing workflows.

How do I install Jira Expert in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill jira-expert -a claude-code`. Or copy the skill folder (project-management/skills/jira-expert in alirezarezvani/claude-skills) into .claude/skills/jira-expert in your project. Claude Code loads it when a task matches its description.

How do I install Jira Expert in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill jira-expert -a codex`. Or copy the skill folder (project-management/skills/jira-expert in alirezarezvani/claude-skills) into .agents/skills/jira-expert in your project. Codex loads it when a task matches its description.

Can I use Jira Expert in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill jira-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-expert, .gemini/skills/jira-expert, .github/skills/jira-expert and .opencode/skills/jira-expert in your project.

What does Jira Expert need to run?

Going by SKILL.md and its folder, Jira Expert needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Jira Expert access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Jira Expert safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Jira Expert use?

Jira Expert is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jira Expert use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.3k tokens, read only when the agent opens those files.

What are the alternatives to Jira Expert?

Skills that share tags, products or a category with Jira Expert: Jira Natural Language Interface (jjmartres/opencode, 133 stars), Jira (VixenLights/Vixen, 114 stars), Daily Meeting Update (davila7/claude-code-templates, 33k stars) and Piv Slice Epic (coleam00/skills, 676 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Expert?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.