Skip to content
Back to skills

Apple Hig Shazamkit

ASecurity

Use when designing or reviewing audio recognition with Shazam or custom catalogs, microphone sampling, recognition-driven content, or opt-in library addition.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 26, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned October 26, 2026

npx -y skills add AyushRajSinghParihar/apple-human-interface-skills --skill apple-hig-shazamkit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apple Hig Shazamkit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Apple Hig Shazamkit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ayushrajsinghparihar-apple-hig-shazamkit/badge)](https://www.skillsdirectory.com/skills/ayushrajsinghparihar-apple-hig-shazamkit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: apple-hig-shazamkit
description: Use when designing or reviewing audio recognition with Shazam or custom catalogs, microphone sampling, recognition-driven content, or opt-in library addition.
---

# Recognize the needed sample without unnecessary recording

Read [ShazamKit](../../references/shazamkit.md). Inspect the recognition task, Shazam versus custom catalog, microphone lifecycle, result use, and requested design/review/adaptation. Preserve the existing audio stack and verify current API availability for the target platform; this overview adds no platform-specific rules.

Choose the recognition result that actually serves the task: identifying a song, aligning accessible captions/sign language, or revealing contextual learning content are different outcomes. Define what the app does with a match and what it shows when no useful match exists. Those result/retry states are application engineering choices, not a claim that every catalog guarantees a match.

Explain and request microphone access before recording. Bound the recording session to the needed recognition sample and stop as soon as it has been captured; continuous recording after a result needs a separate justified task, not inertia. Keep recording status and its result understandable. If recognized songs can be added to the person's iCloud library, obtain opt-in first even when Music Recognition/Shazam identifies the originating app. Recognition is not consent to modify the library.

**Before → decision → after:** A music-history app starts listening silently on launch, keeps recording after identifying a track, and automatically adds every match to the library. Decision: recognition and saving are separate intents. After, an explicit recognition action explains microphone use, sampling stops when sufficient, the result shows the identified track, and a separate opt-in controls library addition.

Deliver the permission/sample/result/library-action contract or implementation. Fail if recording starts before required access, continues after the needed sample without purpose, or recognition changes the library without opt-in. Test actual microphone start/stop and catalog matching where supported; static flow review cannot establish recognition accuracy, synchronized accessibility content, or iCloud library behavior.

Use [Privacy](../../../apple-hig-foundations/.topics/apple-hig-privacy/SKILL.md) for recording explanations and [Accessibility](../../../apple-hig-foundations/.topics/apple-hig-accessibility/SKILL.md) when recognition drives captions/sign-language alternatives.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.