mcpbeat Sign in

Social Export Skill for Claude

Generates infrastructure for exporting app content to social platforms (Instagram Stories, TikTok, Twitter/X) with platform-specific formatting, aspect ratios, and metadata. Use when user wants social media export, share to stories, or platform-specific sharing pipelines.

13k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
585
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/rshankras/claude-code-apple-skills --skill social-export

The instruction itself

28 sections, as written by the author

Social Export Generator

Generate a production social export pipeline with platform-specific formatters, aspect ratio handling, branding overlays, and a complete SwiftUI export flow. Different from share-card (which creates the visual image) — this handles the full export pipeline to each social platform.

When This Skill Activates

Use this skill when the user:

  • Asks to "export to Instagram" or "share to Instagram Stories"
  • Wants "social media export" or "social sharing pipeline"
  • Mentions "share to TikTok" or "export for TikTok"
  • Asks about "platform-specific sharing" or "export to Twitter/X"
  • Wants to "format content for social platforms"
  • Mentions "story export" or "share to stories"

Pre-Generation Checks

1. Project Context Detection

  • [ ] Check Swift version (requires Swift 5.9+)
  • [ ] Check deployment target (iOS 16+ / macOS 13+)
  • [ ] Check for @Observable support (iOS 17+ / macOS 14+)
  • [ ] Identify source file locations

2. Conflict Detection

Search for existing social export or sharing code:

