Inspect GPX score files with AI
Trace tuning and track information through scorelib's modern Guitar Pro reader, then verify the same detail after writing the score.
Inspect GPX score files with AI when an imported score looks plausible but a specific detail is wrong. A guitar with an unusual tuning makes a good test because a fallback to standard tuning is easy to spot. The gp-modern-format skill distinguishes opening the container from interpreting the musical data it holds.
GP6 and GP7 use different containers around GPIF score data. That gives a contributor two distinct places to investigate. Once the score content is available, follow the affected track through the internal representation instead of assuming that every missing value came from unpacking the file.
What it does
- Distinguish the GP6 container from its GP7 counterpart.
- Trace a track's tuning to the data used for that format.
- Check how measure, voice and beat references fit together.
- Recognise when a default value masks missing source information.
- Verify that a change survives export and reimport.
Install and use
- Give the agent the public scorelib checkout, a Rust toolchain and a score you may use. Identify the relevant format and expected result.
- Ask, “Find out why this six-string track comes back in standard tuning. Compare its source and imported values before proposing a fix.”
- Keep a small round-trip test that checks the actual tuning or rhythm as well as successful parsing.
FAQ
Source
Made by slundi. Original skill: gp-modern-format, published on Codeberg under the MIT licence.
View on Codeberg