Skip to content
TrustedSkillsbeta
Back to all skills

Install Flutter From Git

Checked
rodydavis·vlatest·frontend

Helps with Flutter, Git as part of building frontend UIs and user experiences workflows.

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 rodydavis/skills --skill install-flutter-from-git -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

rodydavis

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 rodydavis/skills at 804913dcbe.

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

Scanned
1 file, 119 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 enables AI agents to fetch and install specific versions of the Flutter SDK directly from Git repositories. It allows for bypassing standard package managers to access development snapshots or custom branches not available via stable releases.

When to use it

  • Installing bleeding-edge Flutter pre-release candidates (beta, dev, or master channels) for early feature testing.
  • Setting up a specific commit hash of the Flutter framework to ensure reproducible builds across a team.
  • Integrating custom Flutter forks or modified SDK versions maintained in private Git repositories.

Key capabilities

  • Direct cloning and installation from remote Git URLs instead of standard package mirrors.
  • Support for version pinning using Git tags, branches, or specific commit hashes.
  • Automated environment configuration to recognize the newly installed SDK path.

Example prompts

  • "Install Flutter from the 'beta' branch on GitHub."
  • "Set up a local development environment using the Flutter commit hash abcdef123456."
  • "Clone and configure a custom Flutter fork hosted at https://github.com/my-org/flutter-fork.git."

Tips & gotchas

Ensure your AI agent has write permissions to the target Git repository, as installation requires cloning source code. Be aware that installing from Git can lead to dependency conflicts if the specific version lacks compatibility with other installed tools or plugins.