Run any Skill in Manus with one click

downspout-release-catalog

Stars5

Forks1

UpdatedJuly 7, 2026 at 12:17

Maintain downspout release packaging, install scripts, GitHub Actions release assets, screenshots, and GitHub Pages plugin catalog metadata. Use when Codex changes plugin bundle lists, adds/removes public plugins, edits docs/pages products, or updates screenshot/release workflows.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

danja

danja/downspout

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	downspout-release-catalog
description	Maintain downspout release packaging, install scripts, GitHub Actions release assets, screenshots, and GitHub Pages plugin catalog metadata. Use when Codex changes plugin bundle lists, adds/removes public plugins, edits docs/pages products, or updates screenshot/release workflows.

Downspout Release Catalog

Use this skill when bundle lists, release packaging, install behavior, screenshots, or Pages product metadata might be affected.

Release/package checklist

Compare plugin-local CMake install declarations with scripts/package-release.sh expected bundles.
Keep install.sh build options aligned with root CMakeLists.txt plugin options.
Keep release docs aligned with actual package contents.
Update .github/workflows/release.yml when platform artifact or bundle assumptions change.
Run syntax checks for changed shell scripts and workflow checks where available.

Pages/screenshot checklist

Ensure every public plugin has docs/pages/_products/<plugin>.md front matter.
Ensure each product references an existing docs/pages/assets/plugins/<plugin>.png screenshot.
Ensure scripts/capture-plugin-screenshots.sh --list includes the plugin when screenshots are expected.
Regenerate screenshots when UI appearance changes and the required local tools are available.
Update docs/screenshots.md and docs/pages/README.md only when the process changes.

Read references/release-catalog.md for commands and expected file relationships.

More from this repository

same repository

downspout-build-test

danja/downspout

Build, test, and verify downspout plugins and core targets. Use when Codex needs to configure CMake, build a plugin or test target, run CTest/core tests, choose narrow verification for a change, or avoid known downspout build-directory races.

2026-07-175

reaper-compose

danja/downspout

Compose, arrange, mix, save, and verify original music in a connected REAPER session through REAPER MCP. Use for requests to create songs, instrumentals, MIDI arrangements, plugin-based productions, or reusable DAW composition recipes, especially when Downspout VST3 instruments and effects are available.

2026-07-125

downspout-add-plugin

danja/downspout

Add a new downspout plugin end to end. Use when Codex is asked to scaffold or port a plugin under the plugins directory and must keep CMake, install, release packaging, docs, screenshots, and GitHub Pages catalog entries synchronized.

2026-07-075

downspout-extend-plugin

danja/downspout

Extend or modify behavior in an existing downspout plugin. Use when Codex is asked to add controls, DSP or MIDI behavior, transport/state handling, serialization, UI elements, or tests inside a plugin directory while preserving the portable-core plus thin-DPF-wrapper architecture.

2026-07-075

name	downspout-release-catalog
description	Maintain downspout release packaging, install scripts, GitHub Actions release assets, screenshots, and GitHub Pages plugin catalog metadata. Use when Codex changes plugin bundle lists, adds/removes public plugins, edits docs/pages products, or updates screenshot/release workflows.

Downspout Release Catalog

Use this skill when bundle lists, release packaging, install behavior, screenshots, or Pages product metadata might be affected.

Release/package checklist

Compare plugin-local CMake install declarations with scripts/package-release.sh expected bundles.
Keep install.sh build options aligned with root CMakeLists.txt plugin options.
Keep release docs aligned with actual package contents.
Update .github/workflows/release.yml when platform artifact or bundle assumptions change.
Run syntax checks for changed shell scripts and workflow checks where available.

Pages/screenshot checklist

Ensure every public plugin has docs/pages/_products/<plugin>.md front matter.
Ensure each product references an existing docs/pages/assets/plugins/<plugin>.png screenshot.
Ensure scripts/capture-plugin-screenshots.sh --list includes the plugin when screenshots are expected.
Regenerate screenshots when UI appearance changes and the required local tools are available.
Update docs/screenshots.md and docs/pages/README.md only when the process changes.

Read references/release-catalog.md for commands and expected file relationships.