Apply when reporting any run's outcome. What did not happen is reported as visibly as what did — skipped passes, degraded modes, and deliberate omissions each get a named line.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add bostonaholic/team --skill principle-skip-loudly --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Principle Skip Loudly?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bostonaholic-principle-skip-loudly)More formats (shields.io, HTML) on the badges page.
---
name: principle-skip-loudly
description: "Apply when reporting any run's outcome. What did not happen is reported as visibly as what did — skipped passes, degraded modes, and deliberate omissions each get a named line."
user-invocable: false
---
# Skip Loudly
Whatever did not happen is reported as visibly as what did. A skipped
pass, a degraded mode, and a deliberate omission each get a named line;
a report that drops them reads exactly like a clean run.
**Why:** A sweep that skipped something and did not say so is
indistinguishable from one that had nothing to do. A reader of a report
that dropped a section cannot tell a pass that ran and found nothing from
one that never ran at all.
**Pattern:**
- A section with nothing to report says so on its own line: "No
findings.", "Not run: <reason>.", "Nothing declared." Never drop the
section.
- Name the reason with the skip — which check, what was unavailable, what
would have run.
- Report what you did NOT change: deliberate omissions, items skipped by
a fence, data loaded only in part. Anything left on disk or on the
board is named.
- A degradation is stated per affected item, in degraded words
("unverified", "captured — not yet uploaded"), never wrapped in the
success wording.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.