A quick-reference manifest of all portable listening skills in this repository.
v0.9 adds attributable listening passes, listening provenance and corpus lineage, addressable route decisions and coded silence, explicit plural-listening versus ear-swarm declarations, plus corpus-listening and /corpus; it also makes clear that supplied text is not heard sound. v0.8 adds accountable listening context: position, apertures, auditory scales, sources, participants, authority, revision, and honest absence become validated data on every current hearing. v0.7 adds the sovereignty layer: the sovereign-listening mode, the /covenant command, and the listening-covenant schema (schemas/covenant.schema.json). v0.6 instruments the system for host apps with the manifest, presets, memory-lineage listening, apparatus/listener/memory declarations, and budget-aware routing plans.
| Skill | Description |
|---|---|
akouo-router |
Meta-router that analyzes the listening situation, evidence type, risk level, conceptual frame, and assigns primary, secondary, and corrective listening modes. Use this first before any specialized mode. |
reference-layer |
Conceptual mapping layer that turns a sonic object or prior listening output into concepts, sonic methodologies, authors or traditions, research routes, questions, cautions, and adjacent modes. Used by /reference, /study, and /method. |
| Skill | Description | When To Use |
|---|---|---|
signal-inspection-listening |
Technical signal inspection ear. | Audio files, waveforms, spectrograms, metadata, dynamics, frequency, clipping, noise, codecs, compression, machine-listening outputs. |
acoulogical-object-listening |
Perceptual object ear for sound-as-auditum. | Sound design, experimental music, Foley, synthetic sounds, ambiguous sources, acousmatic situations, texture-first listening. |
embodied-affective-listening |
Body and affect ear. | Bass/club music, noise, drone, ambient, ASMR, sirens, sonic weapons, accessibility, atmospheres of dread or euphoria. |
transductive-media-listening |
Mediation and transduction ear. | Sonification, sensors, AI audio, voice cloning, ASR, neural codecs, compression artifacts, platform-mediated recordings. |
forensic-archival-listening |
Evidentiary and archival ear. | Recordings of violence, testimony, surveillance, protest recordings, archives, damaged tapes, legal or custody contexts. |
ecological-posthuman-listening |
More-than-human and ecological ear. | Field recordings, weather, hydrophones, animal sound, acoustic ecology, urban ecology, soundwalks, habitat and infrastructure listening. |
critical-political-listening |
Critical and political ear. | AI audio platforms, surveillance, colonial archives, acoustic justice, sonic policing, marginalized voices, platform critique. |
musical-aesthetic-listening |
Musical, aesthetic, and sound-design ear. | Music, rhythm, pulse, meter, tempo, pitch, harmony, interval, melody, contour, timbre, texture, form, production aesthetics, sound-design utility, poetic usefulness, and genre/cultural caution. |
symbolic-fictional-listening |
Speculative and symbolic ear. | Sonic fiction, myth, ritual, hauntology, game audio, film worlds, ambient fantasy, creative worldbuilding. |
audiovisual-scenic-listening |
Sound-image-text-scene ear. | Video, film, games, UI sound, captions, subtitles, synchronization, offscreen sound, diegesis, audiovisual phrasing, and sound-versus-vision cautions. |
voice-speech-listening |
Voice, speech, and transcript ear. | Spoken audio, transcripts, ASR, TTS, voice agents, voice cloning, podcasts, radio, diarization, intelligibility, consent, and identity caution. |
accessibility-normative-listening |
Accessibility and hearing-norm ear. | Captions, transcripts, haptics, deaf and hard-of-hearing access, sensory variation, fatigue, masking, alerts, assistive technology, and implied listener audits. |
material-event-listening |
Material, vibration, and event ear. | Resonance, vibration, duration, flux, feedback, low frequencies, installation sound, propagation, loudspeakers, room coupling, and sonic process. |
memory-lineage-listening |
Sound-memory and lineage ear. | Stored listening records, akousma/akousmata stores, recurrence, kinship, lineage, series over time, archive comparison, and registering listenings into a store. |
sovereign-listening |
Sovereignty ear that listens under a covenant. | Community protocols, consent-bound recording, the right to silence and opacity, retention rules, habitat protocols, listening without identification, and auditing hearings against a declared covenant. |
corpus-listening |
Computational-inheritance and corpus-provenance ear. | Training, fine-tuning, retrieval, annotation, provider disclosure, licensing, labor, consent, jurisdiction, opt-out, and unknown lineage. |
Each skill folder includes a references/ directory containing the JSON schemas needed for strict output formatting:
listening-output.schema.json— shared output structure for all listening modeslistening-context.schema.json— accountable declaration of position, apertures, scale, sources, participants, authority, revision, and honest absenceclaim-taxonomy.schema.json— epistemic claim categories (heard, measured, inferred, interpreted, speculative, undetermined)listening-pass.schema.json— one attributable listening at one momentlistening-provenance.schema.json— evidence sources, cuts, corpora, and optional source-of-voice disclosureroute-decision.schema.json— accountable gate outcomes, including coded silenceensemble.schema.json— explicit plural-listening or ear-swarm declarationrouter-output.schema.json— router-specific output structure (bundled withakouo-routeronly)routing-plan.schema.json— expanded agent handoff route structure (bundled withakouo-routeronly)reference-map.schema.json— conceptual mapping output structure (bundled withreference-layeronly)
All skills follow the standard skill format:
- YAML frontmatter with
nameanddescriptionfor agent triggering - Markdown body with structured instructions
- Bundled JSON schemas for standalone use
Compatible with any LLM agent framework that supports skill injection (OpenCode, Claude Code, Gemini, etc.).
- Humans: Browse the table above and click through to individual
SKILL.mdfiles. - Agents: Load
SKILL.mdfrom any skill folder as a system prompt. Schemas are inreferences/. - Developers: Preserve the manifest and bundled-schema conventions, then run
./scripts/validate-release.shafter adding or modifying a skill.