Skip to content

Development skills

Browse reusable Agent Skills, each with a clear purpose and practical guidance.

libreyolo-add-task

Add a new task type to LibreYOLO (a new output kind like detect, segment, semantic, pose, classify, gaze, obb, point, depth, restore), as opposed to adding a model family to an existing task. Use when someone proposes a new capability that no current task's result/label/metric contract fits, e.g. "add OCR", "add 3D boxes", "add image enhancement as a task". Covers the decision (new task vs existing task), and the full wiring checklist: tasks.py registration, the Results payload class, dataset loader + schema, validator, trainer support, filename suffix, docs/ADR, and the tests that gate each piece. For porting a model into an existing task use libreyolo-port-model.

493 repo stars36 repo forks

Development

libreyolo-api-conventions

The rules every user-facing LibreYOLO surface must follow (Python API, CLI, dataset YAMLs, metric keys, Results fields) and the safe method for checking parity with the de-facto YOLO ecosystem conventions. Use when designing or reviewing any new public API, CLI command or flag, train/val kwargs, metric names, or Results attributes; when someone asks "what should this be called?", "should predict return a list?", or "is this compatible with standard YOLO tooling?"; or when an API-parity gap is reported. Encodes the AGENTS.md rule that user-facing APIs follow the ecosystem standard, and the license-safe way to verify that (docs only, never source).

493 repo stars36 repo forks

Development

libreyolo-export-formats

Work on LibreYOLO's export subsystem: debug a failing export, fix an exported model that predicts differently from the .pt, extend a format's coverage to a new family/task, or add a new export format. Use when someone reports "export to X fails", "the ONNX/TensorRT model gives different results", asks which formats a family supports, or wants a new format wired. Covers the exporter/backend twin architecture, the metadata round-trip contract, per-format quirks and extras, the parity-testing method, and the support-claim bar. For a user just running export, see use-libreyolo; for Hailo specifically, libreyolo-export-hailo.

493 repo stars36 repo forks

Development

libreyolo-port-model

Port a model into LibreYOLO. Executable guide — finds your closest existing family to clone, gives paste-ready templates for the model class, conversion script, runtime auto-convert recognizer, and trainer subclass, then walks the port as a sequence of self-contained commits. Covers detection, pose, and segmentation in depth; routes classify / semantic / depth / restore / point / gaze ports to their merged exemplar families. Use this for any new family (RTMO, MobileDet, PP-YOLOE, a new HF model).

493 repo stars36 repo forks

Development

libreyolo-upload-hf-model

Prepare and upload a LibreYOLO weight repo to the HuggingFace LibreYOLO org. Use when publishing new weights (new family, new size, or new task like -seg). Covers filename, README, LICENSE, NOTICE, and collection membership.

493 repo stars36 repo forks

Development

merge-to-dev

The whole dance for landing code on LibreYOLO's dev branch: branch, commit, push to upstream, then hand the user a one-click compare URL that opens an empty PR form for them to submit (agents must not open the PR themselves), and once they have opened it, babysit the Greptile bot review until it is happy. Use whenever the user says "put this on dev", "push this to dev", "merge this to dev", "ship this", "open a PR for this", or hands over finished work on LibreYOLO/libreyolo. The user should never have to ask for the PR link; producing it is the task.

493 repo stars36 repo forks

Development

pst-codebase

PalworldSaveTools (PST) architecture map — repo layout, entry chain, the palsav SAV<->GVAS<->JSON pipeline, the palworld_aio GUI structure, game data locations, and the custom pytest dynamic-import registry. Load FIRST whenever working anywhere in this repo so you orient on real structure, not guesses.

493 repo stars47 repo forks

Development

pst-game-data

Schemas of all 11 resources/game_data/*.json files, the 6 app config presets in src/data/configs/, the i18n system (8 languages, t() lookup, English fallback), the resources/assets directory layout, and resource resolution (dev vs frozen builds). Load when editing game data, configs, i18n, or asset paths.

493 repo stars47 repo forks

Development

pst-pal-editor

The pal editing engine — pal data model (every SaveParameter field with type-wrapper shapes), editing operations, illegal pal detection, pal generation, container/slot model, game data binding, and the PalEditorWidget UI. Previously the monolithic `edit_pals.py` (5454 lines), now a modular `pal_editor/` package (17 modules + backward-compat `edit_pals.py` shim). Load when editing pal logic, stats, skills, IVs, containers, or illegal detection.

493 repo stars47 repo forks

Development

pst-ui-tabs

Every UI tab, dialog, and reusable widget in palworld_aio/ui/ and widgets/, plus the map rendering pipeline (MapGraphicsView/markers/items/effects). Load when editing UI, tabs, dialogs, the map, or Qt styling.

493 repo stars47 repo forks

Development