verify-live
Skill1 starsChanged 2 months agoMITView on GitHub
Exercise Lineupify against the real Spotify, Deezer and Last.fm APIs and the published npm package: live tests, smoke scripts, a stranger-style install, and a Deezer-mode build. Use before a release, after an API change, or when asked to test the whole app.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- mojopoly/three-loopstheir own version, first seen Oct 20, 2026
- facontidavide/PlotJugglertheir own version, first seen Oct 8, 2026
- tydude001/proofcuttheir own version, first seen Oct 7, 2026
- Neogenuity/harness-kittheir own version, first seen Jul 14, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- facontidavide/PlotJuggler★ 6.3ksame name
- tydude001/proofcut★ 4same name
- mojopoly/three-loops★ 0same name
- Neogenuity/harness-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-featureSkill
- api-checkSkill
- dependabot-triageSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Run this from a directory outside the repo so npx fetches from the registry rather than the local package.
- Very specific: line 63
If Spotify starts returning 404/403 on an endpoint the smoke test uses, update the header of src/sources/spotify.ts and …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify Lineupify live
The unit suite is offline; these steps prove the real world still matches. Nothing here publishes a playlist unless you call create_playlist yourself.
1. Offline gate first
npm run typecheck && npm run lint && npm test2. Deezer (no account needed)
npm run test:liveCovers artist resolution, related artists, chart, playlist search and tracks, ISRC lookup (tempo), title search ordering.
3. Spotify (needs a connected account: lineupify-mcp doctor shows it)
npm run smoke:spotify # every endpoint; leaves a playlist named "[delete me] Lineupify smoke"
npx tsx test/smoke/playlists.ts <public user-made playlist link> # read, analysis, taste profile, all seed types, library readSpotify-made playlists (Discover Weekly, editorial) 404 by design; use a playlist a person made.
4. Deezer mode end to end (no Spotify)
Run the tool handlers directly with tsx, e.g. a script that imports src/tools/drafts.ts and calls createDraft({ provider: 'deezer', artists: [...], seeds: [{ type: 'genre', value: 'shoegaze' }], yearRange: { from: 2010 } }), polls getDraftTool with waitSeconds: 25, then exportDraft with format: 'links', searchTracks({ provider: 'deezer' }), editDraft add_track, readPlaylistTool / mergePlaylistsTool / expandPlaylistTool on a public Deezer playlist such as https://www.deezer.com/playlist/1109890291 (Top France by Deezer Charts). Delete the drafts afterwards with deleteDraft from src/engine/draft.ts, or they clutter list_drafts (unpublished drafts are pruned after 30 days anyway).
5. The published package, as a stranger
export LINEUPIFY_HOME=$(mktemp -d) # PowerShell: $env:LINEUPIFY_HOME = "$env:TEMP\lineupify-fresh"
export LINEUPIFY_NO_UPDATE_CHECK=1
npx -y lineupify-mcp@latest --version
npx -y lineupify-mcp@latest doctor # Client ID missing is expected; Deezer must be OK
npx -y lineupify-mcp@latest setup --client-id nope # must reject
printf 'Khruangbin\nWet Leg\n' > lineup.txt && npx -y lineupify-mcp@latest preview lineup.txt --per-artist 2
npx -y lineupify-mcp@latest init < /dev/null # must explain it is interactive and exit 2Run this from a directory outside the repo so npx fetches from the registry rather than the local package.
6. Protocol
npm run build && node test/smoke/mcp-stdio.mjs # initialize, tools/list (22 tools), status, parse_lineup
node test/smoke/mcp-stdio.mjs status # any single tool: node test/smoke/mcp-stdio.mjs <tool> '<json args>'What "good" looks like
- Seeds return sensible artists (similar_to Khruangbin → Skinshape, Sault, BALTHVS; shoegaze → Slowdive, my bloody valentine; Brazil → Anitta, Ana Castela).
- A 64-track playlist reads in under 2 s; analysis with genres and tempo under ~15 s the first time.
- Remaster years show as
2024?and are kept unlessstrictYear; that is documented behaviour, not a bug. - If Spotify starts returning 404/403 on an endpoint the smoke test uses, update the header of
src/sources/spotify.tsandSPOTIFY_API_SNAPSHOT, then see theapi-checkskill.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

