Build Rust Native Libraries for FFI Plugin

VerifiedSafe

Build the Rust native libraries for the keychat_rust_ffi_plugin. Supports iOS, Android, Linux, Windows, macOS.

Sby Skills Guide Bot
DevelopmentIntermediate
7/22/2026
Claude Code
#rust#ffi#cross-compilation#flutter-rust-bridge#mobile-build

Recommended for

Automated summary

Builds the keychat_rust_ffi_plugin Rust native libraries for a chosen target platform (iOS, Android, Linux, Windows, macOS) using rustup and cargo, and points to the Dart binding regeneration step.

Strengths

  • Clear table mapping each platform to its rustup target triple and cargo build --release command
  • Documents prerequisites, including the pinned flutter_rust_bridge_codegen 2.11.1 install and Linux system packages (protobuf-compiler, libsecret-1-dev)
  • Also covers regenerating Dart bindings after Rust API changes
  • Narrow allowed-tools scope limited to cargo and rustup commands

Limitations

  • Only one architecture per platform (aarch64): no universal/fat binaries and no x86_64 simulator target for iOS
  • Assumes a fixed project layout (packages/keychat_rust_ffi_plugin/rust), so it is not portable to other repositories as-is
  • Does not cover copying artifacts into Xcode/Gradle, code signing, or distribution
When to use it

Use it when you need to produce the plugin's native Rust binary for a specific platform before testing or packaging the Flutter app.

When not to use it

Don't use it if you need multi-architecture builds, simulator targets, or want to build a Rust project other than this specific FFI plugin.

Security analysis

Safe
Quality score90/100

The skill only contains standard build commands using cargo and rustup, which are legitimate development tools. It does not include destructive operations, network exfiltration, obfuscated payloads, or disabling of safety features. The apt install line is for normal system dependencies and is not inherently risky.

No concerns found

How this analysis is made

Examples

Build for Android
Build the keychat_rust_ffi_plugin Rust library for android
Build for iOS
Compile the Rust FFI native library for iOS in release mode
Regenerate bindings
I changed the Rust API in the FFI plugin — regenerate the flutter_rust_bridge Dart bindings

name: rust-build description: Build Rust native libraries for the FFI plugin argument-hint: "[target]" disable-model-invocation: true allowed-tools: Bash(cargo *), Bash(rustup *)

Build the Rust native libraries for the keychat_rust_ffi_plugin.

Arguments

  • $ARGUMENTS - Target platform: ios, android, linux, windows, macos

Prerequisites

Ensure flutter_rust_bridge codegen is installed:

cargo install flutter_rust_bridge_codegen@2.11.1

For Linux, install system dependencies:

apt install protobuf-compiler libsecret-1-dev

Target Setup and Build Commands

| Platform | Target | Setup & Build | |----------|--------|---------------| | iOS | aarch64-apple-ios | rustup target add aarch64-apple-ios && cargo build --target aarch64-apple-ios --release | | Android | aarch64-linux-android | rustup target add aarch64-linux-android && cargo build --target aarch64-linux-android --release | | Linux | x86_64-unknown-linux-gnu | rustup target add x86_64-unknown-linux-gnu && cargo build --target x86_64-unknown-linux-gnu --release | | Windows | x86_64-pc-windows-msvc | rustup target add x86_64-pc-windows-msvc && cargo build --target x86_64-pc-windows-msvc --release | | macOS | aarch64-apple-darwin | rustup target add aarch64-apple-darwin && cargo build --target aarch64-apple-darwin --release |

Workflow

  1. Change to the Rust plugin directory:

    cd packages/keychat_rust_ffi_plugin/rust
    
  2. If no target specified, ask which platform to build for

  3. Add the rustup target if not already added:

    rustup target add <target>
    
  4. Build the library:

    cargo build --target <target> --release --target-dir target
    
  5. Report build success or any errors

Regenerating Dart Bindings

After modifying Rust API files, regenerate the Dart bindings:

cd packages/keychat_rust_ffi_plugin
flutter_rust_bridge_codegen generate

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/build-rust-native-libraries-for-ffi-plugin-mrwak95z/download' --output '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md.part' && mv '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md.part' '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(cargo *), Bash(rustup *)

Original excerpt: Prerequisites

Ensure flutter_rust_bridge codegen is installed:

cargo install flutter_rust_bridge_codegen@2.11.1

For Linux, install system dependencies:

apt install protobuf-compiler libsecret-1-dev

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md' && test -s '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/rust-build' && cp -R '.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z' '.claude/skills/rust-build'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z'

openskills read 'build-rust-native-libraries-for-ffi-plugin-mrwak95z'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/build-rust-native-libraries-for-ffi-plugin-mrwak95z/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills