A repository health-check skill that runs the same broad verification script used by CI. CI is the automated system that checks changes, and this project requires a Mac for its full Swift and app checks.

It checks tests, coverage, builds, formatting, linting, dependency and site integrity, shell scripts, Python code, evaluation tests, and release checks.

It provides one reference for whether the repository is ready and avoids claiming that Mac-only tests passed on another system. A portable subset is available for non-Mac environments.

How AssemblyAI/blurt configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AssemblyAI/blurt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AssemblyAI/blurt/main/.claude/skills/check/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/AssemblyAI/blurt

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/assemblyai/blurt/check/github.svg)](https://agentmods.dev/skills/assemblyai/blurt/check)

Your own site

<a href="https://agentmods.dev/skills/assemblyai/blurt/check"><img src="https://agentmods.dev/badge/skills/assemblyai/blurt/check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/assemblyai/blurt/check"><img src="https://agentmods.dev/badge/skills/assemblyai/blurt/check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 159 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,091 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00159	$0.02091
Opus 5.5	$0.00064	$0.00836
Sonnet 5.5	$0.00032	$0.00418
Haiku 4.5	$0.00016	$0.00209

Measured 27d ago against content hash ecfdf7664c06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 27d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/check/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

check — is this green?

scripts/check.sh is the single source of truth for "is this green?" It is exactly what CI (.github/workflows/check.yml, macos-26) runs, so a clean local check.sh matches CI by construction.

Before you run: the macOS-only guard

Blurt is macOS-only (platforms: [.macOS(.v15)], AppKit + AVFoundation). The engine imports AVFoundation, so even the SPM package won't compile off-Mac.

If swift/xcodebuild/xcodegen are unavailable (Linux or web sandbox): do not run the full check.sh (it fails fast anyway), and never claim a build/test passed. Say plainly: "Verification must happen on a Mac — CI runs the full check.sh on macos-26 and is the authority on green." You may still read/edit Swift, reason about the pipeline, and write tests for later verification — just don't assert they pass.

What you CAN run there is the portable subset:

scripts/check.sh --portable

It runs the repo-integrity guards — dependencies, sound catalog, shell portability, and settled decisions — then actionlint, zizmor, prettier, xmllint, markdownlint, shellcheck, shfmt, ruff (lint + format check), pytest over evals/, and release.test.sh. swift-format lint and swiftlint lint join them when Linux builds are on PATH; under the default web network policy they are not.

That fully verifies docs, scripts, eval, and workflow changes. It is not "green" in the CI sense: the entire Swift side is skipped, and the closing line says so. For Swift changes, push and watch check.yml instead — its compile job reports a broken test build in ~2 minutes, and format-patch publishes the exact swift-format reflow as an artifact so you don't have to reproduce it by hand. In Claude Code on the web, the SessionStart hook installs the portable linters automatically.

Quick preflight:

command -v swift xcodebuild xcodegen >/dev/null 2>&1 \
  && echo "macOS toolchain present — safe to run check.sh" \
  || echo "NO toolchain — only check.sh --portable works; Swift verification happens on a Mac/CI"

Read the full file on GitHub · 139 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

27d ago Changed · +13 lines ecfdf7664c06
1mo ago Changed · -3 lines · -5 tokens per session 3c4055f87fd4
2mo ago First seen · 129 lines · 164 tokens per session scan A 16ca1507a565

Subscribe to this mod's changes

check is a skill published in the GitHub repository AssemblyAI/blurt (65 stars, last pushed today), licensed MIT. It adds 159 tokens to every session and 2,091 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Testing accessibility assemblyai dictation dictation-app macos macos-app

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens

scarf-miniapp-author

Author a Scarf mini-app — a small sandboxed web surface (HTML/CSS/JS) that renders inside a project's cockpit and talks to the bound Hermes session + project data through the versioned window.scarf bridge. Use to build a bespoke panel (a task board, an approval queue, a chart, a data table) for a project.

awizemann/scarf · 78 tokens

blurt: Skill for Claude Code