AUR Bundler

VerifiedSafe

Creates Arch Linux packages (PKGBUILD) for AUR submission. Useful when packaging software for Arch Linux, generating AUR metadata (.SRCINFO), and handling VCS (git, svn) or release builds.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#arch-linux#aur#pkgbuild#package-management#linux

Recommended for

Automated summary

Creates PKGBUILD files and related metadata for submitting software projects to the Arch User Repository (AUR).

Strengths

  • Automates PKGBUILD creation based on project structure
  • Supports multiple build systems (Cargo, Python, CMake, etc.)
  • Handles both release tarballs and VCS packages
  • Includes validation and submission guidance

Limitations

  • Requires an Arch Linux environment with makepkg and namcap installed
  • May not cover highly non-standard build configurations
  • Assumes familiarity with AUR submission process
When to use it

When you need to package a software project for distribution via the Arch User Repository.

When not to use it

For general package installation, managing existing packages, or for non-Arch Linux distributions.

Security analysis

Safe
Quality score85/100

The skill provides instructions for creating PKGBUILD files and does not include any dangerous commands or system modifications. It explicitly restricts usage to AUR packaging tasks and avoids arbitrary code execution.

No concerns found

How this analysis is made

Examples

Rust CLI tool packaging
Create an AUR package for my Rust CLI tool located at https://github.com/user/my-rust-tool (tag v1.2.0). Generate PKGBUILD and .SRCINFO.
Python library packaging
Generate a PKGBUILD for a Python package from PyPI called 'mylib' version 0.5.0. It uses setuptools, has dependencies on requests and click, and license is MIT.
CMake project with Git VCS
Package this CMake project from GitHub (https://github.com/user/project) for AUR as a VCS package. The project uses Git and builds with CMake. Provide PKGBUILD for the -git variant.

name: aur-bundler description: Creates Arch Linux packages (PKGBUILD) for AUR submission. Use when users want to "package for AUR", "create PKGBUILD", "build AUR package", "submit to AUR", or need Arch packaging for software projects. scope: global license: MIT

AUR Bundler Skill

When to use this skill

Use this skill when users need to:

  • Create PKGBUILD files for AUR submission
  • Package software projects for Arch Linux
  • Convert GitHub/GitLab projects into installable AUR packages
  • Build Rust, Python, CMake, Autotools, or other projects for AUR
  • Generate AUR metadata (.SRCINFO) and validate packages
  • Handle VCS packages (git, svn) or regular releases

Triggers: "AUR", "PKGBUILD", "Arch package", "aur-bundler", "package for Arch", "submit to AUR", "create AUR package"

Never use for: General package installation, system package management, non-Arch systems

Instructions

Step 1: Analyze Project Structure

  • Identify build system (Cargo.toml, package.json, Makefile, CMakeLists.txt, setup.py)
  • Extract metadata: name, version, description, license, URL
  • List all dependencies (runtime, build-time, optional)
  • Check for VCS needs (git, svn) or static releases

Step 2: Create PKGBUILD

Generate main build script with:

  • Mandatory fields: pkgname, pkgver, pkgrel, arch, pkgdesc, url, license
  • Source: Release tarball URL or VCS URL with branch/tag
  • Checksums: sha256sums for releases, SKIP for VCS
  • Dependencies: depends, makedepends, checkdepends, optdepends

Step 3: Implement Build Functions

build() {
  cd "$pkgname-$pkgver"
  # Build commands based on project type
}

package() {
  cd "$pkgname-$pkgver"
  # Install to $pkgdir with correct paths
}

Step 4: Test and Validate

  • Test build: makepkg --nodeps --skippgpcheck
  • Generate checksums: makepkg -g >> PKGBUILD
  • Validate: namcap PKGBUILD
  • Generate metadata: makepkg --printsrcinfo > .SRCINFO

Step 5: AUR Submission

  • Set up Git repository with PKGBUILD and .SRCINFO
  • Configure SSH for AUR access
  • Push to AUR git repository

Tools Required

  • makepkg: Package building (pacman)
  • namcap: PKGBUILD validation
  • git: For VCS packages and AUR submission
  • Build tools: base-devel, cargo, rust, cmake, etc.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/aur-bundler-mm8o52cu/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/aur-bundler-mm8o52cu' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/aur-bundler-mm8o52cu/download' --output '.skill-downloads/aur-bundler-mm8o52cu/SKILL.md.part' && mv '.skill-downloads/aur-bundler-mm8o52cu/SKILL.md.part' '.skill-downloads/aur-bundler-mm8o52cu/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/aur-bundler-mm8o52cu/SKILL.md' && test -s '.skill-downloads/aur-bundler-mm8o52cu/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/aur-bundler' && cp -R '.skill-downloads/aur-bundler-mm8o52cu' '.claude/skills/aur-bundler'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/aur-bundler-mm8o52cu'

openskills read 'aur-bundler-mm8o52cu'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/aur-bundler-mm8o52cu/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills