More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    ChipTune Pro

    1

    Seamless loops, adaptive layers, stems, MIDI in and out, character voices, reference track analysis, a sound-effect library and mastering that sounds finished. Python + numpy, no samples, any engine.

    $14.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    ChipTune Pro

    ChipTune Pro

    Example session with this skill installed

    Cozy game about running a little café on a rainy street. I want a lo-fi hip hop loop for the café during the day and a slower jazzy loop for after closing, both swung and loose, like a person played them, not a grid.
    Add a rainy-street ambience bed that loops seamlessly to run under both, and a few café sounds: a cup set down on a saucer, the door bell when a customer comes in, and a coin dropped in the tip jar. Put everything in ./audio and keep the loudness even.
    Cozy game about running a little café on a rainy street. I want a lo-fi hip hop loop for the café during the day and a slower jazzy loop for after closing, both swung and loose, like a person played them, not a grid. Add a rainy-street ambience bed that loops seamlessly to run under both, and a few café sounds: a cup set down on a saucer, the door bell when a customer comes in, and a coin dropped in the tip jar.
    Put everything in ./audio and keep the loudness even.

    • Read your context and instructions
    • Compiled the chiptune pro
    • cafe_day.wav: a lo-fi beat at 90 bpm, a worn electric piano over its own chord stabs, a sine bass, a soft 808 kick, a snare that drags 30 ms behind the beat, tape hiss. 42.7 s loop, −16 LUFS.
    • cafe_night.wav: a late-night piano trio at 60 bpm, piano melody, Rhodes comping, a walking upright, brushes and a ride. 64 s loop, −16 LUFS. Both loops share a five-note motif and are swung and humanised, in the MIDI too.
    • A one-bar transition each way, with the second the next loop starts at.
    • bed_rainy_street.wav: 30 s of stereo rain, distant traffic and drips off the awning, its loop points in the file, 8 LU under the music.
    • cup_saucer.wav, door_bell.wav, tip_jar_coin.wav, within 0.3 dB of each other, with a command for three takes of each.
    • tools/audio/: the generators, the MIDI, piano rolls, spectrograms and a report (lint clean on both loops), and a reply that marks every decision the agent made on its own and says it could not listen.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Give your game a finished soundtrack without a composer, samples or a DAW. ChipTune Pro is a score/kit tracker in Python with numpy: a Score is the composition, a Kit is the instruments, and the same score renders through 15 kits: NES, SNES, Genesis, Game Boy, C64, arcade FM, Amiga and PC speaker, plus synthwave, lo-fi, lo-fi hip hop, orchestral, jazz and acoustic. Graybox first, dress later, MIDI as the proof the tune did not change.

    What makes it Pro: the agent can check what it cannot hear. It draws piano rolls and spectrograms, measures LUFS and true peak, lints a score (range, leaps, drones, the wrap on a downbeat, the NES and Game Boy channel budgets) and a mix (is the lead masked by the pad, is the low end mud, does it survive mono, does the kick sit under the snare, where a drum has room), and writes a soundtrack report that proves six cues share a motif and sit within 2 dB of each other.

    • Finished loops: compressor, sidechain ducking, per-part EQ, era "finish" presets, swing, accents, humanised timing, drum fills, automation lanes.
    • Song form: intro / loop / outro files, sections, bar-aligned transitions between cues, loop points in the file (WAV smpl, Vorbis LOOPSTART) for engines that read them.
    • Adaptive music: stems per part or group and intensity layers that stack sample-aligned, with a manifest and runtime snippets for Web Audio, Unity, Godot, Decentraland and AGS.
    • A clean mix by default: every dressed cue gets a mixing pass with one part per band, the kick giving way to the snare, cuts before boosts and drive on one or two parts, each default tied to the line that measures it.
    • Your tune in: import a MIDI file as a score, quantised and named by part, detect its chords, add the bass and drums, render it through any kit.
    • A reference track for inspiration: bring a WAV or MP3 you love and chip.py analyze measures its style (the tempo to 0.01 bpm and the bar line, the feel, the drum grids, the key, the note that makes its scale (a harmonic minor's raised seventh) and a chord per bar, the form, the balance, width and loudness) into a brief, and says plainly what it could not read instead of guessing; the agent writes an original track to it, --against compares the render with the reference, and --reference checks every cue's melody against the reference's lead, so a quoted phrase is caught and rewritten. The style is taken, never the melody.
    • Your drum samples: bring a pack of one-shots (kick, snare, hats, crash) and the kit plays them in place of the synthesised drums, at any sample rate (WAV, FLAC, OGG or MP3), with the same EQ, compression, ducking and stems as any part; the composition and its MIDI do not change. No pack? Ask for sampled drums and the agent fetches CC0 one-shots, auditions them by measurement and writes each one's source, license and credits beside it.
    • Voices: vowel and formant voices, gibberish dialogue per character (child, giant, robot, elder), choirs.
    • Sound effects: 101 parametrised generators in families (UI, impacts by material, footsteps by surface, weapons, magic, creatures, pickups, doors, machines, water, fire, weather, arcade hits) with seeded variation sets, plus ambience bed presets.
    • Two complete example soundtracks (an 8-bit action game, a 16-bit mystery) with cue sheets, stems and effects, as the model for yours.

    Everything is synthesised, so there is nothing to clear: the audio, MIDI and scripts you make are yours (a reference track lends its measurements, not its notes; a drum pack you bring stays under its own license). Engine-agnostic: WAV and OGG output plus MIDI. The scripts make no network calls and no obfuscated code; asked for sampled drums when you have no pack, the agent downloads CC0 one-shots with its own tools and records each file's source and license beside it.

    Earlier versions of this skill (up to 0.1.1) were released under MIT in pravusjif/pravus-ags-mcp and remain free there. ChipTune Pro is its maintained successor; you pay for what was added since and for future versions, which are included. One license per person; commercial use and public repositories allowed; see LICENSE.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Game Development.

    • The agent cannot hear. Everything it checks is measured, and every reply lists what only an ear can settle: listen before you ship.
    • Synthesised, not sampled: the orchestral and jazz kits are convincing sketches, not a sample library. Samples of your own play as drums (one-shots, at any sample rate); there is no sampled instrument that plays a melody.
    • analyze reads a reference's style, and of its melody only enough to catch a quote, not a transcription; it says "not read" or "unsure" where it cannot tell (a swing under noisy hats, a snare under a melody, the bar line of a dense arrangement).
    • The engine snippets (Unity, Godot, Decentraland, AGS) are compiled or parsed by tooling, not played in each engine; the Web Audio one has run in headless Chrome.
    • Rendering runs on the CPU: a 30 s jazz loop takes about 4 s on a laptop, 40 s of a dense orchestral cue about 20s, and the agent's checks (lint, rolls, reports) add to that.
    • Levels are set for a game (−16 LUFS for loops), quieter than commercial releases on purpose, so effects and dialogue fit on top.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed today

    Software
    Python 3.9 or laterAgs MCPGit

    No API keys, no accounts, no GPU, no network, no samples or asset packs needed. Only when you ask for sampled drums and have no pack does the agent download CC0 one-shots, with its own tools, and record their source and license beside them.

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed6 days ago
    Updatedtoday

    What's inside

    Frequently Asked Questions

    No. Describe the game and the mood; the agent writes the score, checks it and tells you what it decided.

    Yes. Everything is synthesised, nothing to clear; the audio, MIDI and scripts you make are yours. One license per person, commercial use allowed.

    Yes, as drums: point the agent at your one-shots and the kit plays them in place of the synthesised kick, snare, hats or crash, resampled to the render's rate, tuned or cut if you ask. They stay yours and under their own license; the skill ships none. With no pack, ask for sampled drums and the agent brings CC0 one-shots and records where each came from.

    Anything that plays a WAV or OGG. The skill has integration notes and snippets for Unity, Godot, Web Audio, Decentraland and AGS, and writes loop points into the files.

    Yes. Pro installs over it in place (same skill name), every name is kept and the MIDI of your scores does not change. The audio sounds cleaner: Pro's pulse and saw voices are band-limited and its piano is damped, and a keyword gives back the old sound of each.

    No. The three scripts are copied beside your generators, so the game regenerates its sound with Python and numpy alone.

    Yes, every future version of ChipTune Pro.

    No. The scripts open local files only, no telemetry. The one download is on request: ask for sampled drums with no pack of your own and the agent fetches CC0 one-shots with its own tools, auditions them by measurement and writes their source, license and credits beside them.

    New in Game Development