Tencent SkillHub · Developer Tools

Fly.io CLI

Use the Fly.io flyctl CLI for deploying and operating apps on Fly.io. Default to read-only diagnostics (status/logs/config/releases). Only perform state-changing operations (deploys, SSH exec, secrets, scaling, machines, volumes, Postgres changes) with explicit user approval. Use when asked to deploy to Fly.io, debug fly deploy/build/runtime failures, set up GitHub Actions deploys/previews, or safely manage Fly apps and Postgres.

skill openclawclawhub Free

0 Downloads

0 Stars

0 Installs

0 Score

High Signal

⬇ 0 downloads ★ 0 stars Unverified but indexed

Install for OpenClaw

Quick setup

Download the package from Yavira.
Extract the archive and review SKILL.md first.
Import or place the package into your OpenClaw setup.

Requirements

Target platform: OpenClaw
Install method: Manual import
Extraction: Extract archive
Prerequisites: OpenClaw
Primary doc: SKILL.md

Package facts

Download mode: Yavira redirect
Package format: ZIP package
Source platform: Tencent SkillHub
What's included: references/safety.md, references/github-actions.md, references/rails-docker-builds.md, scripts/fly_app_from_toml.sh, SKILL.md

Validation

Use the Yavira download entry.
Review SKILL.md after the package is downloaded.
Confirm the extracted package contains the expected setup assets.

Install with your agent

Agent handoff

Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.

Download the package from Yavira.
Extract it into a folder your agent can access.
Paste one of the prompts below and point your agent at the extracted folder.

New install

I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.

Upgrade existing

I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.

Open Send to Agent page Open JSON manifest Open Markdown brief

Trust & source

Release facts

Source: Tencent SkillHub
Verification: Indexed source record
Version: 1.0.3

Provenance

Publisher: justinburdett
Source page: View original listing
Canonical URL: Open canonical page

Documentation

ClawHub primary doc Primary doc: SKILL.md 13 sections Open source page

Fly.io (flyctl) CLI

Operate Fly.io apps safely and repeatably with flyctl.

Defaults / safety

Prefer read-only commands first: fly status, fly logs, fly config show, fly releases, fly secrets list. Do not edit/modify Fly.io apps, machines, secrets, volumes, or databases without your human’s explicit approval. Read-only actions are OK without approval. Destructive actions (destroy/drop) always require explicit approval. When debugging builds, capture the exact error output and determine whether it’s a: build/packaging issue (Dockerfile, Gemfile.lock platforms, assets precompile) runtime issue (secrets, DB, migrations) platform issue (regions, machines, health checks)

Quick start (typical deploy)

From the app repo directory: Confirm which app you’re targeting fly app list fly status -a <app> Check fly.toml for app = "..." Validate / inspect (read-only) fly status -a <app> fly logs -a <app> fly config show -a <app> (Deploys are in High-risk operations below and require explicit user approval.)

Common checks

fly deploy --verbose (more build logs) If using Dockerfile builds: verify Dockerfile Ruby/version and Gemfile.lock platforms match your builder OS/arch.

Rails + Docker + native gems (nokogiri, pg, etc.)

Symptoms: Bundler can’t find a platform gem like nokogiri-…-x86_64-linux during build. Fix pattern: Ensure Gemfile.lock includes the Linux platform used by Fly’s builder (usually x86_64-linux). Example: bundle lock --add-platform x86_64-linux Ensure Dockerfile’s Ruby version matches .ruby-version. (See references/rails-docker-builds.md.)

Logs & config (read-only)

Stream logs: fly logs -a <app> Show config: fly config show -a <app> List secrets (names only): fly secrets list -a <app>

High-risk operations (ask first)

These commands can execute arbitrary code on servers or mutate production state. Only run them when the user explicitly asks you to. Deploy: fly deploy / fly deploy --remote-only SSH exec / console: fly ssh console -a <app> -C "<command>" Secrets changes: fly secrets set -a <app> KEY=value See references/safety.md.

Identify the Postgres app

fly postgres list

Attach Postgres to an app

fly postgres attach <pg-app> -a <app>

Create a database inside the cluster

fly postgres db create <db_name> -a <pg-app> fly postgres db list -a <pg-app>

Connect (psql)

fly postgres connect -a <pg-app>

GitHub Actions deploys / previews

For production CD: use Fly’s GitHub Action (superfly/flyctl-actions/setup-flyctl) and run flyctl deploy. For PR previews: Prefer one preview app per PR and one database per PR inside a shared Fly Postgres cluster. Automate create/deploy/comment on PR; destroy on close. (See references/github-actions.md.)

Bundled resources

references/safety.md: safety rules (read-only by default; ask before mutating state). references/rails-docker-builds.md: Rails/Docker/Fly build failure patterns + fixes. references/github-actions.md: Fly deploy + preview workflows. scripts/fly_app_from_toml.sh: tiny helper to print the Fly app name from fly.toml (shell-only; no ruby).

Category context

Code helpers, APIs, CLIs, browser automation, testing, and developer operations.

Source: Tencent SkillHub

Largest current source with strong distribution and engagement signals.

Package contents

Included in package

4 Docs1 Scripts

SKILL.md Primary doc
references/github-actions.md Docs
references/rails-docker-builds.md Docs
references/safety.md Docs
scripts/fly_app_from_toml.sh Scripts