How do I install the Build Distribution skill?

Run npx skillmds@latest add fusengine/build-distribution in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Distribution safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Distribution?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Distribution free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build Distribution?

fusengine (@fusengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Distribution by fusengine — Agent Skill

Name: Build Distribution
Rating: 4.2 (5 reviews)
Author: fusengine

File contents

Includes a release checklist (version/build number, app icons for light/dark/tinted, privacy manifest, release configuration, archive validation, TestFlight testing, screenshots, App Store metadata) and guidance on automating releases with fastlane and CI/CD (e.g. GitHub Actions).

Best practices favor automatic signing, TestFlight testing before any public release, incrementing the build number on every upload, and a mandatory privacy manifest for App Store submission.

Build & Distribution

App build, signing, and distribution for all Apple platforms.

Agent Workflow (MANDATORY)

Before ANY distribution, spawn 3 agents in parallel, one Agent call each with a name:

fuse-ai-pilot:explore-codebase - Check existing build configuration
fuse-ai-pilot:research-expert - Verify latest App Store requirements
mcp__XcodeBuildMCP__show_build_settings - Review build settings

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

Preparing app for release
Configuring code signing
Uploading to TestFlight
Submitting to App Store
Creating app icons
CI/CD pipeline setup

Why Build Distribution Skill

Feature	Benefit
Automatic signing	Simplifies certificate management
TestFlight	Beta testing with users
App Store	Public distribution
CI/CD	Automated releases

Reference Guide

Need	Reference
Certificates, profiles	code-signing.md
Beta testing	testflight.md
App Store submission	app-store.md
Icons, assets	app-icons.md
In-app purchases, subscriptions	storekit2.md

Release Checklist

Version and build number updated
App icons complete (light/dark/tinted)
Privacy manifest (PrivacyInfo.xcprivacy)
Release configuration
Archive validates
TestFlight tested
Screenshots updated
App Store metadata complete

Best Practices

Automatic signing - Let Xcode manage
TestFlight first - Always beta test
Increment build - Every upload needs new build number
Privacy manifest - Required for App Store
fastlane - Automate repetitive tasks
CI/CD - GitHub Actions for automation

---name: build-distributiondescription: Use when preparing an Apple release — code signing, TestFlight upload, App Store submission, or app icons/CI across all platforms.---<objective>Covers app build, code signing, and distribution across all Apple platforms: certificate/profile management, TestFlight beta distribution, App Store submission, app icon/asset preparation, and StoreKit 2 in-app purchases/subscriptions.Includes a release checklist (version/build number, app icons for light/dark/tinted, privacy manifest, release configuration, archive validation, TestFlight testing, screenshots, App Store metadata) and guidance on automating releases with fastlane and CI/CD (e.g. GitHub Actions).Best practices favor automatic signing, TestFlight testing before any public release, incrementing the build number on every upload, and a mandatory privacy manifest for App Store submission.</objective># Build & DistributionApp build, signing, and distribution for all Apple platforms.## Agent Workflow (MANDATORY)Before ANY distribution, spawn 3 agents in parallel, one `Agent` call each with a `name`:1. **fuse-ai-pilot:explore-codebase** - Check existing build configuration2. **fuse-ai-pilot:research-expert** - Verify latest App Store requirements3. **mcp__XcodeBuildMCP__show_build_settings** - Review build settingsAfter implementation, run **fuse-ai-pilot:sniper** for validation.---## Overview### When to Use- Preparing app for release- Configuring code signing- Uploading to TestFlight- Submitting to App Store- Creating app icons- CI/CD pipeline setup### Why Build Distribution Skill| Feature | Benefit ||---------|---------|| Automatic signing | Simplifies certificate management || TestFlight | Beta testing with users || App Store | Public distribution || CI/CD | Automated releases |---## Reference Guide| Need | Reference ||------|-----------|| Certificates, profiles | [code-signing.md](references/code-signing.md) || Beta testing | [testflight.md](references/testflight.md) || App Store submission | [app-store.md](references/app-store.md) || Icons, assets | [app-icons.md](references/app-icons.md) || In-app purchases, subscriptions | [storekit2.md](references/storekit2.md) |---## Release Checklist- [ ] Version and build number updated- [ ] App icons complete (light/dark/tinted)- [ ] Privacy manifest (PrivacyInfo.xcprivacy)- [ ] Release configuration- [ ] Archive validates- [ ] TestFlight tested- [ ] Screenshots updated- [ ] App Store metadata complete---## Best Practices1. **Automatic signing** - Let Xcode manage2. **TestFlight first** - Always beta test3. **Increment build** - Every upload needs new build number4. **Privacy manifest** - Required for App Store5. **fastlane** - Automate repetitive tasks6. **CI/CD** - GitHub Actions for automation

Frequently asked questions

Build Distribution