Add App Clips

Community

khadinakbarlabs

add-app-clips

Plan and implement an iOS App Clip with preserved native work, validated invocation URLs and verified target constraints. Use for App Clips, QR/NFC launch, or lightweight app experiences.

Overview

Publisher	khadinakbarlabs
Repository	`expo-mobile-app-builder`
Skill name	`add-app-clips`
Stars	3
Forks	0
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

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.
1 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 Add App Clips AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/add-app-clips
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/add-app-clips

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/add-app-clips .claude/skills/add-app-clips

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Add App Clips 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 Add App Clips 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 Add App Clips 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.

Add an App Clip

Plan a small iOS App Clip for an owner-selected QR, NFC or URL entry point. Inspect the existing Expo SDK, Xcode project, targets and signing configuration. Use Apple's current documentation at https://developer.apple.com/documentation/appclip/creating-an-app-clip-with-xcode and the maintained Expo integration at https://github.com/EvanBacon/expo-apple-targets. Verify size and capability restrictions for the chosen deployment target instead of assuming a universal size limit.

Preserve the existing app

Review the current target configuration and native changes before proposing a dependency or prebuild. Present the exact compatible package version, files affected and regeneration risk. Follow existing user authorization for dependency changes; obtain missing authorization before installation or native regeneration. Do not automatically run a clean prebuild: it can overwrite native work. Use a recoverable snapshot and review the diff before adopting generated changes.

Create an App Clip target through the maintained package's documented target configuration, typically targets/clip/expo-target.config.js with type: 'clip', or the owner's Xcode workflow. Keep credentials, signing keys and provisioning material out of generated source and logs. Do not enable capabilities or change developer accounts silently.

Invocation and security

Prepare associated domains and an AASA document only for domains the owner controls. Reuse verified bundle/team identifiers; do not invent them. Publishing AASA files or configuring App Store Connect experiences requires the owner's authorization for those external changes.

Treat invocation URLs and parameters as untrusted input. Allow only documented HTTPS hosts, known paths and validated identifiers; reject unknown destinations. An App Clip must enforce ordinary authentication and authorization before account actions. Avoid sensitive values in URLs. Payment, location and other permission-dependent functionality needs its own approved flow; adding an App Clip does not authorize transactions or personal-data access.

Verification and handoff

Build the correct target and test valid/invalid invocation links, cold launch, denied permissions, offline behavior and the transition to the full app on a supported physical device. Measure the actual binary against the applicable Apple limit. Record entitlements, build evidence, unresolved errors and any domain/store step awaiting authorization. A local build does not prove App Store approval or a working production invocation.

Pair with add-expo-apple-targets, add-deep-links, code-signing and pre-submission-audit.

Bundled files

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

agents/openai.yaml1 KB

Frequently asked questions

What does the Add App Clips AI skill do?

Plan and implement an iOS App Clip with preserved native work, validated invocation URLs and verified target constraints. Use for App Clips, QR/NFC launch, or lightweight app experiences.

Why use Add App Clips on TypingMind?

Because you install it once and use it with any model. Add App Clips 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 Add App Clips in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/add-app-clips. 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 Add App Clips?

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 Add App Clips?

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

Is the Add App Clips 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.

View all

Gog

openclaw

OrganizationPopular

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Healthcheck

Audit/harden OpenClaw hosts: SSH, firewall, updates, exposure, backups, disk encryption, gateway security.

Change Impact

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths,…

Test Collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Add an App Clip

Preserve the existing app

Invocation and security

Verification and handoff

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now