Glob: **/*SocialExport*.swift, **/*ShareExport*.swift, **/*StoryExport*.swift
Grep: "UIActivityViewController" or "instagram-stories" or "SocialPlatform"

If existing share infrastructure found:

  • Ask if user wants to extend or replace it
  • If extending, integrate with existing sharing code

3. Framework Detection

Check for frameworks already in use:

Grep: "import Photos" or "import PhotosUI" or "import LinkPresentation"
Grep: "UIDocumentInteractionController" or "UIActivityViewController"

If Photos framework is used, export pipeline can integrate save-to-library as a fallback.

Configuration Questions

Ask user via AskUserQuestion:

  • Target platforms? (multi-select)
  • Instagram Stories (URL scheme + pasteboard)
  • TikTok (URL scheme + share API)
  • Twitter/X (URL scheme + activity controller)
  • General share sheet (UIActivityViewController fallback)
  • Content type?
  • Image only (photo, illustration, screenshot)
  • Video (short-form video export)
  • Text + Image (quote cards, text overlays on images)
  • Include app branding overlay?
  • Yes — add app logo/name watermark to exported content
  • No — export clean content
  • Watermark style? (if branding selected)
  • Corner logo (small, unobtrusive)
  • Bottom banner (app name + URL strip)
  • None

Generation Process

Step 1: Read Templates

Read templates.md for production Swift code.

Step 2: Create Core Files

Generate these files:

  • SocialPlatform.swift — Enum for supported platforms with requirements (aspect ratio, max file size, URL scheme)
  • ExportConfiguration.swift — Configuration struct for export options (platform, quality, branding, watermark)
  • SocialExporter.swift — Protocol + platform-specific implementations for each social network

Step 3: Create Content Formatting

  • ContentFormatter.swift — Formats content per platform (resize, crop to aspect ratio, add metadata)

Step 4: Create UI Files

  • ExportPreviewView.swift — SwiftUI preview showing how content will look on each platform
  • SocialExportSheet.swift — Complete export flow with platform picker, preview, and share action

Step 5: Determine File Location

Check project structure:

  • If Sources/ exists -> Sources/SocialExport/
  • If App/ exists -> App/SocialExport/
  • Otherwise -> SocialExport/

Output Format

After generation, provide:

Files Created

SocialExport/
├── SocialPlatform.swift       # Platform enum with requirements
├── ExportConfiguration.swift  # Export options configuration
├── SocialExporter.swift       # Protocol + platform exporters
├── ContentFormatter.swift     # Resize, crop, metadata
├── ExportPreviewView.swift    # Platform-specific preview
└── SocialExportSheet.swift    # Complete export flow UI

Integration Steps

Export an image to Instagram Stories:

let config = ExportConfiguration(
    platform: .instagramStories,
    quality: .high,
    branding: .cornerLogo(UIImage(named: "AppLogo")!)
)

let exporter = SocialExporter()
try await exporter.export(image: myImage, configuration: config)

Present the export sheet:

struct ContentDetailView: View {
    let content: AppContent
    @State private var showExportSheet = false

    var body: some View {
        VStack {
            ContentView(content: content)
            Button("Share to Social") {
                showExportSheet = true
            }
        }
        .sheet(isPresented: $showExportSheet) {
            SocialExportSheet(image: content.renderedImage)
        }
    }
}

Quick share with fallback:

let exporter = SocialExporter()

// Tries platform-specific export first, falls back to share sheet
try await exporter.export(
    image: shareImage,
    configuration: .init(platform: .instagramStories),
    fallbackToShareSheet: true,
    presentingViewController: viewController
)

Testing

@Test
func instagramStoriesExportFormatsCorrectly() async throws {
    let formatter = ContentFormatter()
    let testImage = UIImage.testSolidColor(.red, size: CGSize(width: 1000, height: 1000))
    let formatted = try formatter.format(testImage, for: .instagramStories)

    // Instagram Stories expects 9:16 aspect ratio (1080x1920)
    #expect(formatted.size.width == 1080)
    #expect(formatted.size.height == 1920)
}

@Test
func fallsBackToShareSheetWhenAppNotInstalled() async throws {
    let exporter = MockSocialExporter(installedApps: [])
    let config = ExportConfiguration(platform: .instagramStories)

    let result = try await exporter.export(
        image: UIImage.testSolidColor(.blue, size: CGSize(width: 500, height: 500)),
        configuration: config,
        fallbackToShareSheet: true
    )

    #expect(result == .fallbackUsed)
}

@Test
func brandingOverlayApplied() async throws {
    let formatter = ContentFormatter()
    let logo = UIImage.testSolidColor(.white, size: CGSize(width: 50, height: 50))
    let config = ExportConfiguration(
        platform: .general,
        branding: .cornerLogo(logo)
    )

    let image = UIImage.testSolidColor(.red, size: CGSize(width: 1080, height: 1080))
    let result = try formatter.format(image, for: config.platform, branding: config.branding)

    // Image should still be the correct size after overlay
    #expect(result.size.width == 1080)
    #expect(result.size.height == 1080)
}

Common Patterns

Instagram Stories Export

Instagram Stories uses URL scheme + pasteboard for background images:

// Key details:
// - URL scheme: instagram-stories://share?source_application=YOUR_APP_ID
// - Pasteboard: set image data with key "com.instagram.sharedSticker.backgroundImage"
// - Aspect ratio: 9:16 (1080x1920)
// - Max file size: ~12 MB for images
// - Supports background image, sticker image, and background color

General Share Sheet Fallback

Always provide UIActivityViewController as a fallback when the target app is not installed:

// Check canOpenURL before attempting URL scheme
// If unavailable, present UIActivityViewController with formatted content
// Include UTType metadata for proper previews in share sheet

Video Export Pipeline

For video content, use AVAssetExportSession to transcode to platform-required formats:

// Instagram/TikTok: H.264, 9:16, max 60s (Stories) or 3min (Reels)
// Twitter/X: H.264, max 2:20, max 512 MB
// General: H.264, original aspect ratio

Gotchas

Instagram URL Scheme Requirements

  • Must register instagram-stories in LSApplicationQueriesSchemes (Info.plist)
  • Facebook App ID is required as the source_application parameter
  • Pasteboard items must be set BEFORE opening the URL scheme
  • Data must be set as Data on the pasteboard, not UIImage

Aspect Ratios Per Platform

| Platform | Stories | Feed Post | Reels/Short |

|----------|---------|-----------|-------------|

| Instagram | 9:16 (1080x1920) | 1:1 (1080x1080) or 4:5 (1080x1350) | 9:16 (1080x1920) |

| TikTok | 9:16 (1080x1920) | 9:16 (1080x1920) | 9:16 (1080x1920) |

| Twitter/X | 16:9 (1200x675) | 16:9 or 1:1 | N/A |

File Size Limits

| Platform | Image Max | Video Max |

|----------|-----------|-----------|

| Instagram Stories | ~12 MB | ~100 MB (H.264) |

| TikTok | ~10 MB | ~287 MB |

| Twitter/X | 5 MB (JPEG/PNG) | 512 MB (H.264) |

App Detection

  • UIApplication.shared.canOpenURL() requires LSApplicationQueriesSchemes in Info.plist
  • iOS limits you to 50 URL schemes in LSApplicationQueriesSchemes
  • Always test on physical device — simulator does not have social apps installed

Thread Safety

  • UIPasteboard.general must be accessed on the main thread
  • UIApplication.shared.open() must be called on the main thread
  • Image formatting/resizing should happen on a background thread to avoid UI lag

References

  • templates.md — All production Swift templates for social export
  • Related: generators/share-card — Generate the visual share image/card
  • Related: generators/watermark-engine — Advanced watermark and branding overlays

Other skills for the same job

different authors, same section of the catalogue
Azure Kubernetes Automatic Readiness
by microsoft
vendor ×3

Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.

13k tokens
Capacity
by microsoft
vendor ×3

Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.

6k tokens scripts
Customize
by microsoft
vendor ×3

Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).

8k tokens
Deploy Model
by microsoft
vendor ×3

Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).

26k tokens scripts
Preset
by microsoft
vendor ×3

Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).

9k tokens
Lamindb
by christophacham
×3

This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.

22k tokens
Latchbio Integration
by christophacham
×3

Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.

12k tokens
Modal
by christophacham
×3

Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.

17k tokens

How to use it

Copy the folder

Take rshankras/social-export from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.