libsync-qobuz-auth-campaign

Detect expired Qobuz tokens and guide in-app re-authentication in Libsync.

4|Updated Aug 15, 2025
One-click install
npx skills add https://github.com/arthursoares/libsync --skill libsync-qobuz-auth-campaign
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: libsync-qobuz-auth-campaign
Source: https://github.com/arthursoares/libsync/tree/main/.claude/skills/libsync-qobuz-auth-campaign
Command: npx skills add https://github.com/arthursoares/libsync --skill libsync-qobuz-auth-campaign

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the issue of expired Qobuz tokens in the Libsync application, providing a method to detect token expiration and facilitate in-app recovery.

Core Features & Use Cases

  • Token Expiry Detection: Automatically detect and notify when a Qobuz token expires.
  • In-App Re-authentication: Direct users to a settings page to re-authenticate and refresh the token.
  • Secret-chain Hardening: Ensure the correct Qobuz app credentials are used for all operations.
  • Use Case: When the Libsync application receives a 401 error due to an expired Qobuz token, this skill triggers a banner in the app that guides the user through the process of re-authenticating with Qobuz.

Quick Start

When encountering a 'Download failed' toast in Libsync due to token expiration, click on the 'Settings' banner to re-authenticate with Qobuz.

Frequently Asked Questions about libsync-qobuz-auth-campaign

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I recover from a Qobuz token expiration error in Libsync?

Detect Qobuz token expiration in Libsync when a 401 error occurs during a download. The app automatically surfaces a banner guiding you to the settings page to initiate re-authentication and restore access.

Why does my Libsync app show a 'Download failed' toast when using Qobuz?

A 'Download failed' toast in Libsync typically indicates an expired Qobuz token returning a 401 error. The application detects this token expiry and prompts you to re-authenticate to resume downloading.

How do I ensure correct Qobuz app credentials are used after a secret rotation?

Ensure correct Qobuz app credentials are used after a secret rotation by relying on the Skill's secret-chain hardening feature, which validates app secrets and handles errors related to app-secret rotation automatically.

Can I re-authenticate with Qobuz directly inside the Libsync app?

Yes, you can re-authenticate with Qobuz directly inside the Libsync app. The skill facilitates in-app re-authentication by redirecting users to a settings page to refresh expired tokens without leaving the application.

What happens when a 401 error occurs due to an expired Qobuz token in Libsync?

When a 401 error occurs due to an expired Qobuz token in Libsync, the skill triggers an in-app banner that guides you through the re-authentication process to refresh the token and resume operations.