New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Libreqos Packaging Release

by LibreQoE in LibreQoE/LibreQoS

Shared LibreQoS workflow for packaging, release, and shipped-file changes.

GPL-2.0Auto-check passed

Install Libreqos Packaging Release

skills CLI
$ npx skills add LibreQoE/LibreQoS --skill libreqos-packaging-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LibreQoE/LibreQoS libreqos-packaging-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LibreQoE/LibreQoS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/libreqos-packaging-release .claude/skills/libreqos-packaging-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
libreqos-packaging-release
GitHub stars
718
Token cost
~781 tokens
SKILL.md length
349 words
Files
3 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
GPL-2.0

At a glance

Shared LibreQoS workflow for packaging, release, and shipped-file changes.

  • Works in 6 steps: Read AGENTS.md first for current… → Identify every new or changed file the… → Review src/build_dpkg.sh and any related… → …
  • Changing src/builddpkg.sh
  • SKILL.md covers Scope, Invariants, Workflow and References, plus 3 more sections
  • Calls bash

What it does

Libreqos Packaging Release is an agent skill from LibreQoE/LibreQoS. Shared LibreQoS workflow for packaging, release, and shipped-file changes. Use when changing src/builddpkg.sh, src/buildrust.sh, src/rust/lqosd/copyfiles.sh, packaged binaries/assets/templates/service files, or any file that must exist on installed LibreQoS systems.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/package-surface.md`).

It works with Rust. The repository describes itself as: Self-hosted traffic management and network operations platform for ISPs. Use CAKE and fqcodel to reduce bufferbloat, enforce bandwidth plans, and troubleshoot congestion with… The licence is GPL-2.0.

When your agent uses it

  • Changing src/builddpkg.sh
  • Src/buildrust.sh
  • Src/rust/lqosd/copyfiles.sh
  • Packaged binaries/assets/templates/service files

Example prompts

  • “/libreqos-packaging-release”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md first for current packaging and safety rules.
  2. Identify every new or changed file the feature needs at runtime, install time, or service start time.
  3. Review src/build_dpkg.sh and any related copy/build helpers for the relevant copy/install path.
  4. Update the packaging/build scripts in the same change as the feature.
  5. If node_manager assets are involved, also review copy_files.sh, dev_build.sh, and the node_manager build contract.
  6. If install behavior or service expectations changed, update docs in the same change.

What it can do on your machine

Read from SKILL.md and the folder at commit 3eeaf94. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Libreqos Packaging Release loads about 781 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 349 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~781
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LibreQoE/LibreQoS at commit 3eeaf94, republished under its GPL-2.0 licence (© LibreQoE). 349 words, ~781 tokens.

Download SKILL.mdSave it as .claude/skills/libreqos-packaging-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
libreqos-packaging-release
description
Shared LibreQoS workflow for packaging, release, and shipped-file changes. Use when changing src/build_dpkg.sh, src/build_rust.sh, src/rust/lqosd/copy_files.sh, packaged binaries/assets/templates/service files, or any file that must exist on installed LibreQoS systems.

LibreQoS Packaging and Release

Use this skill for packaging and shipped-file work.

Scope

  • Packaging scripts: src/build_dpkg.sh, src/build_rust.sh
  • Node manager asset copy/build path: src/rust/lqosd/copy_files.sh, src/rust/lqosd/dev_build.sh
  • Files copied into installed layouts such as /opt/libreqos/src, /opt/libreqos/src/bin, /etc/systemd/system, and packaged static assets

Invariants

  • src/build_dpkg.sh is the functional source of truth for shipped .deb installs.
  • src/build_rust.sh and src/build_dpkg.sh should stay aligned where they overlap on binaries, static assets, helper scripts, and operator expectations.
  • If a change adds, renames, moves, or newly requires a shipped file, update packaging in the same change.
  • Never assume packaging will pick up a new file automatically. Verify the copy/install path explicitly.

Workflow

  1. Read AGENTS.md first for current packaging and safety rules.
  2. Identify every new or changed file the feature needs at runtime, install time, or service start time.
  3. Review src/build_dpkg.sh and any related copy/build helpers for the relevant copy/install path.
  4. Update the packaging/build scripts in the same change as the feature.
  5. If node_manager assets are involved, also review copy_files.sh, dev_build.sh, and the node_manager build contract.
  6. If install behavior or service expectations changed, update docs in the same change.

References

  • Read references/package-surface.md when deciding whether a file is part of the shipped install or where it is copied from.

Validation

  • Run bash -n on changed shell scripts.
  • If node_manager assets are involved, run src/rust/lqosd/src/node_manager/js_build/test-build-contract.sh.
  • After any repo change, invoke heckler via $libreqos-review-subagents-workflow before returning to the user.
  • After each source-code implementation batch, also invoke reaper via $libreqos-review-subagents-workflow.
  • During large sessions, invoke $libreqos-review-subagents-workflow (and helen if UI changed).
  • If you did not run a full package build, say so explicitly.
  • Before finishing, answer this directly: "Does src/build_dpkg.sh include every new required file?"

High-Risk Changes

  • Service files and post-install behavior
  • Static assets copied through intermediate build helpers
  • Python/Rust files that work in-repo but are missing from the installed package
  • update_api.sh / lqos_api packaging behavior
  • Any change that assumes /opt/libreqos/src contains files that packaging does not copy

Notes

  • Package-content drift is a recurring failure mode in this repo.
  • src/build_rust.sh can restart services on the local host; treat it as an operationally sensitive script, not a harmless build helper.

© LibreQoE, GPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/libreqos-packaging-release of LibreQoE/LibreQoS.

  • SKILL.md
  • agents/openai.yaml
  • references/package-surface.md

Open the folder on GitHubat commit 3eeaf94

Compare with similar skills

Libreqos Packaging Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Libreqos Packaging Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Libreqos Packaging Release this skillLibreQoE/LibreQoS718—~781Automated safety check: PassGPL-2.0
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0
Firecrawl Page Scrape Integrationfirecrawl/firecrawl189k1 repos~944Automated safety check: PassISC
Migrate Core Code to Submodulestinyhumansai/openhuman41k—~2.6kAutomated safety check: PassGPL-3.0
Rust TDD Workflowrtk-ai/rtk83k—~753Automated safety check: NotesApache-2.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Firecrawl Page Scrape Integration

    firecrawl/firecrawl

    Adds Firecrawl's /scrape endpoint to application code to pull markdown, HTML, links, screenshots or structured data from a single known URL.

    189k GitHub starsUsed in 1 repo~944 tokens
    Data & AnalyticsAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    41k GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Rust TDD Workflow

    rtk-ai/rtk

    Enforces red-green-refactor for Rust work, with idiomatic test patterns, a naming convention and a pre-commit gate of cargo fmt, clippy and test.

    83k GitHub stars~753 tokensUpdated today
    Testing & QAAuto-check: notes

  • Rust Best Practices

    farm-fe/farm

    Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated 4 days ago
    DevelopmentAuto-check: notes

More from LibreQoE/LibreQoS

All 8 skills in this repo

  • Libreqos Review Subagents Workflow

    LibreQoE/LibreQoS

    Project workflow for invoking the local review sub-agents Thomas, Helen, Beck, Jonas, The Reaper, and Heckler during LibreQoS coding sessions.

    718 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Anti Slop

    LibreQoE/LibreQoS

    Anti-slop workflow for LibreQoS. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~820 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Python Workflow

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for Python orchestration, scheduler, integrations, and helper scripts under src/.

    718 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Git Workflow

    LibreQoE/LibreQoS

    Shared LibreQoS git workflow. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~479 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Lqos Sys Ebpf

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for lqossys eBPF, C wrapper, bindgen, and pinned-map ABI work.

    718 GitHub stars~793 tokensUpdated 3 days ago
    Auto-check passed

  • Libreqos Node Manager Frontend

    LibreQoE/LibreQoS

    Shared LibreQoS workflow for nodemanager frontend work. An agent skill from LibreQoE/LibreQoS.

    718 GitHub stars~915 tokensUpdated 3 days ago
    Auto-check passed

Works with

Questions about Libreqos Packaging Release

What does Libreqos Packaging Release do?

Shared LibreQoS workflow for packaging, release, and shipped-file changes. Libreqos Packaging Release is an agent skill from LibreQoE/LibreQoS. Shared LibreQoS workflow for packaging, release, and shipped-file changes.

When should I use Libreqos Packaging Release?

Libreqos Packaging Release fits situations like: changing src/builddpkg.sh; src/buildrust.sh; src/rust/lqosd/copyfiles.sh; packaged binaries/assets/templates/service files.

How do I install Libreqos Packaging Release in Claude Code?

Run `npx skills add LibreQoE/LibreQoS --skill libreqos-packaging-release -a claude-code`. Or copy the skill folder (.agents/skills/libreqos-packaging-release in LibreQoE/LibreQoS) into .claude/skills/libreqos-packaging-release in your project. Claude Code loads it when a task matches its description.

How do I install Libreqos Packaging Release in Codex?

Run `npx skills add LibreQoE/LibreQoS --skill libreqos-packaging-release -a codex`. Or copy the skill folder (.agents/skills/libreqos-packaging-release in LibreQoE/LibreQoS) into .agents/skills/libreqos-packaging-release in your project. Codex loads it when a task matches its description.

Can I use Libreqos Packaging Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LibreQoE/LibreQoS --skill libreqos-packaging-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/libreqos-packaging-release, .gemini/skills/libreqos-packaging-release, .github/skills/libreqos-packaging-release and .opencode/skills/libreqos-packaging-release in your project.

What does Libreqos Packaging Release need to run?

Going by SKILL.md and its folder, Libreqos Packaging Release needs the command-line tools its instructions call (bash).

Does Libreqos Packaging Release access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Libreqos Packaging Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Libreqos Packaging Release use?

Libreqos Packaging Release is published under the GPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Libreqos Packaging Release use?

About 781 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 426 tokens, read only when the agent opens those files.

What are the alternatives to Libreqos Packaging Release?

Skills that share tags, products or a category with Libreqos Packaging Release: Update V8 Version (openinterpreter/openinterpreter, 69k stars), Firecrawl Page Scrape Integration (firecrawl/firecrawl, 189k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 41k stars) and Rust TDD Workflow (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Libreqos Packaging Release?

LibreQoE (a GitHub organization) maintains it in LibreQoE/LibreQoS, which has 718 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 4, 2026.

Source: LibreQoE/LibreQoS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.