> vosslab/vosslab-skills

> arch-docs

Create or update docs/CODE_ARCHITECTURE.md and docs/FILE_STRUCTURE.md by inspecting a repo. Use when asked to document or refresh repository architecture, file layout, or structure docs based on current contents.

> bptools-writer

Create, edit, and validate biology-problems bptools Python question generators and supporting YAML content. Use when requests involve authoring question scripts, updating files under problems/*-problems, tuning randomization or anti-cheat behavior, or debugging BBQ/QTI output that depends on bptools.py and qti_package_maker.

> computer-vision-expert

Design, implement, debug, and review computer vision systems in Python, including image processing, detection, segmentation, classification, tracking, OCR, camera pipelines, and dataset-driven evaluation. Use when working with OpenCV, PyTorch vision models, video/image analysis, model-selection tradeoffs, annotation strategy, failure analysis, or CV performance and robustness problems.

> docset-refresh

Audit and refresh repo documentation sets against docs/REPO_STYLE.md, create missing docs only when supported by evidence, keep ALL CAPS doc naming under docs, and report created, updated, flagged, and known gaps.

> gas-town-workflow

Gas Town style multi-agent coordination with role-mapped task routing and convoy-based work decomposition. Use when the user explicitly requests Gas Town workflow, convoy-style task decomposition, theatrical role-mapped coordination, or this repo's specific agent role system. Do not trigger on generic multi-agent or parallel task requests.

> install-usage-docs

Create or refresh minimal docs/INSTALL.md and docs/USAGE.md stubs from repo evidence. Use when these docs are missing, too thin, or stale.

> manager-make-new-plan

Create forward-looking implementation plans from scratch for coding teams without writing code. Use when the user needs a new plan document, major rewrite, milestone restructuring, acceptance gates, migration strategy, risk handling, or rollout planning for future work; do not use this skill for post-implementation audits of an existing plan.

> manager-review-existing-plan

Review a specific existing implementation plan and verify whether code and tests actually satisfy the plan's goals, sequencing, and gates. Use when the user asks for plan quality review, closure validation, implementation-to-plan conformance, risk gap analysis, or go/no-go readiness on an existing plan document.

> orchestrate-next-milestone

Implement the manager-prioritized milestone of an existing plan and carry it to closure, including adjacent fixes needed to pass gates and close the milestone cleanly. Use when a manager/reviewer says to start the next milestone and expects end-to-end delivery with evidence.

> parallel-plan

Lightweight parallelization nudge for active tasks: split work so one agent does not carry everything. Use when a request has separable tracks, can benefit from help/subagents, or risks stalling in a single linear pass. Skip this skill for tightly coupled single-file edits.

> parallel-web-game-build

Use when building a single-file web game or interactive web app from modular source files using parallel agents. Use when the output is one HTML file assembled from parts via a build script, and multiple agents will write code concurrently.

> pdf

Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.

> pyside6-ui-engineer

Design, implement, refactor, and review PySide6 desktop applications with strong widget architecture, signal-slot design, state flow, and expert UI/UX logic. Use when building or fixing Qt for Python windows, dialogs, forms, navigation shells, model-view tables, theming, validation, accessibility, or interaction polish in Python GUI code.

> python-code-review

Comprehensive Python code review focused on bugs, correctness, security, maintainability, and actionable fixes. Use when a user asks for a review of Python files, wants severity-rated findings, wants before/after fix suggestions, or wants verification that implementation matches an active plan document (if one exists). Start by applying read-repo-rules to AGENTS.md, docs/REPO_STYLE.md, docs/PYTHON_STYLE.md, and docs/CHANGELOG.md so review guidance follows repository rules.

> readme-fix

Standardize README.md to match repo conventions. Brief purpose, quick start, and links to docs/. Keep content verifiable, concise, and ASCII. Use when README.md drifted or is missing key pointers.

> read-repo-rules

Read specified repo rule files (AGENTS.md, docs/REPO_STYLE.md, docs/PYTHON_STYLE.md, docs/CHANGELOG.md) and return one-sentence summaries in a strict four-line format, including missing-file handling and no recursive listings. For docs/CHANGELOG.md, summarize only the latest dated entry instead of the full file. Use when a prompt asks for structured summaries of repo instruction files with exact output lines or similar constraints.

> skill-writing-guide

Guide for authoring Agent Skills (SKILL.md). Covers the open standard format, required frontmatter, directory layout, progressive disclosure, description writing, and best practices. Use when creating a new skill, improving an existing skill, or learning how skills work.

> unit-test-starter

Generate thorough Python 3 pytest unit tests across a repo by scanning every *.py file and each function, writing one test module per source file while skipping IO/network behavior and documenting gaps.

> webwork-writer

Create, edit, and lint WeBWorK PG/PGML questions following docs/webwork guidance, HTML whitelist constraints, and renderer-based lint checks. Use for tasks like authoring new PGML problems, adjusting randomization or grading, fixing PGML rendering issues, and running renderer API linting.