takwerx

Atak Plugin Pipeline — Data skill for Claude Code

Data community

How takwerx builds ATAK plugins and gets them through TAK's third-party signing pipeline, as a Claude Code skill.

How to install Atak Plugin Pipeline

This entry records only its repository, not the path inside it, so there is no exact command to give. Open takwerx/atak-plugin-pipeline and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Atak Plugin Pipeline does

How takwerx builds ATAK plugins and gets them through TAK's third-party signing pipeline, as a Claude Code skill. No SDK included.

Alternatives in Data

Skill Production Pipeline — Claude-skills — Effective: 2026-03-07 Applies to ALL new skills, improvements, and deployments 5.3k ★
Ars Full — ARS full pipeline — research → write → review → revise → finalize 4.5k ★
Osint Employees — Gather employee names + email patterns for password spray prep 4.5k ★

README

atak-plugin-pipeline

How we build ATAK plugins and get them through TAK's third-party signing pipeline, packaged as a [Claude Code](https://claude.com/claude-code) skill. It covers scaffolding from the SDK template, ATAK-native UI, release builds, the user manual and its Tool Preferences entry, the tak.gov source-submission zip, reading what tak.gov sends back, the public plugin repo, and the `versionCode` rule an MDM needs.

It is a working set of gates, not a write-up. Each script refuses the mistake it was written for, and every rule in it shipped broken at least once before it became a rule.

Why

A plugin is not finished when it works on your phone. It is finished when a stranger can install the right APK for their ATAK version, open the manual from inside ATAK, and get the next version pushed to them without uninstalling anything. Most of what goes wrong between those two points is silent: a plugin that builds and will not load, a manual nobody can open, a signed APK that reads as broken on the wrong phone, an update the MDM refuses because every signed build says `versionCode=1`.

Install

git clone https://github.com/takwerx/atak-plugin-pipeline \
    ~/.claude/skills/atak-plugin-pipeline

Claude Code picks it up on the next session and uses it when you work on an ATAK plugin, or on demand with `/atak-plugin-pipeline`. Update with `git pull` in that directory.

To use the scripts from a shell as well:

source ~/.claude/skills/atak-plugin-pipeline/scripts/env.sh

You can also install it per project: clone it into `/.claude/skills/` instead. That is the better choice if you want the scripts versioned next to the plugin.

The SDK is not here, and never will be

The ATAK-CIV SDK comes from [tak.gov](https://tak.gov) and nowhere else. Its license lets you build plugins from it and forbids anyone to redistribute it. So this repository contains no SDK code, resources or binaries, and neither should yours. Each developer