[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS58SHKEXD8RQBJZNKA3S8":3,"skill-same:01M7AS58SHKEXD8RQBJZNKA3S8":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AS58SHKEXD8RQBJZNKA3S8","dsp-implementation-tools-and-testing",null,"Use when getting DSP to run correctly on real hardware: implementation (fixed-point arithmetic and Q formats, overflow and saturation, real-time constraints, block processing), the tool landscape (NumPy and SciPy, MATLAB, GNU Radio, JUCE, CMSIS-DSP), testing and debugging DSP against known signals and reference implementations, and sensors and physical signals including calibration and drift.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsignal-processing\u002Fskills\u002Fdsp-implementation-tools-and-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dsp-implementation-tools-and-testing\ndescription: \"Use when getting DSP to run correctly on real hardware: implementation (fixed-point arithmetic and Q formats, overflow and saturation, real-time constraints, block processing), the tool landscape (NumPy and SciPy, MATLAB, GNU Radio, JUCE, CMSIS-DSP), testing and debugging DSP against known signals and reference implementations, and sensors and physical signals including calibration and drift.\"\n---\n\n# Signal Processing: Implementation, Tools, Testing, and Physical Sensors\n\n> **Part 4 of 5** of the *Signal Processing* reference (plugin `signal-processing`), covering §11–§14. Sibling skills: `dsp-sampling-frequency-domain-and-filters` (§0–§3), `dsp-convolution-multirate-and-spectral-analysis` (§4–§7), `dsp-audio-rf-and-images` (§8–§10), `dsp-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `dsp-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers who need DSP working, not a course. Three\n> markers:\n> - **[DURABLE]** — sampling theory, transforms, filters, estimation. **Nyquist is 1928;\n>   Shannon 1949; the Cooley–Tukey FFT 1965. This material does not expire.**\n> - **[VERSIONED]** — codecs, libraries, hardware, the ML layer.\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark where the code runs, the plot looks fine, and the answer is\n> wrong.\n>\n> **The three framings that organize everything below:**\n> 1. **Everything is a trade between time and frequency resolution, and you cannot cheat\n>    it.** The uncertainty principle is not a metaphor here — **a short window gives you\n>    good time resolution and poor frequency resolution, and no amount of cleverness\n>    escapes that** (§2.4 → `dsp-sampling-frequency-domain-and-filters`). Most DSP design is choosing where on that curve to sit.\n> 2. **⚠️ Aliasing is irreversible.** Once you've sampled too slowly, the information is\n>    gone — no filter, no algorithm, and no neural network recovers it. **This is the one\n>    mistake in this document that cannot be fixed downstream** (§1 → `dsp-sampling-frequency-domain-and-filters`).\n> 3. **The field is mid-convergence with machine learning, and the interesting result is\n>    that hybrids are winning** — not pure DSP, and not pure end-to-end learning.\n>    ⚠️ **The pattern that keeps recurring: use DSP for the structure you know, and learn\n>    the parameters you can't hand-tune** (§8 → `dsp-audio-rf-and-images`, §16.1 → `dsp-reference`).\n\n---\n\n## §11. Implementation\n\n**[DURABLE] Where DSP theory meets the hardware budget.**\n\n**Fixed point** — ⚠️ **still standard on MCUs, DSP chips, and in FPGA\u002FASIC.**\n**Q notation** (Q15, Q31) describes where the binary point sits. **The failure modes**:\n**overflow** (⚠️ **use saturating arithmetic — wraparound turns a loud sound into a\nhorrible one**), **underflow and loss of precision** in cascades, and ⚠️ **coefficient\nquantization changing your filter's response — and in IIR, potentially its stability**\n(§3.2 → `dsp-sampling-frequency-domain-and-filters`). **Always simulate in fixed point before committing to hardware.**\n\n**⚠️ Denormals**: on some CPUs, arithmetic on denormal floats runs **orders of magnitude\nslower**. In a decaying IIR filter this manifests as **CPU spikes when the signal goes\nquiet** — a genuinely confusing symptom. **Enable flush-to-zero, or inject tiny dither.**\n\n**Real-time constraints**: fixed block size, **⚠️ no allocation, no locks, and no\nunbounded operations in the audio callback** — this is a hard-real-time thread, and a\n`malloc` or a mutex in it produces dropouts. **Lock-free ring buffers** to communicate with\nother threads. **Latency = block size + algorithmic delay + hardware buffering.**\n\n**Hardware**: **SIMD** (⚠️ **DSP vectorizes exceptionally well — this is often a 4–8×\nwin**), **DSP cores** (TI C6000, ADI SHARC), **ARM CMSIS-DSP** on Cortex-M (⚠️ **and the\nM4F\u002FM7 DSP extensions make surprisingly capable audio possible on a microcontroller**),\n**FPGA** for extreme throughput or determinism, and **GPU** for large batch or image work\n(⚠️ **but usually the wrong answer for low-latency streaming audio because of transfer\noverhead**).\n\n---\n\n## §12. Tools\n\n**Python**: **`scipy.signal`** (⚠️ **the practical default — and remember `output='sos'`\nand `resample_poly`**), **NumPy**, **`librosa`** (music\u002Faudio analysis),\n**`python-soundfile`**, **`pyFFTW`**, **`torchaudio`**.\n**MATLAB**: the **Signal Processing** and **DSP System** toolboxes are genuinely excellent\nand remain an industry standard, with a real Simulink-to-hardware path.\n**C\u002FC++**: **FFTW** (⚠️ **the reference FFT; note the GPL\u002Fcommercial licensing**),\n**KissFFT** (permissive, simple), **CMSIS-DSP**, **JUCE** (audio applications),\n**liquid-dsp** (SDR), **Eigen**.\n**Julia**: `DSP.jl`, `FFTW.jl`. **GNU Radio** for SDR flowgraphs (§9 → `dsp-audio-rf-and-images`).\n**Analysis**: **Audacity**, **Sonic Visualiser**, **REW**, **Inspectrum**, and\n⚠️ **a spectrum analyzer plugin of some kind is the single most useful debugging tool in\naudio work** (§13).\n\n---\n\n## §13. Testing and Debugging DSP\n\n**[DURABLE] The discipline, and it's underdeveloped in most codebases.**\n\n**⚠️ Test with known signals first, always**: an impulse (gives you the impulse response\ndirectly), a step, a pure sine at a known frequency and amplitude, white noise (⚠️ **which\nshould give you a flat spectrum — if it doesn't, your analysis is wrong before your\nalgorithm is**), and a **chirp\u002Fsweep** to get the frequency response in one shot.\n\n**Verify the properties you can check cheaply**: **Parseval's theorem** (⚠️ **energy in\ntime equals energy in frequency — a superb catch-all for scaling and normalization bugs**),\n**linearity and time-invariance** where they should hold, **DC gain**, **group delay**, and\n**round-trip identity** (analyze then synthesize should reconstruct).\n\n**⚠️ Look at the signal.** Plot the waveform, the spectrum, and the spectrogram. **Most DSP\nbugs are instantly visible and invisible in numbers** — and for audio, **listen to it**.\nThe ear detects artifacts that no metric flags.\n\n**⚠️ The specific bugs to check for first**: **off-by-one in window alignment or overlap**;\n**scaling factors** from FFT normalization; **edge effects** at buffer boundaries\n(⚠️ **the classic: filter state not carried between blocks, giving a click at every block\nboundary**); **circular convolution wraparound** (§4 → `dsp-convolution-multirate-and-spectral-analysis`); **complex conjugate and sign\nconventions**; **and phase unwrapping**.\n\n**Metrics**: SNR, THD, THD+N, SINAD, ENOB for converters; **PESQ, POLQA, STOI, SI-SDR**\nfor speech quality — ⚠️ **and the honest caveat that these correlate imperfectly with human\njudgement, which is why subjective MOS testing persists.**\n\n---\n\n## §14. Sensors and Physical Signals\n\n**⚠️ The physical layer determines what's possible, and it's often mishandled in\nsoftware-first teams.** **Transducer characteristics** — sensitivity, frequency response,\nnonlinearity, drift — **bound your entire system**; no filter fixes a bad sensor.\n**Calibration** matters and drifts with temperature and time. **Grounding, shielding, and\nmains hum** at 50\u002F60 Hz and harmonics are the most common contaminants in instrumentation.\n**Anti-aliasing before the ADC** (§1.1 → `dsp-sampling-frequency-domain-and-filters`). **Common-mode rejection** in differential\nmeasurements. **Noise types**: thermal\u002FJohnson (white), shot, **1\u002Ff flicker**\n(⚠️ **dominant at low frequencies and the reason DC measurements are hard**), and\nquantization (§1.2 → `dsp-sampling-frequency-domain-and-filters`).\n\n**Domain notes**: **biomedical** — ECG (baseline wander, mains, muscle artifact), EEG\n(⚠️ **microvolt-level, and eye-blink artifacts dominate**), PPG (motion artifact);\n**vibration and machinery** — envelope analysis for bearing faults, order tracking;\n**seismic and geophysical** — deconvolution; **radar\u002Flidar** — matched filtering and\npulse compression.\n","# Signal Processing: Implementation, Tools, Testing, and Physical Sensors\n\n> **Part 4 of 5** of the *Signal Processing* reference (plugin `signal-processing`), covering §11–§14. Sibling skills: `dsp-sampling-frequency-domain-and-filters` (§0–§3), `dsp-convolution-multirate-and-spectral-analysis` (§4–§7), `dsp-audio-rf-and-images` (§8–§10), `dsp-reference` (§15–§20). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 → `dsp-reference` for the currency snapshot and what goes stale first.\n\n> **How to read this.** Reference for engineers who need DSP working, not a course. Three\n> markers:\n> - **[DURABLE]** — sampling theory, transforms, filters, estimation. **Nyquist is 1928;\n>   Shannon 1949; the Cooley–Tukey FFT 1965. This material does not expire.**\n> - **[VERSIONED]** — codecs, libraries, hardware, the ML layer.\n> - **[CONTESTED]** — genuine disagreement.\n>\n> **⚠️ GOTCHA** boxes mark where the code runs, the plot looks fine, and the answer is\n> wrong.\n>\n> **The three framings that organize everything below:**\n> 1. **Everything is a trade between time and frequency resolution, and you cannot cheat\n>    it.** The uncertainty principle is not a metaphor here — **a short window gives you\n>    good time resolution and poor frequency resolution, and no amount of cleverness\n>    escapes that** (§2.4 → `dsp-sampling-frequency-domain-and-filters`). Most DSP design is choosing where on that curve to sit.\n> 2. **⚠️ Aliasing is irreversible.** Once you've sampled too slowly, the information is\n>    gone — no filter, no algorithm, and no neural network recovers it. **This is the one\n>    mistake in this document that cannot be fixed downstream** (§1 → `dsp-sampling-frequency-domain-and-filters`).\n> 3. **The field is mid-convergence with machine learning, and the interesting result is\n>    that hybrids are winning** — not pure DSP, and not pure end-to-end learning.\n>    ⚠️ **The pattern that keeps recurring: use DSP for the structure you know, and learn\n>    the parameters you can't hand-tune** (§8 → `dsp-audio-rf-and-images`, §16.1 → `dsp-reference`).\n\n---\n\n## §11. Implementation\n\n**[DURABLE] Where DSP theory meets the hardware budget.**\n\n**Fixed point** — ⚠️ **still standard on MCUs, DSP chips, and in FPGA\u002FASIC.**\n**Q notation** (Q15, Q31) describes where the binary point sits. **The failure modes**:\n**overflow** (⚠️ **use saturating arithmetic — wraparound turns a loud sound into a\nhorrible one**), **underflow and loss of precision** in cascades, and ⚠️ **coefficient\nquantization changing your filter's response — and in IIR, potentially its stability**\n(§3.2 → `dsp-sampling-frequency-domain-and-filters`). **Always simulate in fixed point before committing to hardware.**\n\n**⚠️ Denormals**: on some CPUs, arithmetic on denormal floats runs **orders of magnitude\nslower**. In a decaying IIR filter this manifests as **CPU spikes when the signal goes\nquiet** — a genuinely confusing symptom. **Enable flush-to-zero, or inject tiny dither.**\n\n**Real-time constraints**: fixed block size, **⚠️ no allocation, no locks, and no\nunbounded operations in the audio callback** — this is a hard-real-time thread, and a\n`malloc` or a mutex in it produces dropouts. **Lock-free ring buffers** to communicate with\nother threads. **Latency = block size + algorithmic delay + hardware buffering.**\n\n**Hardware**: **SIMD** (⚠️ **DSP vectorizes exceptionally well — this is often a 4–8×\nwin**), **DSP cores** (TI C6000, ADI SHARC), **ARM CMSIS-DSP** on Cortex-M (⚠️ **and the\nM4F\u002FM7 DSP extensions make surprisingly capable audio possible on a microcontroller**),\n**FPGA** for extreme throughput or determinism, and **GPU** for large batch or image work\n(⚠️ **but usually the wrong answer for low-latency streaming audio because of transfer\noverhead**).\n\n---\n\n## §12. Tools\n\n**Python**: **`scipy.signal`** (⚠️ **the practical default — and remember `output='sos'`\nand `resample_poly`**), **NumPy**, **`librosa`** (music\u002Faudio analysis),\n**`python-soundfile`**, **`pyFFTW`**, **`torchaudio`**.\n**MATLAB**: the **Signal Processing** and **DSP System** toolboxes are genuinely excellent\nand remain an industry standard, with a real Simulink-to-hardware path.\n**C\u002FC++**: **FFTW** (⚠️ **the reference FFT; note the GPL\u002Fcommercial licensing**),\n**KissFFT** (permissive, simple), **CMSIS-DSP**, **JUCE** (audio applications),\n**liquid-dsp** (SDR), **Eigen**.\n**Julia**: `DSP.jl`, `FFTW.jl`. **GNU Radio** for SDR flowgraphs (§9 → `dsp-audio-rf-and-images`).\n**Analysis**: **Audacity**, **Sonic Visualiser**, **REW**, **Inspectrum**, and\n⚠️ **a spectrum analyzer plugin of some kind is the single most useful debugging tool in\naudio work** (§13).\n\n---\n\n## §13. Testing and Debugging DSP\n\n**[DURABLE] The discipline, and it's underdeveloped in most codebases.**\n\n**⚠️ Test with known signals first, always**: an impulse (gives you the impulse response\ndirectly), a step, a pure sine at a known frequency and amplitude, white noise (⚠️ **which\nshould give you a flat spectrum — if it doesn't, your analysis is wrong before your\nalgorithm is**), and a **chirp\u002Fsweep** to get the frequency response in one shot.\n\n**Verify the properties you can check cheaply**: **Parseval's theorem** (⚠️ **energy in\ntime equals energy in frequency — a superb catch-all for scaling and normalization bugs**),\n**linearity and time-invariance** where they should hold, **DC gain**, **group delay**, and\n**round-trip identity** (analyze then synthesize should reconstruct).\n\n**⚠️ Look at the signal.** Plot the waveform, the spectrum, and the spectrogram. **Most DSP\nbugs are instantly visible and invisible in numbers** — and for audio, **listen to it**.\nThe ear detects artifacts that no metric flags.\n\n**⚠️ The specific bugs to check for first**: **off-by-one in window alignment or overlap**;\n**scaling factors** from FFT normalization; **edge effects** at buffer boundaries\n(⚠️ **the classic: filter state not carried between blocks, giving a click at every block\nboundary**); **circular convolution wraparound** (§4 → `dsp-convolution-multirate-and-spectral-analysis`); **complex conjugate and sign\nconventions**; **and phase unwrapping**.\n\n**Metrics**: SNR, THD, THD+N, SINAD, ENOB for converters; **PESQ, POLQA, STOI, SI-SDR**\nfor speech quality — ⚠️ **and the honest caveat that these correlate imperfectly with human\njudgement, which is why subjective MOS testing persists.**\n\n---\n\n## §14. Sensors and Physical Signals\n\n**⚠️ The physical layer determines what's possible, and it's often mishandled in\nsoftware-first teams.** **Transducer characteristics** — sensitivity, frequency response,\nnonlinearity, drift — **bound your entire system**; no filter fixes a bad sensor.\n**Calibration** matters and drifts with temperature and time. **Grounding, shielding, and\nmains hum** at 50\u002F60 Hz and harmonics are the most common contaminants in instrumentation.\n**Anti-aliasing before the ADC** (§1.1 → `dsp-sampling-frequency-domain-and-filters`). **Common-mode rejection** in differential\nmeasurements. **Noise types**: thermal\u002FJohnson (white), shot, **1\u002Ff flicker**\n(⚠️ **dominant at low frequencies and the reason DC measurements are hard**), and\nquantization (§1.2 → `dsp-sampling-frequency-domain-and-filters`).\n\n**Domain notes**: **biomedical** — ECG (baseline wander, mains, muscle artifact), EEG\n(⚠️ **microvolt-level, and eye-blink artifacts dominate**), PPG (motion artifact);\n**vibration and machinery** — envelope analysis for bearing faults, order tracking;\n**seismic and geophysical** — deconvolution; **radar\u002Flidar** — matched filtering and\npulse compression.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsignal-processing\u002Fskills\u002Fdsp-implementation-tools-and-testing",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill dsp-implementation-tools-and-testing",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill dsp-implementation-tools-and-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill dsp-implementation-tools-and-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fsignal-processing\u002Fskills\u002Fdsp-implementation-tools-and-testing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]