create-aur-package

Included with Lifetime

$97 forever

This skill should be used when the user asks to "create an AUR package", "make a new AUR package", "scaffold AUR package", "create PKGBUILD", "package for AUR", or mentions AUR package creation with a specific source type (npm, rust, go, git, binary, appimage). Provides comprehensive guidance for creating Arch User Repository packages with proper structure, checksums, and git setup.

Backend & APIs

What this skill does


Create a new AUR (Arch User Repository) package with proper structure, validation, and git setup.

Package name: $ARGUMENTS[0]
Source type: $ARGUMENTS[1]

## Workflow

1. **Gather package information**:
   - Package name (provided by user)
   - Source type (npm, rust, go, git, binary, appimage)
   - Fetch metadata from upstream (version, description, license, URL)

2. **Create package directory structure**:
   - Directory named after the package
   - `.gitignore` for build artifacts
   - `PKGBUILD` with appropriate structure for source type

3. **Generate checksums** (skip for `-git` packages):
   ```bash
   updpkgsums
   ```

4. **Build and validate**:
   ```bash
   makepkg -f              # Build the package
   namcap PKGBUILD         # Lint PKGBUILD
   namcap *.pkg.tar.zst    # Lint built package
   ```

5. **Generate metadata**:
   ```bash
   makepkg --printsrcinfo > .SRCINFO
   ```

6. **Initialize git and push to AUR**:
   ```bash
   git init
   git remote add origin ssh://[email protected]/<package-name>.git
   git add .
   git commit -m "feat: initial commit for <package-name>"
   git push -u origin master
   ```

## .gitignore

Create with the following content:

```
pkg
src
<package-name>-*
*.tar.zst
```

For NPM packages, use the actual package name (without scope for scoped packages).
For AppImage packages, also include `squashfs-root`, `*.AppImage`, and the downloaded license file.

## Common PKGBUILD Structure

All PKGBUILD files include these fields:

```bash
pkgname=<package-name>
pkgver=<version>
pkgrel=1
pkgdesc="<package description>"
arch=(any)  # or (x86_64) for architecture-specific
url="<upstream-url>"
license=('<license>')
depends=()      # runtime dependencies
makedepends=()  # build-time dependencies
source=(<source-url>)
sha256sums=('SKIP')  # Update with updpkgsums

package() {
  # Installation steps
}
```

## Source-Specific Instructions

Load the appropriate reference file based on source type:

- **NPM packages**: See `references/npm-packages.md` - For Node.js packages from npm registry
- **Rust packages**: See `references/rust-packages.md` - For Cargo-based Rust projects
- **Go packages**: See `references/go-packages.md` - For Go modules
- **VCS/Git packages**: See `references/vcs-packages.md` - For `-git` packages tracking upstream
- **Binary packages**: See `references/binary-packages.md` - For pre-compiled binaries
- **AppImage packages**: See `references/appimage-packages.md` - For AppImage binaries (typically Electron apps)

## Useful Commands

| Command | Purpose |
|---------|---------|
| `updpkgsums` | Update sha256sums from source files |
| `makepkg --printsrcinfo > .SRCINFO` | Generate .SRCINFO metadata |
| `makepkg -f` | Build package (force rebuild) |
| `makepkg -si` | Build and install package |
| `namcap PKGBUILD` | Lint PKGBUILD for issues |
| `namcap *.pkg.tar.zst` | Lint built package |

## Package Naming Conventions

- **Standard**: `<package-name>` - For release tarballs
- **VCS tracking**: `<package-name>-git` - For git repositories
- **Binary**: `<package-name>-bin` - For pre-compiled binaries
- **AppImage**: `<package-name>-appimage` - For AppImage binaries

## Additional Resources

### Reference Files

- **`references/npm-packages.md`** - NPM package specifics (scoped packages, registry URLs, permission fixes)
- **`references/rust-packages.md`** - Rust/Cargo package specifics (build flags, LTO issues, workspaces)
- **`references/go-packages.md`** - Go module specifics (build flags, GOPATH handling)
- **`references/vcs-packages.md`** - VCS/Git package specifics (pkgver() function, provides/conflicts)
- **`references/binary-packages.md`** - Binary package specifics (release downloads, architecture handling)
- **`references/appimage-packages.md`** - AppImage package specifics (extraction, desktop integration, /opt/ install)

### Examples

- **`examples/pkgbuild-template`** - Basic PKGBUILD template structure

Files: 8

Size: 26.7 KB

Complexity: 54/100

Category: Backend & APIs

Source: https://github.com/asermax/claude-plugins/tree/main/aur/skills/create-aur-package

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts