add-native Skill
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps mo Published by microsoft in power-platform-skills.
What is add-native Skill?
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps mo Published by microsoft in power-platform-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use add-native Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/power-platform-skills
- Skill file: plugins/mobile-apps/skills/add-native/SKILL.md
What it does
Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps mo
Skill instructions
📋 Shared instructions: shared-instructions.md — read first. Add Native Capability Generate a one-file typed wrapper under src/native/ for a native device capability that the upstream template already ships. Screens import the wrapper instead of touching Expo modules directly, so the discriminated-union result contract stays consistent across the app. Hard rules — do NOT cross these lines 1. Never run npx expo install, npm install, or yarn add for a native module. The set of native modules in package.json is fixed by the upstream template. Adding a new one breaks the rewrap pipeline (the customer's binary is built from a pre-built base, not from their package.json). 2. Never edit app.config.js — plugins, ios.infoPlist, android.permissions, or anything else. All native config the template ships is intentional and signed off; arbitrary additions cannot be honored at rewrap time. 3. Never edit package.json dependencies for native modules (anything starting with expo-, react-native-, or th
Explore related resources
Frequently asked questions
What is add-native?
add-native is a open-source AI agent skill with Copy skill directory. Public entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, PDF generation/viewing.
Who is add-native best for?
add-native is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install add-native?
Install or run add-native using Copy skill directory. Check add-native for the latest setup command.
Is add-native actively maintained?
add-native may need a closer maintenance check before production use.
Auto-fetched from GitHub.
