TypingMindTypingMindThe best frontend for AI
Code Signing logo

Code Signing

Community
khadinakbarlabs
code-signing

Manage iOS code signing: ASC API key, Distribution Certificate, Provisioning Profiles via EAS managed credentials. Use when the user says 'code signing', 'provisioning profile', 'distribution certificate', 'ASC API key'.

Overview

Publisherkhadinakbarlabs
Repositoryexpo-mobile-app-builder
Skill namecode-signing
Stars
3
Forks
0
Bundled files
2
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by khadinakbarlabs on GitHub. Read the source before you install it.

Installation

Install the Code Signing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/code-signing
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/khadinakbarlabs/expo-mobile-app-builder.git /tmp/expo-mobile-app-builder
mkdir -p .claude/skills
cp -r /tmp/expo-mobile-app-builder/skills/code-signing .claude/skills/code-signing
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Code Signing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Code Signing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Code Signing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Code Signing

Indie default: EAS managed credentials. EAS handles cert + profile rotation. You never touch keychains.

Credential and external action gate

Signing certificates, profiles, and App Store Connect keys are private credentials. Do not run eas credentials, create EAS secrets, download a .p8, generate signing material, or revoke a profile without the owner's explicit confirmation of the Apple account, bundle identifier, affected apps, and intended action. Store credentials outside the repository and never display their values.

Initial setup

bash
eas credentials

Choose iOS → Build credentials. EAS will:

  1. Log into your Apple Developer account
  2. Create Distribution Certificate
  3. Create App ID (matching your bundle ID)
  4. Create Provisioning Profile
  5. Store everything in EAS-managed credentials

After that, eas build just works. Collaborators can build without ever touching ASC.

ASC API Key (.p8) — owner-managed setup

  1. App Store Connect → Users and Access → Integrations → +
  2. Use the least-privilege role that supports the intended workflow
  3. Download .p8 file (Apple gives ONE chance — lose it, regenerate)
  4. Note Key ID + Issuer ID

After the owner has approved key creation and selected protected secret storage, configure the values through the approved EAS or CI secret mechanism. The following placeholders are illustrative; never paste real values into a repository, prompt, or log.

bash
eas secret:create --scope project --name ASC_KEY_ID --value "<key-id>"
eas secret:create --scope project --name ASC_ISSUER_ID --value "<issuer-id>"
eas secret:create --scope project --name ASC_KEY_BASE64 --type file --value "<path-outside-repository/AuthKey.p8>"

Manual signing (advanced)

Upload your own .p12 + .mobileprovision via eas credentials. Use when:

  • Multiple apps share one cert
  • You need a specific entitlement (App Groups, Push, custom)
  • Org security policy forbids EAS holding Apple credentials

Recovery from broken signing

bash
# Review the impact with the owner before removing any profile.
eas credentials  # → Build credentials → Remove provisioning profile

# Then, after separate build approval, trigger an interactive build to regenerate.
eas build --platform ios --profile production

Common errors

  • "Provisioning Profile expired" in CI → EAS won't auto-regenerate non-interactively. Run eas credentials locally to remove + rebuild interactively, then re-trigger CI.
  • "No profiles for X were found" with extension targets → set ios.bundleIdentifier per-target via config plugin, then eas credentials to generate per-target profiles.
  • "Cached profile without App Groups" → eas build --clear-cache + remove cached profile via eas credentials.

Certificate rotation

Distribution certs last 1 year. Provisioning profiles last 1 year. EAS auto-regenerates interactively. For CI, run eas credentials proactively a month before expiry.

Reference

references/02-eas-pipeline.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Code Signing AI skill do?

Manage iOS code signing: ASC API key, Distribution Certificate, Provisioning Profiles via EAS managed credentials. Use when the user says 'code signing', 'provisioning profile', 'distribution certificate', 'ASC API key'.

Why use Code Signing on TypingMind?

Because you install it once and use it with any model. Code Signing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Code Signing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/code-signing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Code Signing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Code Signing?

As many as you like. As long as a model supports skills, you can use Code Signing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Code Signing AI skill free?

Yes. It is published on GitHub by khadinakbarlabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
anthropics logo

Command Development

anthropics
OrganizationPopular

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create…

23.8K
146.3K
9 files
View
openclaw logo

Discord E2e

openclaw
OrganizationPopular

Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and…

82.2K
391K
4 files
View
openclaw logo

Openclaw Ghsa Maintainer

openclaw
OrganizationPopular

Inspect, patch, validate, publish, or confirm OpenClaw GHSA security advisories and private-fork state.

82.2K
391K
Instructions
View
openclaw logo

Openclaw Secret Scanning Maintainer

openclaw
OrganizationPopular

Triage, redact, clean up, and resolve OpenClaw GitHub Secret Scanning alerts in issues or PRs.

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