Skip to content
TrustedSkillsbeta
Back to all skills

Analyze Rust Ffi Crate Surface

Checked
redisearch·vlatest·backend

Helps with analysis, Rust as part of developing backend services and APIs workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add redisearch/redisearch --skill analyze-rust-ffi-crate-surface -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

redisearch

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned redisearch/redisearch at c8f9d94e77.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c8f9d94e77
Manifest
.skills/analyze-rust-ffi-crate-surface/SKILL.md
Scanned
1 file, 37 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill analyzes Rust Foreign Function Interface (FFI) crates or files to identify C-visible symbols and determine their usage within a C codebase. It compiles a list of these symbols, such as functions annotated with #[unsafe(no_mangle)] or type definitions, and then identifies which modules in the C code utilize them. The skill leverages auto-generated header files for assistance when available.

When to use it

  • When integrating Rust code into existing C/C++ projects via FFI.
  • To understand how specific Rust functions or types are being used within a larger C codebase.
  • During refactoring or maintenance of systems that combine Rust and C components.
  • To verify the correctness of generated header files for FFI interfaces.

Key capabilities

  • Identifies C-visible symbols (functions, types) in Rust FFI crates/files.
  • Determines which modules in a C codebase use those symbols.
  • Generates reports detailing symbol name, usage module(s), and type.
  • Distinguishes between symbols used in production code versus unit tests.
  • Utilizes auto-generated header files (located in src/redisearch_rs/headers) for analysis.

Example prompts

  • "Analyze the numeric_range_tree_ffi crate to identify all exposed FFI symbols and their usage."
  • "What C modules use the function defined in src/redisearch_rs/c_entrypoint/some_file.rs?"
  • "Generate a report for the src/redisearch_rs/another_file.rs file, listing all FFI symbols and their usage locations."

Tips & gotchas

  • Paths to Rust files should typically start with src/. If not, the skill assumes they are located within the src/redisearch_rs/c_entrypoint directory.
  • If a directory is provided as input, the skill will review all Rust files within that directory.
  • Auto-generated header files in src/redisearch_rs/headers can be helpful resources during analysis.